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.
My box was acting funny so I decided to reboot it. When it started coming up I get about 20 lines of this:
Buffer I/O error on device hda2, Logical block 0
Buffer I/O error on device hda2, Logical block 1
Buffer I/O error on device hda2, Logical block 2
Buffer I/O error on device hda2, Logical block 3
Buffer I/O error on device hda2, Logical block 4
Buffer I/O error on device hda2, Logical block 5
Buffer I/O error on device hda2, Logical block 6
Buffer I/O error on device hda2, Logical block 7
Buffer I/O error on device hda2, Logical block 0
Buffer I/O error on device hda2, Logical block 1
Buffer I/O error on device hda2, Logical block 2
Buffer I/O error on device hda2, Logical block 3
Buffer I/O error on device hda2, Logical block 4
Buffer I/O error on device hda2, Logical block 5
Buffer I/O error on device hda2, Logical block 6
Buffer I/O error on device hda2, Logical block 7
mkrootdev: label / not found
mount:error 2 mounting ext3
pivotroot: pivot_root (/sysroot,/sysroot,init) failed :2
umount /initrd/proc failed :2
kernel panic: no init found. Try passing Init= option to kernel
It looks like it can't read my fstab file or something. Is there any way to get the fstab working if that's the case? When I try and load the Fedora 3 rescue disk it says that it can't find any partitions. The BOIS isn't reporting it as a bad drive or anything and if I do a badblocks test it spins the drive with no errors.
I did try and fsck and an e2fsck and they both fail saying something about possible zero lenth or something. I'm starting to doubt myself now because I made a change to the FSTAB file earlier and starting to wonder if that change broke it. Are there tools to recover or create a new FSTAB file?
I think I know what my problem is. I found somewhere that if you're getting a pivotroot: pivot_root (/sysroot,/sysroot,init) failed :2 error, then it's because the 'initrd' is not there.
If I boot up to the rescue disk, I can mount /dev/hda1 which is my boot directory. If I try and mount /dev/hda2 though it says"
mount: Mounting /dev/hda2 on /mnt/system failed: Input/output error
Any easy to tell if you harddrive is physically damaged is to pull it out of its bay and listen to it. Does it sound any different than before? Is it consistent or does rapidly spin up and then abruptly spin down?
It sounds like atleast one of your partitions is corrupted. This doesn't easily happen on a journaling file system.
Yikes... Corrupt journaling doesn't sound good. I've pulled the drive and it sounds normal. How would I fix that one partition? I've tried e2fsck and it fails. Seems like I've had this problem before a long time ago and I got it fixed...
I can't figure this out... When I try to do fsck or e2fsck it fails saying that it's possibly a zero-length partition or something. How to I force it to check the partition? I'm running out of ideas... lol
Device Boot Start End Blocks ID System
/dev/hda1 * 1 13 104391 83 Linux
/dev/hda2 14 29496 236822197+ 83 Linux
/dev/hda3 29497 30515 8185117+ 82 Linux Swap
When I boot to the rescue disk and try and mount /dev/hda2 using 'mount /dev/hda2 /mnt/system' I get this:
Code:
Mount: mounting /dev/hda2 on /mnt/system failed: Input/Output error.
When I try and run a e2fsck I get this error:
Code:
e2fsck: Attempt to read block from file system resulted in short read while trying tro open /dev/hda2
Try running the proprietary disk tools that come with your drive. Seatools for Seagate, Data Lifeguard for WD, Power Max for Maxtor. They usually have a drive test tool to see if your drive is physically failing.
Something interesting to add... I just downloaded Tom's boot disk and booted another machine of mine that's working just fine and tried to do an fsck and e2fsck and I get the same exact "superblock might be corrupt" message.
I am doing /dev/hda2. I can mount hda1 just fine. Anyway, as a last ditch effore I've run a "mke2fs -S /dev/hda2" followed with "e2fsck -f /dev/hda2" and I'm seeing lots being changed and lots being removed from the tree. I hope that very little of this is the data I need off that partition...
Seems like I've had to do this before and I was able to get my data by looking through lostandfound directories. Is this a common problem with e2fs? Should I be moving all my partitions to e3fs?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.