after much searching, new hard drive still not found
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
after much searching, new hard drive still not found
Hi,
This computer used to be a dual-boot Windows 2000 Prof. and Mandrake 9.0, with 1 20-Gb drive as the bootable drive and 2 20-Gb disks on a Hpt RAID-0 array. (I never tried to get Linux to see the raid disks - they were NTFS and worked better as Windows-only.)
I just recently deleted Windows off the system entirely and broke up the raid array since I had no further use for windows and could use the drives better elsewhere. One of them has never been formatted by itself, and I would like to put it back in this system as the slave hdd. However, when I try this, the BIOS has no problems - it finds 2 20-Gb drives in a Master/Slave arrangement, and linux boots fine....but I can't actually _see_ the slave drive!
I've read posts where the fstab configuration could be ignoring the existance of a /dev/hdb drive because of cd-rom arrangements, etc, and I don't believe that's the problem:
No luck either with trying random "fdisk /dev/hd*" commands, either (I've tried up to replacing the '*' with everything from 'a', which is my primary hdd and the only one that works, through 'f')
As requested by finegan:
Code:
$ /usr/bin/lspcidrake
unknown : VIA Technologies|VT8367 [KT266]
unknown : VIA Technologies|VT8367 [KT266 AGP]
ne2k-pci : Realtek|RTL-8029(AS)
audigy : Creative Labs|EMU10K2 Audigy Audio Processor
emu10k1-gp : Creative Labs|EMU10K2 Audigy Gameport
ohci1394 : Creative Labs|EMU10K2 Audigy IEEE1394 Firewire Controller
unknown : VIA Technologies Inc|VT8233 PCI to ISA Bridge
unknown : VIA Technologies|VT82C586 IDE [Apollo]
usb-uhci : VIA Technologies|VT82C586B USB
usb-uhci : VIA Technologies|VT82C586B USB
hptraid : Triones|HPT366
Card:ATI Radeon : ATI|Radeon QY
unknown : Virtual|Hub []
unknown : Virtual|Hub []
unknown : Chic Technology Corp.|PS2/USB Browser Combo Mouse [Human Interface Devices|Boot Interface Subclass|Mouse]
unknown : Lexmark|Inkjet color printer [Printer|Printer|Bidirectional]
My dmesg output is posted on a temp website so I don't take up half the page here.
What am I missing?
Laura
OK, has /dev/hdb been formatted with a file system yet? IE..ext2, 3 or reiserfs?? according to dmesg, your system recognizes both of your drives Quote... hda: MAXTOR 6L020J1, ATA DISK drive
hdb: MAXTOR 6L020J1, ATA DISK drive
but without a formatted file system the drive will not be mounted.
Linux does not mount a drive by itself, there needs to be a file system that is recognized......
Ahh! No, I haven't formatted it yet. The filesystem as it currently stands is 1/2 of a raid array and definitely unrecognizable by an OS. Ok - after I format it, should I let linux find it first, or put the line in /etc/fstab first? (Not quite sure which is the chicken and which is the egg...)
Hi,
As a newbie, I have a question.
I thought that you should be able to access a new harddrive with the fdisk command. It should not have to be mounted. If it is setup as a slave on the primary IDE, then the command:
fdisk /dev/hdb
should do it.
Here is where I get lost. In looking at your dmesg info, I notice that you have a line setting up /dev/hdb for SCSI emulation. I have a similar line for /dev/hdc, but it is for my CD-Writer. Is this line needed for your harddrive? It appears to be causing problems later on in the dmesg log.
Hi! No, you're right. I thought the same about fdisk, frankly, and I'm still mystified. However, the drive set up for SCSI emulation is my cd burner....I don't know where the /dev/hdb assignment came from....
My system as it is now looks like this:
Primary master: the working hard drive (/dev/hda)
Primary slave: the non-found hard drive (not found)
Secondary master: CD-ROM (/dev/hdc)
Secondary slave: cd-burner (/dev/scsi0)
Is there any way to change where it assigns /dev/hdb??
Hi,
I do not know enough about this to give advice. I can tell you how it is done on my machine.
I use lilo (not grub or anything else, so this may not be for you.)
In my /etc/lilo.conf file is a line that says
append="hdc=ide-scsi"
I believe this is what tells my machine to use SCSI emulation on my CD-Writer.
If you use lilo, you might look for a line that says
append="hdb=ide-scsi"
You might try commenting out that line.
After that you would have to run /sbin/lilo and (I think) reboot.
I may be in a little over my head.
Oh, wait...I just had a thought:
Since this hard drive was out of a raid-0 array, it doesn't have a valid partition table of its own at all - might that be the reason fdisk "can't read device"?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.