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.
So today my PC completely froze. After the reboot i stuck in an infinite loop trying to boot into emergency mode.
I suspected an fstab issue, so booted with a live USB stick to fix it, but my HDD didn't show up in /dev/xxxx nor in blkid's output.
(my external hard drive was detected without problems)
That's possible. It could be damaged, or a file corrupt. The motherboard or power supply could be the issue. Boot with whatever you can - install cd or whatever, and post the output of
Quote:
ls -l /dev/disk/by-id
Also check logs for disk errors. A disk vanishing is awful like a plug pulled out - check for that. Oh, if the cdrom and hard disk are on the same cable, pull the other one.
Look in the bios and see if bios recognises the internal hardrive.
Some bioses have a checker built in.
I have used in a live session as root in terminal
Code:
smartctl -a /dev/sdx | less
where x= the letter name of drive given in blkid or fdisk -l or lshw
This is pretty catastrophic.
Either you have no disk driver (a)in software or (b) in hardware
You are booting from usb? have you checked dmesg and /var/log/messages for hardware errors? Do they sit up and say hello?
Yes, i'm booting from USB.
The HDD which doesn't working now was the one i used to boot, so i can access only the live system's logs (which is running from USB).
I'm pretty sure it's not a software issue, booted into a Debian installer and it didn't recognize my internal HDD (at the part where i have to set up the partitions).
Since my optical drive isn't detected either i think it could be the SATA controller.
Tried different SATA ports, the result is the same.
That's my external HDD, which is connected via USB.
edit:
It was an fstab issue after all
For some reason the Debian live system (which i booted from USB) didn't recognize the SATA devices. Now i guess it was missing the appropriate drivers. I gave Puppy Linux a try and it detected my HDD, so i could fix fstab.
Thanks for all the replies!
Last edited by earthw0rmjim; 07-26-2014 at 09:42 AM.
That's my external HDD, which is connected via USB.
And called /dev/sda and linux partition /dev/sda1.
That is a wonderment.
Maybe because internal drive is not seen so lshw gives it sda instead of sdb,sdc,sde,sdf.
Quote:
In BIOS both my internal HDD and optical drive are detected as SATA devices. I'm kinda confused now. So they're not detected anywhere else but in BIOS. What could this mean?
To me, that they are not fubar. Usually bios is the beginning so if seen there. You can work your way up from there.
This thread is beyond my level of expertise though, because bios sees drives but live session does not.
I am stumped like you.
Edit: Glad you got it sorted but a installed bad /etc/fstab entry should not have had any relevance in a live session. So I am getting on the bike and cruising for the rest of the morning.
@nd edit: Must have been a old Debian kernel I guess.
3rd edit: Sure would be cool to see
Code:
cat /etc/fstab
for future readers. Mark thread as solved with thread tools above your 1st post to be helpful also.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.