[SOLVED] error: attempt to read or write outside of disk 'hd0' -- entering rescue mode
Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
error: attempt to read or write outside of disk 'hd0' -- entering rescue mode
I know there are several threads on this topic out there. But I still cannot find the solution. I'm trying to fix grub from livecd but it doesn't recognize /dev/sda at all. Is there a way to mount sda so that I can reinstall/repair grub?
Have you the correct drivers loaded? I am a believer in a usb drive as an essential piece of equipment. I have an ide/sata one and can shove any disk in for test/repair purposes. Useful, as it's the only ide reader I have now.
There was no way I could check SMART data on that drive, nor access its info. The chances were: hardware issue (the drive has only a few months old), or the system (software) was corrupted in some way. There was nothing I could do to repair grub (not that I knew ;-/ ) given that it was inaccesible. To avoid any data loss, I disconnected the disk where personal data is allocated (sdc), just in case, and then, used this cables with the failing disk, in order to make sure everything was working fine. Turned on the pc and for my surprise it recognized sda, eventhough the grub was corrupted. (At this point, I was pretty sure It was a cable or motherboard issue, slots perhaps?). Don't remember why is it that I couldn't repair it from live session (the grub), and I'm not an advanced linux user either, so I installed a distro in a free partition I had available, so that during the process of installation it would set up grub as well. It worked. Perhaps, not the quickest, nor the smartest, but worked. Lastly, I wanted sdc (personal files) working too, so I put cables back to its respective drives, and both worked properly till now!!!
Crazy, isn't it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.