rbw wrote:
I'm stuck... maybe someone has seen this before...
I have a PIII 450 PC with a 160Gb Western Digital HD which is managed by
"Dynamic Drive Overlay v9.88" by OnTrack. I need to run Knoppix (v5.0.1
or v5.1.1) and mount that HD. Supposedly the solution is to ad the
following parameter when booting Knoppix like so:
knoppix hda=remap63
see:
8.7 Since 2.5.70: boot parameters
In 2.5.70 the automatic disk manager support was removed. Instead, two
boot options were added: "hda=remap" to do the EZ-Drive remapping of
sector 0 to sector 1, and "hda=remap63" to do the OnTrack Disk Manager
shift over 63 sectors.
http://tldp.org/HOWTO/Large-Disk-HOWTO-8.html
http://www.knoppix.net/forum/viewtopic.php?t=26522&highlight=
I end up with /dev/hda mounted but it is mapped to /dev/cdrom which ends
up being a duplicate of the /KNOPPIX mount.
[EMAIL PROTECTED]:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 3471 22 3449 1% /
/dev/hda 713064 713064 0 100% /cdrom
/ramdisk 204068 4612 199456 3% /ramdisk
/UNIONFS 204068 4612 199456 3% /UNIONFS
/dev/hdc 713064 713064 0 100% /cdrom
/dev/cloop 1997852 1997852 0 100% /KNOPPIX
/dev/sda1 997844 43708 954136 5% /media/sda1
Once starting knoppix with the hda=remap63 parameter, fdisk -l /dev/hda
shows:
[EMAIL PROTECTED]:~# fdisk -l /dev/hda
Disk /dev/hda: 164.6 GB, 164696523264 bytes
255 heads, 63 sectors/track, 20023 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
This doesn't look like a partition table
Probably you selected the wrong device.
Device Boot Start End Blocks Id System
/dev/hda1 ? 13578 119522 850995205 72 Unknown
Partition 1 does not end on cylinder boundary.
/dev/hda2 ? 45382 79243 271987362 74 Unknown
Partition 2 does not end on cylinder boundary.
/dev/hda3 ? 10499 10499 0 65 Novell Netware 386
Partition 3 does not end on cylinder boundary.
/dev/hda4 167628 167631 25817+ 0 Empty
Partition 4 does not end on cylinder boundary.
Partition table entries are not in disk order
[EMAIL PROTECTED]:~# fdisk -l /dev/hdb
[EMAIL PROTECTED]:~#
TIA!
rbw
My experience is to never, ever, never EVERNEVER run such disk
managers.They're written for clueless consumers for I don't know what
reason. If your BIOS doesn't support large volumes, you're better off
scrapping the mobo than munging your disk system with this type of
software sorcery.
I've yet to find any of these things not end in so much hassle at some
point hindsight showed a new motherboard would have saved both time and
money.
I suggest you nuke the drive with the manufacturer's drive tools and do
it the right way.
The only reason not to (which if true, you didn't make clear) is if you
need to recover irreplaceable data from the drive. In that case, good luck.
--
Best Regards,
~DJA.
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
