LinuxQuestions.org
Help answer threads with 0 replies.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 11-24-2002, 06:56 PM   #1
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Rep: Reputation: 15
Adding a hard disk


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
 
Old 11-24-2002, 09:45 PM   #2
michaelk
Moderator
 
Registered: Aug 2002
Posts: 21,802

Rep: Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250
Are you sure you have the IDE jumpers set correctly?
 
Old 11-25-2002, 01:43 AM   #3
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
The bios recognizes all the disks. So, yeah, I think so.
 
Old 11-25-2002, 07:03 AM   #4
michaelk
Moderator
 
Registered: Aug 2002
Posts: 21,802

Rep: Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250
So what are the errors?
 
Old 11-25-2002, 08:24 PM   #5
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
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.
 
Old 11-25-2002, 08:27 PM   #6
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 69
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
 
Old 11-25-2002, 11:10 PM   #7
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
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.
 
Old 11-26-2002, 12:16 AM   #8
born4linux
Senior Member
 
Registered: Sep 2002
Location: Philippines
Distribution: Slackware, RHEL&variants, AIX, SuSE
Posts: 1,127

Rep: Reputation: 49
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?
 
Old 11-26-2002, 04:29 PM   #9
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
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: hdaMA, hdbMA
ide1: BM-DMA at 0xa808-0xa80f, BIOS settings: hdcMA, hddMA
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
 
Old 11-26-2002, 05:35 PM   #10
michaelk
Moderator
 
Registered: Aug 2002
Posts: 21,802

Rep: Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250Reputation: 4250
You are correct.

So I think you need to change the bootloader to not pass the parameter to the kernel.
 
Old 11-26-2002, 10:07 PM   #11
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
That sounds like a plan....how? I am not very bootloader savvy. (LILO)
 
Old 11-27-2002, 01:01 AM   #12
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 69
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
 
Old 11-27-2002, 01:29 PM   #13
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
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!
 
Old 11-27-2002, 02:21 PM   #14
MasterC
LQ Guru
 
Registered: Mar 2002
Location: Salt Lake City, UT - USA
Distribution: Gentoo ; LFS ; Kubuntu
Posts: 12,612

Rep: Reputation: 69
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
 
Old 11-27-2002, 03:11 PM   #15
mastahnke
Member
 
Registered: Feb 2002
Location: IL
Distribution: Ubuntu currently, also Fedora, RHEL, CentOS
Posts: 111

Original Poster
Rep: Reputation: 15
Thanks!

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

This site rocks once again.

MIKE
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

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

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
adding new hard disk jkmartha Linux - Newbie 3 08-19-2005 01:09 AM
GRUB - adding new hard disk gedi1 Linux - General 2 06-16-2004 07:16 PM
Problems adding a hard disk dirxx Linux - Hardware 1 05-10-2004 10:57 AM
adding a hard disk after instalation (slackware) kyoukan Linux - Software 0 05-10-2003 08:02 PM
Adding a hard disk in Mandrake aizkorri Linux - General 3 03-26-2002 03:27 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 04:21 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration