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.
Distribution: open SuSE 10.3, heavily modified...;)
Posts: 13
Rep:
Undetected hard-drives on NZXT Alpha
Just got a NZXT Alpha. It came with 1 SATA drive, and when I tried to install (SuSE 10.3, 64-bit DVD), installation failed becasue the hard drive was not detected. I installed a working hard drive, one of my old ones, also SATA and tried to start installation again, but now neither one of the drives is detected. Everything else seems to be found just fine. Any ideas?
Distribution: open SuSE 10.3, heavily modified...;)
Posts: 13
Original Poster
Rep:
An update: BIOS finds all the drives no problem, for some reason they are on IDE Channel 2. SuSE and Knoppix both fail at finding them, though, even though Knoppix finds an external eSATA drive no problem (and that one is on Ch 1 somehow). When booting from my old drive (the one I added), the drive is found, but then the boot process breaks down since grub is looking for the drive in the wrong place. But what is the right one? If I knew, I'd edit grub menu and fstab, but in rescue mode I cannot find either drive.
Distribution: open SuSE 10.3, heavily modified...;)
Posts: 13
Original Poster
Rep:
More updates: tried to boot from grub command line. The problem is that I cannot get the device name for the drive. The kernel is found with grub> find /boot/vmlinuz; then the device appears as hd(0,0), so all would seem to be good, but upon issuing "boot", it ends up with:
VFS: Cannot open root device "<NULL>" or unknown-block(8,13)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,13)
Distribution: open SuSE 10.3, heavily modified...;)
Posts: 13
Original Poster
Rep:
And yet another update and a happy conclusion: Ubuntu 8.0.1 found all the drives and is installing as I type this. Goody. Now I have to learn Ubuntu package handling, so I can bring this system up to the level of awesomeness it deserves.
My view is the disk (or disks) is there all the time. You just haven't got any proof it wasn't there as you showed none. May be you rely it from the desktop and didn't do a "fdisk -l".
My point is your definition of undetected hard disk may be different from us.
Distribution: open SuSE 10.3, heavily modified...;)
Posts: 13
Original Poster
Rep:
Quote:
Originally Posted by saikee
My view is the disk (or disks) is there all the time. You just haven't got any proof it wasn't there as you showed none. May be you rely it from the desktop and didn't do a "fdisk -l".
My point is your definition of undetected hard disk may be different from us.
Um, what proof? The SuSE installer failed with "no hard drives found". Knoppix booted happily and saw neither of the disks. fdisk is irrelevant, since one of the drives was already ext3 with a system that functioned in a previous computer. My question was: how do I find out the device name? (They turned out to be /dev/sda and /dev/sdb just as I suspected, but it was certainly a driver issue: much as I love to insult Ubuntu, in this case it beat all competition. Trying to mount them from SuSE or Knoppix came up with "no drive found")
I fail to see what desktops have to do with it since the best I could get was a grub command line up to stage 2 and then failure, and nothing at all in Knoppix.
Since I am typing this on the new machine, something obviously worked and I could have saved everyone a toxic dump of trouble. On the other hand, not too many people seem to have troubled...
In the above I used an installed Suse 10.1 (about 2 years old) with 2.6.13 kernel. At that time Linux allowed Pata disks to have 63 partitions. Now all disks are permitted 15 partitions only as my Sata sda.
There are many ways to install Suse. If you select an alternative to install Suse into the empty space of a hard disk but none of the disks have any then Suse installer could report no such disk found. On the other hand if you choose expert mode and specify which partition Suse to be installed then any of the partitions showed up in fdisk can be used for installation.
The box I am using has 150+ Oses. Three of them are Suse (V10.1_x64, 10 and 9.1). You should only claim the disk not detected if it is not show up in the "fdisk -l".
If a raw disk, direct from a purchase and has no partition inside, is present it will show up in fdisk. If a partition has been created but not formatted it will still show up in fdisk but can't in the desktop because without a filing system inside it cannot be mounted. Thus fdisk is the command to see all your hard disks.
If the disk is not shown in "fdisk -l" then it would be likely a hardware fault; either the disk cannot be read because it is corrupted so badly or there is a loose connection (or a wrong jumpered position) resulting the Bios cannot detect it and the kernel cannot establish it.
If one Linux kernel can see it then all other Linux kernel and operating systems can see it too. Nothing wrong with the distros.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.