Adding a hard disk

mastahnke · 11-24-2002, 07:56 PM

I used to have two cdroms and two hdisks in my linux box. I recently got a new HD and I want to add it. I removed a cdrom drive and placed this new disk on the secondary master ide chain. I have tried fdisk -l /dev/hdc and it gets an error. This disk should have mountable filesystems, as it was a linux installation on another box I own. What can I do and not erase the data? It is in a swapbay and I would like to be able to change hard drives very easily if that is possible.

--mIKE

michaelk · 11-24-2002, 10:45 PM

Are you sure you have the IDE jumpers set correctly?

mastahnke · 11-25-2002, 02:43 AM

The bios recognizes all the disks. So, yeah, I think so.

michaelk · 11-25-2002, 08:03 AM

So what are the errors?

mastahnke · 11-25-2002, 09:24 PM

I can't recognize the disk, or I don't know how to. I can't mount the disk, I can't use the disk. Not so much errors, it could just be I don't know exactly what I am doing.

MasterC · 11-25-2002, 09:27 PM

You said it was on another linux box, so try mounting it at any mount point using the previously used filesystem. Here's an example, and assumes ext2:
mkdir /mnt/newhd
mount -t ext2 /dev/hdc1 /mnt/newhd

BTW, just try 'fdisk -l' not specifying ANY hard drives, and make sure you are root.

Cool

mastahnke · 11-26-2002, 12:10 AM

I have tried the fdisk -l
and it shows nothing from this disk. It shows my two other disks, but not this one. Mounting it doesn't work either.

I think if Mandrake could see it, I could work with it.

born4linux · 11-26-2002, 01:16 AM

try this:

dmesg | grep hd

You should be able to see your IDE drives. Now, if all your hard drives are there, you should be able to access it in your system. Also, your two cdroms - are they not scsi emulated?

mastahnke · 11-26-2002, 05:29 PM

This is the message I get when I try that. It appears as though there is a problem with HDC. I am not sure if it is because the IDE device was a cdrom and scsi emulated or another reason. I am going to try booting off of that hd in another box and make sure it is still ok.

_______________________________________________

dmesg | grep hd
Kernel command line: auto BOOT_IMAGE=linux ro root=305 devfs=mount hdc=ide-scsi hdd=ide-scsi
ide_setup: hdc=ide-scsi
ide_setup: hdd=ide-scsi
ide0: BM-DMA at 0xa800-0xa807, BIOS settings: hda

MA, hdb

MA
ide1: BM-DMA at 0xa808-0xa80f, BIOS settings: hdc

MA, hdd

MA
hda: WDC AC420400D, ATA DISK drive
hdb: IBM-DHEA-38451, ATA DISK drive
hdc: WDC WD800BB-75CAA0, ATA DISK drive
hdd: CW038D ATAPI CD-R/RW, ATAPI CD/DVD-ROM drive
hda: 39876480 sectors (20417 MB) w/1966KiB Cache, CHS=2482/255/63, UDMA(33)
hdb: 16514064 sectors (8455 MB) w/472KiB Cache, CHS=1027/255/63, UDMA(33)
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: DMA disabled
hdd: DMA disabled
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc: status error: status=0x51 { DriveReady SeekComplete Error }
hdc: status error: error=0x04 { DriveStatusError }
hdc : bad access: block=0, count=8
end_request: I/O error, dev 16:00 (hdc), sector 0
hdc : bad access: block=2, count=6
end_request: I/O error, dev 16:00 (hdc), sector 2
hdc : bad access: block=4, count=4
end_request: I/O error, dev 16:00 (hdc), sector 4
hdc : bad access: block=6, count=2
end_request: I/O error, dev 16:00 (hdc), sector 6
hdc : bad access: block=0, count=8
end_request: I/O error, dev 16:00 (hdc), sector 0
hdc : bad access: block=2, count=6
end_request: I/O error, dev 16:00 (hdc), sector 2
hdc : bad access: block=4, count=4
end_request: I/O error, dev 16:00 (hdc), sector 4
hdc : bad access: block=6, count=2
end_request: I/O error, dev 16:00 (hdc), sector 6
hdc : bad access: block=0, count=8
end_request: I/O error, dev 16:00 (hdc), sector 0
hdc : bad access: block=2, count=6
end_request: I/O error, dev 16:00 (hdc), sector 2
hdc : bad access: block=4, count=4
end_request: I/O error, dev 16:00 (hdc), sector 4
hdc : bad access: block=6, count=2
end_request: I/O error, dev 16:00 (hdc), sector 6

michaelk · 11-26-2002, 06:35 PM

You are correct.

So I think you need to change the bootloader to not pass the parameter to the kernel.

mastahnke · 11-26-2002, 11:07 PM

That sounds like a plan....how? I am not very bootloader savvy. (LILO)

MasterC · 11-27-2002, 02:01 AM

Post your /etc/lilo.conf file here, but I think you'll just need to remove the entries in the append line for the /dev/hdc

Cool

mastahnke · 11-27-2002, 02:29 PM

boot=/dev/hda
map=/boot/map
default=linux
keytable=/boot/us.klt
prompt
nowarn
timeout=100
message=/boot/message
menu-scheme=wb:bw:wb:bw
image=/boot/vmlinuz
label=linux
root=/dev/hda5
initrd=/boot/initrd.img
append="devfs=mount hdc=ide-scsi hdd=ide-scsi"
read-only
image=/boot/vmlinuz
label=failsafe
root=/dev/hda5
initrd=/boot/initrd.img
append="devfs=nomount hdc=ide-scsi hdd=ide-scsi failsafe"
read-only
other=/dev/fd0
label=floppy
unsafe
~

Thanks for any help!

MasterC · 11-27-2002, 03:21 PM

Ok, so remove the lines there in each append line:
hdc=ide-scsi

Then save and rerun lilo:
/sbin/lilo -v

Restart, and cross your fingers

Cool

mastahnke · 11-27-2002, 04:11 PM

Your last idea works. Now I have my drive over there. Thank you very much for your help.

This site rocks once again.

MIKE