|
netwinxp
高级用户
   
积分 741
发帖 366
注册 2007-7-25
状态 离线
|
『第 31 楼』:
使用 LLM 解释/回答一下
MMC的磁盘管理不太行,不过Diskpart还是很不错滴。
The disk management of MMC is not very good, but Diskpart is really good.
|
|
2008-12-25 14:13 |
|
|
xsrdg
初级用户
 
积分 51
发帖 27
注册 2007-11-9
状态 离线
|
『第 32 楼』:
使用 LLM 解释/回答一下
Originally posted by Climbing at 2008-12-25 09:54 AM:
我同意楼上fujianabc兄的观点。
我用PQ分区,当然不全是新机器,完全重新分区,我给人装系统,好多时候对方的硬盘上已经有好多数据(分过区),我要用PQ的无损分区功能重新整理一下不合理的分区方案。我除了用PQ分区后,常用的还有Acronis,有时候,PQ进入时会提示分区表错误(Error 106之类的)然后无法看到原硬盘的分区,但Acronis却能正常识别原来的分区,这时候我就用Acronis来给硬盘分区,但用Acronis处理过后,PQ又能正常识别了。当然,我几乎从来不用Windows的磁盘管理器分区,就算是用,至多也是删除原来一个分区再重建。
从你这段回复可知同样遇到PQ误报问题。也说明了PQ存在严重问题了,它把没问题的分区误认为有问题,更要命的是千万不能修复,一修复就造成不可修复性的损失。其它分区软件不认为错,更重要的是磁盘能正常使用,就不能认为分区有错,只是PQ不认可的格式。不用microsoft的分区软件主要就是它不能无损分区,但兼容性它是最好的,或者说大家都要兼容它。我想“不点”大师也是这么认为的,你看,他每次回答别人问题时,只要提到分区、格式化时,都说要用microsoft的fdisk和format,以免可能出现一些不可知的莫名其妙的问题。
Originally posted by Climbing at 2008-12-25 09:54 AM:
I agree with the view of brother fujianabc above.
When I use PQ to partition, of course, it's not all new machines. I completely re-partition. When I install the system for others, many times the other party's hard drive already has a lot of data (partitioned). I need to use the lossless partition function of PQ to re-organize the unreasonable partition scheme. In addition to using PQ to partition, I often use Acronis. Sometimes, when PQ enters, it prompts a partition table error (Error 106, etc.) and then cannot see the original hard drive partitions, but Acronis can normally recognize the original partitions. At this time, I use Acronis to partition the hard drive, but after processing with Acronis, PQ can recognize normally again. Of course, I almost never use Windows Disk Manager to partition. Even if I use it, at most I delete the original partition and rebuild it.
From your reply, it can be seen that the same PQ false alarm problem is encountered. It also shows that PQ has serious problems. It mistakenly thinks that there are no problems with the partitions, and what's more, it must not be repaired. Once repaired, it will cause irreparable losses. Other partition software does not think it is wrong. More importantly, the disk can be used normally, so it cannot be considered that there is a partition error, just the format that PQ does not recognize. The main reason for not using Microsoft's partition software is that it cannot partition without loss, but its compatibility is the best, or that everyone has to be compatible with it. I think Master "不点" also thinks so. You see, every time he answers others' questions, as long as he mentions partitioning and formatting, he says to use Microsoft's fdisk and format to avoid some unknown and inexplicable problems.
|
|
2008-12-25 22:26 |
|
|
lianjiang2004
金牌会员
     
积分 3946
发帖 1884
注册 2006-1-20
状态 离线
|
『第 33 楼』:
使用 LLM 解释/回答一下
“用microsoft的fdisk和format”与“Windows的磁盘管理器分区”是两码事,呵呵。
"Using Microsoft's fdisk and format" is completely different from "Windows Disk Management for partitioning", heh.
|

Windows 一键还原
http://www.yjhy.com |
|
2008-12-26 00:36 |
|
|
Climbing
铂金会员
       网络独行侠
积分 6962
发帖 2753
注册 2003-4-16 来自 河北保定
状态 离线
|
『第 34 楼』:
@xsrdg
使用 LLM 解释/回答一下
PQ报错时,往往就算是修复了,它照样不能正常识别原来的硬盘分区。
我觉得,这也不能算是PQ的错,你只能说它对分区表格式检查严格,事实就是,凡是PQ认可的分区表格式,在其它分区软件中也从来不会出现问题。至于用PQ修复导致错误发生,只能说PQ的分区表修复功能比较垃圾,毕竟它是一个程序,如果大家都严格按照规矩来修改分区表,可能就不容易出现错误。
不过,今天遇到一个情况需要向大家汇报一下,提起重视:今天给一台机器重新安装系统,刚开始我仍然使用Volume Manager 2.0 for DOS(也就是PQ的服务器版)来给硬盘分区,开始时一切正常。但由于这台机器的原硬盘(联想的机器)有HPA保留区,我使用hpatool将它清除掉了,但在DOS下看不到释放的这一部分空间,安装好xp后,在xp的硬盘管理器下可以看到,我为了避免重新启动,就使用paragon partition manager将这部分空间与前面预留的空间合并成了一个逻辑分区,用来制做基于HPA的一键恢复分区(我用的hpa一键恢复是基于清华同方的,也就是软通科技的产品)。这个hpa的一键恢复软件安装正常,重新启动后按热键也可以正常启动并进入,但自动查找最后一个分区(也就是显示出来的hpa分区)时,发现了问题,omnifs info命令无法显示最后的两个逻辑分区(第一个是一个正常的逻辑分区,第二个就是那个hpa分区),导致我的备份批处理无法正常将克隆文件备份到这个hpa分区。启动Volume Manager for DOS,果然发现分区表错误并提示修复,修复后果然导致了严重问题:我再重新启动,进入DOS后发现,除了C:盘正常外,从D:盘以后的盘符全部只显示第一个逻辑分区的内容,进入diskgen,显示分区参数重叠(一直不断的提示,无法进入),再重启用grub4dos的geometry (hd0)来看,会发现有无数个逻辑分区(这大概就是类似逻辑锁之类的东西了),启动Acronis Disk Director Suite也无法进入。最后实在搞不定了,我用diskrw 0 0 1 /e /y命令将逻辑0扇区清空了,这时候相当于硬盘是空的,然后用Acronis的分区恢复功能恢复了XP所在的主分区(Acronis的分区恢复功能很垃圾,速度巨慢,而且,成功率很低),然后重新启动进入XP,使用Partition Table Doctor重建分区表,顺利恢复了丢失的所有分区。然后重新建立HPA分区(这次是在XP下用gdisk32建立),再次安装HPA的一键恢复软件,这次就完全没有问题了。
通过这个事故说明什么呢?PQ的分区应该很标准,而Paragon Partiton Manager的分区并不是绝对规范,另外,尽量不要使用PQ的分区修复功能,真的很垃圾。
When PQ reports an error, even if it is fixed, it still cannot normally recognize the original hard disk partitions.
I think this can't be regarded as PQ's fault. You can only say that it is strict in checking the partition table format. The fact is that any partition table format recognized by PQ has never had problems in other partition software. As for the error caused by PQ repair, it can only be said that PQ's partition table repair function is relatively rubbish. After all, it is a program. If everyone strictly modifies the partition table according to the rules, it may not be easy to have errors.
However, today I encountered a situation that needs to be reported to everyone and attract attention: Today, I reinstalled the system on a machine. At the beginning, I still used Volume Manager 2.0 for DOS (that is, the server version of PQ) to partition the hard disk, and everything was normal at the beginning. But because the original hard disk (Lenovo machine) of this machine has an HPA reserved area, I used hpatool to clear it, but this part of the space was not visible under DOS. After installing XP, it could be seen under the disk manager of XP. In order to avoid restarting, I used Paragon Partition Manager to merge this part of the space with the previously reserved space into a logical partition to make a one-key recovery partition based on HPA (the HPA one-key recovery I used is based on Tsinghua Tongfang, that is, the product of Soft-Tech). This HPA one-key recovery software was installed normally, and it could be started and entered normally by pressing the hotkey after restarting, but when automatically finding the last partition (that is, the displayed HPA partition), a problem was found. The omnifs info command could not display the last two logical partitions (the first one is a normal logical partition, and the second one is that HPA partition), which caused my backup batch processing to fail to back up the clone file to this HPA partition normally. Starting Volume Manager for DOS, it果然 found that the partition table was wrong and prompted to repair. After repairing, it果然 caused serious problems: I restarted again, and when entering DOS, I found that except for the C: drive being normal, the drive letters from D: drive onwards all showed the content of the first logical partition. Entering DiskGen, it showed that the partition parameters overlapped (it kept prompting and could not enter). Then restarting and using grub4dos's geometry (hd0) to see, there would be countless logical partitions (this is probably something similar to a logical lock), and Acronis Disk Director Suite could not be entered. Finally, I couldn't handle it anymore. I used the command diskrw 0 0 1 /e /y to clear the logical 0 sector. At this time, it was equivalent to the hard disk being empty. Then I used the partition recovery function of Acronis to recover the main partition where XP was located (the partition recovery function of Acronis is very rubbish, the speed is extremely slow, and the success rate is very low). Then I restarted and entered XP, used Partition Table Doctor to rebuild the partition table, and successfully recovered all the lost partitions. Then I re-established the HPA partition (this time using gdisk32 under XP to establish), and installed the HPA one-key recovery software again. This time there was no problem at all.
What does this accident illustrate? PQ's partitions should be very standard, and Paragon Partition Manager's partitions are not absolutely standard. In addition, try not to use PQ's partition repair function, it is really rubbish.
|

偶只喜欢回答那些标题和描述都很清晰的帖子!
如想解决问题,请认真学习“这个帖子”和“这个帖子”并努力遵守,如果可能,请告诉更多的人!
|
|
2008-12-26 00:58 |
|
|
netwinxp
高级用户
   
积分 741
发帖 366
注册 2007-7-25
状态 离线
|
『第 35 楼』:
使用 LLM 解释/回答一下
最标准的分区完全二叉树分布,结构如下:
-----------------------------------------------
MBR及分区表(整条磁道其他扇区空)。分区表项--主分区(指向主分区);扩展分区(指向下一级扩展分区表)
-----------------------------------------------
主分区
-----------------------------------------------
一级扩展分区表(整条磁道其他扇区空)。扩展分区表项--逻辑分区1(指向该分区);扩展分区(指向下一级扩展分区表)
-----------------------------------------------
逻辑分区1
-----------------------------------------------
二级扩展分区表(整条磁道其他扇区空)。扩展分区表项--逻辑分区2(指向该分区);扩展分区(指向下一级扩展分区表)
-----------------------------------------------
...
-----------------------------------------------
最后一级扩展分区表(整条磁道其他扇区空)。扩展分区表项--最后一个逻辑分区(指向该分区)
-----------------------------------------------
最后一个逻辑分区
===============================
ms的分区查找使用二叉树算法,稍微扩展一下,就是主分区表最多可以有4项。
逻辑分区的定义(比如BPB、分区表项、分区ID)和主分区表基本一样,只不过是扩展分区表内没有引导程序,只有分区表项。
在合并分区的时候如果上下级分区表没完全修改就会出问题,特别是合并中间的逻辑分区最容易出问题(要根据中间包含的那级扩展分区表项修改上一级分区表项,还要修改长度<这里的大小是两个逻辑分区+一条磁道,不是两个逻辑分区大小之和>,所以合并逻辑分区很容易出问题)。
***对于非整数条磁道的分区,那合并分区就更乱套了,严重的就会出现分区表项的指向与实际分区位置错位,连DISKGEN也无法恢复***
***逻辑分区同样直接靠BPB定位,所以如果你能在MBR中直接找到其启动扇区,并加载的话也是可以引导它的***
Last edited by netwinxp on 2008-12-26 at 14:24 ]
The most standard partition complete binary tree distribution, the structure is as follows:
-----------------------------------------------
MBR and partition table (other sectors of the whole track are empty). Partition table entries -- primary partition (points to the primary partition); extended partition (points to the next-level extended partition table)
-----------------------------------------------
Primary partition
-----------------------------------------------
First-level extended partition table (other sectors of the whole track are empty). Extended partition table entries -- logical partition 1 (points to this partition); extended partition (points to the next-level extended partition table)
-----------------------------------------------
Logical partition 1
-----------------------------------------------
Second-level extended partition table (other sectors of the whole track are empty). Extended partition table entries -- logical partition 2 (points to this partition); extended partition (points to the next-level extended partition table)
-----------------------------------------------
...
-----------------------------------------------
Last-level extended partition table (other sectors of the whole track are empty). Extended partition table entries -- last logical partition (points to this partition)
-----------------------------------------------
Last logical partition
===============================
MS's partition search uses a binary tree algorithm. A slight extension is that the primary partition table can have at most 4 entries.
The definition of logical partitions (such as BPB, partition table entries, partition ID) is basically the same as that of the primary partition table. The difference is that there is no boot program in the extended partition table, only partition table entries.
When merging partitions, problems will occur if the upper and lower partition tables are not completely modified, especially when merging intermediate logical partitions. It is easiest to have problems. (You need to modify the upper-level partition table entries according to the extended partition table entries of the intermediate level, and also modify the length <here is a image 43e6c669ebf32fce-477d9615ad37460c> here the size is two logical partitions + one track, not the sum of the sizes of two logical partitions>, so merging logical partitions is very easy to have problems.)
***For partitions that are not an integer number of tracks, then merging partitions will be even more messed up. In serious cases, there will be a misalignment between the pointer of the partition table entry and the actual partition position, and even DISKGEN cannot be recovered***
***Logical partitions are also directly located by BPB. So if you can directly find its boot sector in the MBR and load it, you can also boot it***
Last edited by netwinxp on 2008-12-26 at 14:24 ]
|
|
2008-12-26 14:07 |
|
|
fujianabc
金牌会员
     
积分 3467
发帖 1616
注册 2004-6-21
状态 离线
|
『第 36 楼』:
使用 LLM 解释/回答一下
Originally posted by netwinxp at 2008-12-26 02:07 PM:
ms的分区查找使用二叉树算法,稍微扩展一下,就是主分区表最多可以有4项。
逻辑分区的定义(比如BPB、分区表项、分区ID)和主分区表基本一样,只不过是扩展分区表内没有引导程序,只有分区表项。
ms的磁盘管理器不但能支持主分区表4项,连扩展分区表都能支持4项,其他分区软件是不支持扩展分区表里多个同级逻辑分区的。
另外,扩展分区表里也能有引导程序的:
最近装了一个opensuse 11.1,装的时候也没注意,装完一开始没找到它把grub引导扇区装到了哪里。后来仔细找了一下发现openSUSE 11.1居然把引导扇区写在了(hd0,3)+1上(我的(hd0,0) (hd0,1) (hd0,2)是三个主分区,从(hd0,3)是扩展分区),并且把(hd0,3)设置为引导分区(0x80),启动一起正常。
Last edited by fujianabc on 2008-12-26 at 20:32 ]
Originally posted by netwinxp at 2008-12-26 02:07 PM:
MS's partition search uses a binary tree algorithm. With a slight extension, the primary partition table can have at most 4 entries.
The definition of a logical partition (such as BPB, partition table entry, partition ID) is basically the same as that of the primary partition table. The only difference is that the extended partition table has no boot program, only partition table entries.
MS's Disk Manager can not only support 4 entries in the primary partition table but also 4 entries in the extended partition table. Other partition software does not support multiple sibling logical partitions in the extended partition table.
In addition, the extended partition table can also have a boot program:
Recently, I installed an openSUSE 11.1. I didn't pay attention during the installation. After installation, I couldn't find it at first and where it installed the grub boot sector. Later, I carefully found that openSUSE 11.1 actually wrote the boot sector to (hd0,3)+1 (my (hd0,0) (hd0,1) (hd0,2) are three primary partitions, and from (hd0,3) is the extended partition), and set (hd0,3) as the boot partition (0x80), and the startup is normal together.
Last edited by fujianabc on 2008-12-26 at 20:32 ]
|
|
2008-12-26 20:30 |
|
|
netwinxp
高级用户
   
积分 741
发帖 366
注册 2007-7-25
状态 离线
|
『第 37 楼』:
使用 LLM 解释/回答一下
Originally posted by fujianabc at 2008-12-26 20:30:
ms的磁盘管理器不但能支持主分区表4项,连扩展分区表都能支持4项,其他分区软件是不支持扩展分区表里多个同级逻辑分区的。
另外,扩展分区表 ...
一般的扩展分区表扇区是没有引导程序的,当然有的写入也没问题,如果要让最后一级逻辑分区也能直接启动那么每一级扩展分区表都要有引导程序。
***PS:绝大多数分区软件不支持每一级扩展分区含四个分区项,也不往扩展分区表写入引导程序***
Originally posted by fujianabc at 2008-12-26 20:30:
Microsoft's disk manager can not only support 4 primary partition table entries, but also support 4 entries in the extended partition table. Other partition software does not support multiple sibling logical partitions in the extended partition table.
In addition, the extended partition table sector generally does not have a boot program. Of course, it is okay to write it. If you want the last-level logical partition to boot directly, then each level of extended partition table must have a boot program.
***PS: Most partition software does not support 4 partition entries per level of extended partition, and does not write boot programs to the extended partition table***
|
|
2008-12-26 21:50 |
|
|
wghxx
初级用户
 
积分 85
发帖 42
注册 2007-11-14
状态 离线
|
『第 38 楼』:
使用 LLM 解释/回答一下
还是不知道用什么分区好
Still don't know what partition to use
|
|
2008-12-26 22:59 |
|
|