This is a discussion on New 250 GB boot disk for Slackware 8.1 within the Slackware Linux Support forums, part of the Unix Operating Systems category; --> For some reason groups.google.com isn't letting me reply to any other messages in the original chain than the "troll ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| For some reason groups.google.com isn't letting me reply to any other messages in the original chain than the "troll trash" tacked on to the end of the discussion: New 250 GB boot disk for Slackware 8.1 http://groups-beta.google.com/group/...inux.slackware /tree/browse_frm/thread/1aa8916a817299d3/825a21f8b8fbd14a > 120 GB should work OK for sure, but disks bigger than > 137 GB might give problems unless he upgrades to a > newer kernel. Slackware 8.1 came with kernel 2.4.18. I > don't remember when 48-bit LBA got into the kernel, maybe > it was in 2.4.18, I for sure know that it is at least > included in kernel 2.4.22. > > Older kernels will still be able to use those big disks, > but they will only see 137.4 GB. Other poster: > But what about the bios if it doesn't support the 48-bit > addressing, will it be able to boot from it ? Anyway, see the thread ... The 200 GB hard drive was added a few days ago to our Slackware 8.1 system. The kernel was patched to 2.4.31 to support the drive. BIOS updated to 3.14 on the hardware (Dell midtower Optiplex? PIII 1GHZ? system). When the hard drive was added as a single drive/partition it showed up as only 68 GB for some reason. Breaking it up as two separate partitions (96GB/100GB) worked, so that is what we went with. I'm not sure if the Wintel server guys configured this box to boot off of the 200 GB drive or not, sorry. I'll see if I can get them to give me better fdisk output than that below or otherwise comment. Here's df and fdisk (crippled) output: $ df -k Filesystem 1k-blocks Used Available Use% Mounted on /dev/hda1 8055288 5001132 2638360 66% / /dev/hdd1 115380192 103987892 5531264 95% /storage/primary /dev/hdb1 115380192 68550096 40969060 63% /storage/secondary /dev/hdc1 94256612 8 89468608 1% /storage/dump1 /dev/hdc2 98038004 8 93057948 1% /storage/dump2 $ /sbin/fdisk -l Cannot open /dev/hdc Cannot open /dev/hdd Cannot open /dev/hda Cannot open /dev/hdb I want to thank everyone who commented! - Pete |
| ||||
| Here's the better fdisk output: # fdisk -l Disk /dev/hdc: 16 heads, 63 sectors, 387621 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hdc1 1 190000 95759968+ 83 Linux /dev/hdc2 190001 387621 99600984 83 Linux Disk /dev/hdd: 16 heads, 63 sectors, 232581 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hdd1 1 232581 117220792+ 83 Linux Disk /dev/hda: 240 heads, 63 sectors, 1292 cylinders Units = cylinders of 15120 * 512 bytes Device Boot Start End Blocks Id System /dev/hda1 1 1100 8315968+ 83 Linux /dev/hda2 1101 1292 1451520 82 Linux swap Disk /dev/hdb: 16 heads, 63 sectors, 232581 cylinders Units = cylinders of 1008 * 512 bytes Device Boot Start End Blocks Id System /dev/hdb1 1 232581 117220792+ 83 Linux # # The drive that was added is /dev/hdc/ . # # Neither of those partitions are the boot partition. # |
| Thread Tools | |
| Display Modes | |
|
|