A computer components & hardware forum. HardwareBanter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » HardwareBanter forum » General Hardware & Peripherals » Storage (alternative)
Site Map Home Register Authors List Search Today's Posts Mark Forums Read Web Partners

Partition Magic crashes during partition move, resulting in PqRT



 
 
Thread Tools Display Modes
  #1  
Old July 23rd 03, 03:37 AM
Jonas Carlsson
external usenet poster
 
Posts: n/a
Default Partition Magic crashes during partition move, resulting in PqRT

Hi
I've googled around and not found much, the best info i got was from
this newsgroup. Among others I've read Svend Olaf Mikkelsen's posts and
they were really great and informative. Though I've tried to learn as
much as possible about the subject, I do not feel secure enough to
simply start try to recover the partition. First i'll ask for some
advice here.

The scenario is as follows:
Harddrive: (80 gb Maxtor 6L0800L4)

initial partitioning:
6gb primary, winxp ntfs
4gb extended, for ext3 and swap
~65gb primary, FAT32 for storage

I wanted to remove the extended partition housing ext3/swap and use it
for storage. Since partition magic 7.0 just said "unknown partition
type" when trying to delete it, i did it from a linux boot disc with
cfdisk. now it looked like:
| 6gb ntfs | 4gb unallocated | 65gb fat32 |

I used PM7 to move the fat32 to the beginning of the space, though,
somewhere in the process the computer rebooted and was not able to find
anything to boot from. Obviously the bootloader or somehing was messed up.

I installed lilo onto the MBR so now i can boot into windows xp, but not
access the large fat32 partition.
The disk is mountable from KNOPPIX (mounted read-only), and i can access
most of the data, but some directories are totally screwed up; filled
with files with long filenames of unreadable characters.

fdisk and cfdisk tells me that the partition type is PqRT and using all
of the space on the disk behind the NTFS partition (what was Unallocated
+ FAT32 partition).

On the powerquest site one is told to simple change the partition type
using PM parted, but postings in this group seems to imply otherwise.

I really hope this is recoverable

Here is the output from findpart:
findpart.exe all fp.txt


OS: Windows 5.1 All

Disk: 1 Cylinders: 10340 Heads: 240 Sectors: 63 MB: 76338

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 07 63 12579777 6142 0 1 1 831 239 63 B OK
-555 - 0C 20971440135369360 66098 832 0 1 9784 239 63 B OK

------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
638 0 2 Second FAT not found.
656 0 33 Second FAT not found.
832 0 33 16548 32 951 16548 0 0 0 02-05-23 57868

Partitions according to partition tables on first harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63 12579777 6142 0 1 1 831 239 63 OK OK
0 3 3C 12579840143760960 70195 832 0 1 10339*239 63 OK

Disk: 2 Cylinders: 256 Heads: 255 Sectors: 63 MB: 2008

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 83 63 584576 285 0 1 1 36 99 62 B5 OK

No FATs found.

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 83 63 584577 285 0 1 1 144 63 63 NB NB
0 1 1 36 99 63 Actual

  #2  
Old July 23rd 03, 11:24 PM
Jonas Carlsson
external usenet poster
 
Posts: n/a
Default

Michael Kimmer wrote:


Run PTEdit32.EXE (as admin) or PTEdit.EXE from the first rescue disk, find
the value $3C under *type* and change it back to the orginal file system
type. Guess it was FAT32, so change it back to $0B). If you cannot find the
$3C directly, click on "Goto EPBR" to find it...(EPBR = Extended Partition
Boot Record).
More info: http://www.powerquest.com/support/primus/id3851.cfm


Well, that seems to be the method which i understood was NOT recommended
when reading old posts to this list. I thought that was a way to get
more data loss than necessary. That recovery should be made by somehow
locating the actual position of the partition and editing the partition
tables or somethings. Does everyone agree that this PTEdit thing is my
best shot?

  #3  
Old July 24th 03, 02:27 PM
Joep
external usenet poster
 
Posts: n/a
Default

PowerQuest PqRP FAQ - July 24 2003 - Joep

** About PqRP: **


* The problem:

As SOON as PartitionMagic (from now on: PM) starts it's operation on a
partition it will 'edit' the partition table and replace the byte that
descibes the type of partition (so FAT (06h), FAT32 (0Bh) etc ...) to byte
value 3Ch. PartitionMagic and all PQ products will display a 3Ch type
partition as PqRP or PQFlex type partition. A PqRP type partition can NOT be
accessed by Windows operating systems (Possibly Linux can). Only when PM
completed the operation it will replace the 3Ch value by the proper value
describing the partition type.

Therefore a PqRP type partition ONLY means that PM was performing a task on
this partition and it didn't get the chance to finish it. It does NOT say
anything regarding the amount of damage in the partition.

SOMETIMES changing the 3Ch value in the partition table to the proper
partition type will help you gain access to the partition again. It highly
depends up on in which stage PM was, if contents of the partition are still
intact. For example PM starts by checking the partition (can sometimes be up
to 10% of total progress), and when it crashes during this stage, where no
'juggling' with data took place yet, editing the partition table alone may
be enough to gain access to the partition again.

Now the whole purpose of 'flagging' the partition this way is to prevent
tools like scandisk 'touching' this partition or to prevent you writing to
it. Running scandisk on a damaged partition may very well render recovery of
data impossible.


* The answer(s)

This group (comp.sys.ibm.pc.hardware.storage) is frequently visited by Svend
Olaf and he nailed down the PqRP problem pretty well (probably he's the
person who knows most about it aside from some PQ developers), he even
studied it to such a degree that he was able to write a tool (PqRP.exe) that
allows you to clasify the amount of damage within the PqRP partition.

His advise often is to leave the 'flag' as it is (3Ch - PqRP) and my guess
is that he advises this because of the same reason the PqRP mechanism exists
in the first place: as long as tools or Windows doesn't recognize a
partition they will not touch it i.e. will not make the damage worse than it
already is. This is good and solid advise!

PQ technical 1st line technical support does not have a clue what_so_ever of
what to do when the Ptedit trick (see below link for PQ KB article) doesn't
work, they just follow the same knowledge base article that is publically
available at the PQ support site (see below). They will refer you to the
manual where it is advised to create a backup before running PM. (NOTE: If
you DO edit the partition table for a FAT16 partition and you find a
'DYN_ROOT' when accessing it, I may be able to help to fix this - I have
written a tool that will fix this automatically - available up on request
only - I will first ask for a partinfo output, see below)

The only chance you have now:

- try the Ptedit trick (see link to PQ KB article below). Make sure to write
NOTHING to the partition, and prevent ALL programs from writing to or
touching the partition! Do NOT run Scandisk or NDD! Safest is to boot a DOS
diskette and try to READ the partition and verify you can access it, access
subfolders and maybe try to open a text file. Under NO circumstances write
to the partition until you have verified all is well! If data is only
partially available, copy the data you can access to ANOTHER physical disk
or removable disk.

- is getting Svend to help you, we all have been witnesses that he
frequently/always DOES recover PqRP partitions intact (at least of the
FAT/FAT32 type). Svend will ask for a findpart output (see below).

- or if you do not want to wait for that try a READ-ONLY commercial data
recovery tool to copy the data to ANOTHER disk. If such a tool succeeds in
recovering your files (verify them FIRST), you can then delete the PqRP
partition and recreate and reformat it. Concentrate on recovering user data
(copying an entire Windows installation and then expecting it to boot is
useles). If you decide to repartition the drive after you have recovered
your data and find PartitionMagic will not run because of partition table
errors see procedure below.

* Web addresses:

PowerQuest PqRP KB article :
http://www.powerquest.com/support/primus/id3851.cfm
PowerQuest's Ptedit program :
ftp://ftp.powerquest.com/pub/utilities/ptedit.zip
PowerQuest's Partinfo program :
ftp://ftp.powerquest.com/pub/utilities/partinfo.zip
Svend's PqRP program : http://inet.uni2.dk/~svolaf/utilities.htm
Svend's Findpart program : http://inet.uni2.dk/~svolaf/utilities.htm
Joep's website (for help with DYN_ROOT): http://www.diydatarecovery.nl


* Procedures:
======================================
PQ KB article:
Solution: Fixing a PQRP with PTEDIT
To fix a PQRP with PTEDIT:

1. Run PTEDIT.

2. Locate the PQRP (partition type 3C).
If the PQRP occurred on a logical partition, click "GoToEPBR" to locate
the correct partition.

3. Click in the "Type" field associated with the 3C partition.

4. Click "Set Type."
A list of available partition types is displayed.

5. Select the appropriate partition type (e.g., FAT32 if the partition type
was FAT32 before the PQRP, etc.).

6. Save the changes and exit.

If the system does not boot properly at this point, run a directory listing
(DIR) on the drive and make sure there are no "DYN_ROOT" entries. A
"DYN_ROOT" indicates that the original root directory has been relocated but
can, in most cases, be restored. If the directory listing appears as random
ASCII code or unrecognizable characters, the partition is likely corrupt and
cannot be recovered.

Note: If the root directory appears as a DYN_ROOT, do not SYS the drive.
Modifications made to the drive while in this state can reduce the
probability of recovery. Contact PowerQuest Technical Support for further
assistance.
======================================



======================================
Running partinfo:

1. Go to a true DOS prompt (not a Windows command prompt).

2. Change to the directory that contains PARTINFO.EXE. (For example, if you
want to run PARTINFO from the PartitionMagic rescue diskettes, insert the
first rescue diskette and change to the A:\ drive.)

3. Type PARTINFO LPT1 (to send the results to the printer) or PARTINFO
A:\PARTINFO.TXT (to save the output as a text file named PARTINFO.TXT to the
root directory), and then press Enter.
======================================


======================================
Running Findpart:

The report can be written to a file. Add the filename to the
command line. File extension must be .txt. To append to current
report file, use +filename.

Example: findpart all fp.txt [enter]
======================================


======================================
Running PartitionMagic while partition table errors are present

ONLY ignore partition table errors if it is your intention to delete the
partitions on the 'BAD' disk. Under NO other circumstances partition table
errors should be ignored!

PartitionMagic may fail to run if partition table errors are present (Disk
is shown as 'BAD'). You can tell PM to ignore partition table errors so you
can at least delete partitions from your harddisk (and by doing so getting
rid of partitions + partition table errors).

To do so run the DOS version of PartitionMagic with the /ipe switch: pqmagic
/ipe [enter].
======================================



* How to prevent dataloss as a result of a PqRP

- BACK UP YOUR DATA!
- Do NOT assume PM is hanging when it seems to have stopped displaying
progress! Toggle the NUMLOCK key and see if the LED toggles on and off, if
so leave PM and let it continue. (I have reproduced situations where it took
FIVE days to merge 2 partitions!)
- Do NOT perform resizes or merging when the partition(s) is/are almost
completely filled up!
- Do NOT merge a 'used' partition with an EMPTY one: instead delete the
empty partition and resize the used partition


* Final note(s):

- Suggestions for a PqRP FAQ are welcome
- remember you will hardly find notice posts how wonderful PM resized
partitions. Almost evry post you'll find will be about a problem of some
kind. This is NOT because PM tends to make partitions F.U.B.A.R., it is
because problems will cause people to seek help and post a message asking
for it. I no use PM for 4,5 years (frequently) and it has never let me down
(knock on wood). Also I have worked for PQ 3rd line support and often PqRPs
were caused by pure stupidity that some people are willing to admit, like
tripping over power cable - power cut - cat jumped on keyboard hitting
CTRL+ALT+DEL - PC fell from table etc.. (I am NOT joking or making this up!)


* Disclaimer: Use this information ON YOUR OWN RISK!


--
Kind regards,
Joep




  #4  
Old July 24th 03, 11:27 PM
hej
external usenet poster
 
Posts: n/a
Default

Joep wrote:
A PqRP type partition can NOT be
accessed by Windows operating systems (Possibly Linux can).


Yes, linux can access it. I mount the partition read-only with
mount -t vfat -o ro /dev/hdXn /mount/point
and thus i can access parts of the data.

  #5  
Old July 24th 03, 11:52 PM
hej
external usenet poster
 
Posts: n/a
Default

Joep wrote:

Thanks I'll add that. Is it possible to mount read only? Or does the 'ro'
stand for read-only? Because I think I'd prefer that to be in the FAQ.

Kind regards,
Joep


You are correct.
"-o ro" stands for "options read-only"
there are a lot of options for mounting, though this may be the most
important. Read man mount.

  #6  
Old August 5th 03, 08:55 AM
Svend Olaf Mikkelsen
external usenet poster
 
Posts: n/a
Default

On Wed, 23 Jul 2003 02:37:20 GMT, Jonas Carlsson
wrote:

Hi
I've googled around and not found much, the best info i got was from
this newsgroup. Among others I've read Svend Olaf Mikkelsen's posts and
they were really great and informative. Though I've tried to learn as
much as possible about the subject, I do not feel secure enough to
simply start try to recover the partition. First i'll ask for some
advice here.

The scenario is as follows:
Harddrive: (80 gb Maxtor 6L0800L4)

initial partitioning:
6gb primary, winxp ntfs
4gb extended, for ext3 and swap
~65gb primary, FAT32 for storage

I wanted to remove the extended partition housing ext3/swap and use it
for storage. Since partition magic 7.0 just said "unknown partition
type" when trying to delete it, i did it from a linux boot disc with
cfdisk. now it looked like:
| 6gb ntfs | 4gb unallocated | 65gb fat32 |

I used PM7 to move the fat32 to the beginning of the space, though,
somewhere in the process the computer rebooted and was not able to find
anything to boot from. Obviously the bootloader or somehing was messed up.

I installed lilo onto the MBR so now i can boot into windows xp, but not
access the large fat32 partition.
The disk is mountable from KNOPPIX (mounted read-only), and i can access
most of the data, but some directories are totally screwed up; filled
with files with long filenames of unreadable characters.

fdisk and cfdisk tells me that the partition type is PqRT and using all
of the space on the disk behind the NTFS partition (what was Unallocated
+ FAT32 partition).

On the powerquest site one is told to simple change the partition type
using PM parted, but postings in this group seems to imply otherwise.

I really hope this is recoverable

Here is the output from findpart:
findpart.exe all fp.txt


OS: Windows 5.1 All

Disk: 1 Cylinders: 10340 Heads: 240 Sectors: 63 MB: 76338

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 - 07 63 12579777 6142 0 1 1 831 239 63 B OK
-555 - 0C 20971440135369360 66098 832 0 1 9784 239 63 B OK

------FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YY-MM-DD DataMB
638 0 2 Second FAT not found.
656 0 33 Second FAT not found.
832 0 33 16548 32 951 16548 0 0 0 02-05-23 57868

Partitions according to partition tables on first harddisk:

--PCyl N ID -----Rel -----Num ---MB --Start CHS- ---End CHS-- BS CHS
0 1 07 63 12579777 6142 0 1 1 831 239 63 OK OK
0 3 3C 12579840143760960 70195 832 0 1 10339*239 63 OK

Disk: 2 Cylinders: 256 Heads: 255 Sectors: 63 MB: 2008

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 - 83 63 584576 285 0 1 1 36 99 62 B5 OK

No FATs found.

Partitions according to partition tables on second harddisk:

-PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS CHS
0 1 83 63 584577 285 0 1 1 144 63 63 NB NB
0 1 1 36 99 63 Actual


I can confirm that the case was solved. It took some days due to
vacations and bad sectors, but it was solved.

And I can confirm that the ptedit method would not have solved the
case.
--
Svend Olaf
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
make your own Restore partition Timothy Daniels Dell Computers 1 August 27th 04 11:01 PM
Hard drive woes Lil' Abner General 10 April 10th 04 05:53 AM
2nd Hard Drive Disappears After Standby/hibernatio, Partition Magic Issue? wrt General 1 December 5th 03 08:20 PM
Boy am I in deep doo doo! Partition Magic 5.0 Michael P Gabriel General Hardware 1 November 26th 03 02:28 AM
USING PARTITION MAGIC 8.01 TO FORMAT A 200GIG DRIVE SAFE ? WHY DO FAST Andy Louie Storage (alternative) 0 July 10th 03 10:14 PM


All times are GMT +1. The time now is 03:44 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2022, Jelsoft Enterprises Ltd.
Copyright 2004-2022 HardwareBanter.
The comments are property of their posters.