Pmount issue - Puppy 2.02 live CD
-
- Posts: 54
- Joined: Fri 25 Aug 2006, 03:55
Pmount issue - Puppy 2.02 live CD
I have Puppy 1.07 installed on the hard disk of an old PC. It works just fine. The hard disk has three partitions: one VFat, one Ext2fs, one Swap.
I popped the Puppy 2.02 into the CD drive to test the new Puppy and tried to mount the hard drive by invoking Pmount, but no go. It appears Pmount is attempting to mount, but seems to acting like it's in some kind of loop and can't get out. There is a small orange dialogue box that flashes on the monitor, but it flashes too quickly for me to read the text.
Has anyone else run into this problem and is there a way of fixing it?
Mark
I popped the Puppy 2.02 into the CD drive to test the new Puppy and tried to mount the hard drive by invoking Pmount, but no go. It appears Pmount is attempting to mount, but seems to acting like it's in some kind of loop and can't get out. There is a small orange dialogue box that flashes on the monitor, but it flashes too quickly for me to read the text.
Has anyone else run into this problem and is there a way of fixing it?
Mark
-
- Posts: 54
- Joined: Fri 25 Aug 2006, 03:55
Might be a corrupted partition table or something scary like that. You can tell fdisk to list your partitions by typing: fdisk -l in a console. Here's what mine looks like:
sh-3.1# fdisk -l
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 2575 20683656 c W95 FAT32 (LBA)
/dev/hda2 2576 2587 96390 83 Linux
/dev/hda3 3804 4870 8570677+ 5 Extended
/dev/hda4 2588 3803 9767520 83 Linux
/dev/hda5 3804 3865 497983+ 82 Linux swap / Solaris
/dev/hda6 3866 4870 8072631 83 Linux
Partition table entries are not in disk order
What happens if you boot your old version of Puppy now - can it still see the partitions?
Bill
sh-3.1# fdisk -l
Disk /dev/hda: 40.0 GB, 40060403712 bytes
255 heads, 63 sectors/track, 4870 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 2575 20683656 c W95 FAT32 (LBA)
/dev/hda2 2576 2587 96390 83 Linux
/dev/hda3 3804 4870 8570677+ 5 Extended
/dev/hda4 2588 3803 9767520 83 Linux
/dev/hda5 3804 3865 497983+ 82 Linux swap / Solaris
/dev/hda6 3866 4870 8072631 83 Linux
Partition table entries are not in disk order
What happens if you boot your old version of Puppy now - can it still see the partitions?
Bill
-
- Posts: 54
- Joined: Fri 25 Aug 2006, 03:55
-
- Posts: 54
- Joined: Fri 25 Aug 2006, 03:55
Okay, here's what the result when I do the fdisk -l in a console:
Disk /dev/hda: 1702 MB, 1702365696 bytes
64 heads, 63 sectors/track, 824 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 51 102784+ 6 FAT16
/dev/hda2 * 52 661 1229760 83 Linux
/dev/hda3 662 824 328608 82 Linux swap / Solaris
I'm no expert with interpreting this result. Does this help explain any possible problem?
Mark
Disk /dev/hda: 1702 MB, 1702365696 bytes
64 heads, 63 sectors/track, 824 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 51 102784+ 6 FAT16
/dev/hda2 * 52 661 1229760 83 Linux
/dev/hda3 662 824 328608 82 Linux swap / Solaris
I'm no expert with interpreting this result. Does this help explain any possible problem?
Mark
-
- Posts: 54
- Joined: Fri 25 Aug 2006, 03:55
Okay, there's something weird going on.......
When I use the fdisk -l command under Puppy 1.07, which is installed on the HD, I get the following results (posted earlier):
Disk /dev/hda: 1702 MB, 1702365696 bytes
64 heads, 63 sectors/track, 824 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 51 102784+ 6 FAT16
/dev/hda2 * 52 661 1229760 83 Linux
/dev/hda3 662 824 328608 82 Linux swap / Solaris
Then, when I reboot the same machine and pop the Puppy 2.02 into the CD drive, let the newer Puppy boot, then issue the fdisk -l command,
I get this result:
Disk /dev/hda: 1702 MB, 1702397952 bytes
16 heads, 63 sectors/track, 3298 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 3297 1661683+ 54 OnTrackDM6
When I try to use gParted under 2.02, it states that the filesystem of the HD is unknown.
I've rebooted the machine with SystemRescue disk inserted and checked the partitions using qtParted, and it confirms what 1.07 is telling me is on the HD (three partitions: Vfat, Linux, & Swap).
Anyone have any idea why I am getting this strange behavior between the two versions of Puppy? I am guessing I would be unable to install Puppy 2.02 to the HD as a replacement to 1.07 until I get this HD issue resolved.
Any suggestions?
Mark
When I use the fdisk -l command under Puppy 1.07, which is installed on the HD, I get the following results (posted earlier):
Disk /dev/hda: 1702 MB, 1702365696 bytes
64 heads, 63 sectors/track, 824 cylinders
Units = cylinders of 4032 * 512 = 2064384 bytes
Device Boot Start End Blocks Id System
/dev/hda1 1 51 102784+ 6 FAT16
/dev/hda2 * 52 661 1229760 83 Linux
/dev/hda3 662 824 328608 82 Linux swap / Solaris
Then, when I reboot the same machine and pop the Puppy 2.02 into the CD drive, let the newer Puppy boot, then issue the fdisk -l command,
I get this result:
Disk /dev/hda: 1702 MB, 1702397952 bytes
16 heads, 63 sectors/track, 3298 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id System
/dev/hda1 * 1 3297 1661683+ 54 OnTrackDM6
When I try to use gParted under 2.02, it states that the filesystem of the HD is unknown.
I've rebooted the machine with SystemRescue disk inserted and checked the partitions using qtParted, and it confirms what 1.07 is telling me is on the HD (three partitions: Vfat, Linux, & Swap).
Anyone have any idea why I am getting this strange behavior between the two versions of Puppy? I am guessing I would be unable to install Puppy 2.02 to the HD as a replacement to 1.07 until I get this HD issue resolved.
Any suggestions?
Mark
-
- Posts: 54
- Joined: Fri 25 Aug 2006, 03:55
AACCKKK!!!! The weirdness is further confirmed.
Just for the heck of it, I tried another partition manager (Ranish) to see how it viewed my HD partitions, and it agrees with what gParted in Puppy 2.02 is detecting!!!
I fear the best thing is to totally wipe this hard drive and start over, unless someone else has other suggestions...........
Mark
Just for the heck of it, I tried another partition manager (Ranish) to see how it viewed my HD partitions, and it agrees with what gParted in Puppy 2.02 is detecting!!!
I fear the best thing is to totally wipe this hard drive and start over, unless someone else has other suggestions...........
Mark
Your disk was partitioned with OnTrack's Disk Manager software. When booting from this harddisk, a driver is loaded which allows your OS to see DM's "special" partitioning. Short of a Linux OnTrack driver, the only way to boot Puppy from CD and use this disk as is would be a DM boot floppy./dev/hda1 * 1 3297 1661683+ 54 OnTrackDM6
If I were you, I would wipe the disk and start over as you say.
I would try to figure out why Disk Manager was used in the first place. Check out the disk statistics in teh bios before making any changes.fluxit wrote:Your disk was partitioned with OnTrack's Disk Manager software. When booting from this harddisk, a driver is loaded which allows your OS to see DM's "special" partitioning. Short of a Linux OnTrack driver, the only way to boot Puppy from CD and use this disk as is would be a DM boot floppy./dev/hda1 * 1 3297 1661683+ 54 OnTrackDM6
If I were you, I would wipe the disk and start over as you say.
Unless the hard disk has been transferred from an older machine you still might have the same problem, bios not being able to see the entire capacity of the HDD.