Some kind of configuration error after replacing motherboard
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Some kind of configuration error after replacing motherboard
I get the grub menu, I choose failsafe, then I get the usual black screen
with a series of text messages and it stops at the messages
"waiting for device sda10 to appear (timeout 1 minute)"
"waiting for device sda9 to appear (timeout 1 minute)"
I'm enclosing the contents of menu.lst, fstab, the output from fdisk -l,
fstab and blkid
Is there anything else I can post to help diagnose ?
The Linux partitions are actually sdb9 and sdb10
supergrub2 dd to a USB stick have it boot you into your box then install grub and update it again, that might get you in quicker. then fiddling with it.
then you can better do damage control checking your fstab again the UUIDs after you get in. etc
or go old school /dev/ddbx in your fstab and see if that will get you in. looks like you're able to get to it by another means
I am in and have access through a Live CD, This is great for troubleshooting, but so far, I don't know what
to change so that I can boot my installed system.
Looks to me like all the UUID's match up as they should, so I'm not sure what is wrong.
The fstab matches the menu.lst which matches the output from blkid which corresponds to sdb9 and sdb10, as you say.
Why during the startup messages is it looking for sda9 and sda10 ? Where is this coming from ?
Are there some grub commands I can issue that will rebuild the whole environment ?
I am in and have access through a Live CD, This is great for troubleshooting, but so far, I don't know what
to change so that I can boot my installed system.
Looks to me like all the UUID's match up as they should, so I'm not sure what is wrong.
The fstab matches the menu.lst which matches the output from blkid which corresponds to sdb9 and sdb10, as you say.
Why during the startup messages is it looking for sda9 and sda10 ? Where is this coming from ?
Are there some grub commands I can issue that will rebuild the whole environment ?
I'd use supergrub2 .. dd a copy onto another USB via your live install, then use that to boot into your Linux then I would try re installing grub update grub, reboot see if that works, then go to changing my fstab to /dev/sdxx if not then I'd try rebooting to eliminate that possibility .. process of elimination is part of trouble shooting.
if you had your system split / and /home you could just do a re-install of linux and not lose any personal data in /home
there is another in here that spoke of your initrd is too specific. in post #2
I'd use supergrub2 .. dd a copy onto another USB via your live install, then use that to boot into your Linux then I would try re installing grub update grub, reboot see if that works, then go to changing my fstab to /dev/sdxx if not then I'd try rebooting to eliminate that possibility .. process of elimination is part of trouble shooting.
if you had your system split / and /home you could just do a re-install of linux and not lose any personal data in /home
there is another in here that spoke of your initrd is too specific. in post #2
Sorry, I've absolutely no idea what this means :
"maybe your initrd is too specific"
In which case I would suggest you ask on your distros (pclos ?) own forums. It is likely you can simply chroot into your on-disk system (from the liveCD) and remake the initrd. But these things can be distro-specific.
Another (last resort) option is to save your data and re-install, then restore your data. The installer should find all the drivers needed.
The fact you can everything from the liveCD is a good sign.
you changed your motherboard therefore hardware is no longer the same, your initrd-2.6.38.8-pclos1.a64.img and initrd may well be fine tuned to your hardware from your other board therefore it cannot load what it needs to boot up your system due to the hardware change.
is it possible hd0 and hd1 connectors got switched?
Appreciate the continuing suggestions.
According to what I see /dev/sda is where the boot loader is, while /dev/sdb is where the Linux root and swap
partitions are. /dev/sda is hd0 and /dev/sdb is hd1. /dev/sdb9 is swap and /dev/sdb10 is root
This point made about the initrd being an issue could be relevant. I am a bit of a newbie, dont know
Linux commands and concepts that well. I might have gone to the PCLinuxOS forum for perhaps more targeted
info, but their site is down; it is so slow its unusable.
When this message appears on the screen "waiting for device sda9 to appear" the initailization has alreay
progressed some of the way. Has the initrd already been successfully processed? Here's a screen shot http://www.mediafire.com/file/sx1j6s...110_133232.jpg
Perhaps it's best to create a new initrd because of the new motherboard. Question is how.
Any one have any tips on the initrd creation from the LiveCD environment?
Appreciate the continuing suggestions.
According to what I see /dev/sda is where the boot loader is, while /dev/sdb is where the Linux root and swap
partitions are. /dev/sda is hd0 and /dev/sdb is hd1. /dev/sdb9 is swap and /dev/sdb10 is root
This point made about the initrd being an issue could be relevant. I am a bit of a newbie, dont know
Linux commands and concepts that well. I might have gone to the PCLinuxOS forum for perhaps more targeted
info, but their site is down; it is so slow its unusable.
When this message appears on the screen "waiting for device sda9 to appear" the initailization has alreay
progressed some of the way. Has the initrd already been successfully processed? Here's a screen shot http://www.mediafire.com/file/sx1j6s...110_133232.jpg
Perhaps it's best to create a new initrd because of the new motherboard. Question is how.
Any one have any tips on the initrd creation from the LiveCD environment?
your hard drive(s) maybe they are not plugged in properly as well so they are not spinning up so that they can be mounted.
1) Boot, press F2, or anything to go to the BIOS configuration. DISABLE
the option for Booting to "LEGACY". or,
2) Swap the Hard Drive Cable socket to the other (usually there are two
of it) then to boot up; or,
3) There are plenty of sources on "how to" create initrd, I used to do
that before when RAM was still expensive. Today I don't use initrd
anymore, Slackware 32bit is doing well without it. Thus, my advice is
not to modify anything about initrd yet until you have tried the two (1)
and (2) above.
Had you bothered to check the pclos forums as I suggested, you might have found this thread that almost exactly covers your situation.
The PCLinuxOS forum and the main website were having problems the last few days, with extremely slow response times.
I have in the meantime found some instructions from an alternate source to recreate the initrd.
I actually tried it yesterday and it successfully recreated the file. The system, still, would not boot from the HDD.
Then I realized I had used a 64-bit LiveCD to fix a 32-bit installed OS.
I have since downloaded an iso from 2013 and are retrying. I'll update the thread later
mkdir /mnt
mount /sdb10 /mnt
mount --bind /proc /mnt/proc
mount --bind /dev /mnt/dev
mount --bind /sys /mnt/sys
chroot /mnt
mkinitrd -f -v /boot/ .... (insert image name and kernel name here)
I can now boot and can get to a safemode command prompt, not sure what would be helpful here.
If I boot regular mode I get a text logon prompt ad I can logon. I think it's having issues with
the graphics. The new motherboard has at ATI chip, while the old had an Nvidia graphics card.
Thanks everybody for the suggestions, it's been interesting for me to get this far.
This old system is 32 bit. There was not that much installed, I've
already got the little data I had safely saved away. It makes more sense to install a new system.
I have already downloaded and looked at the latest LiveCD versions of 64 bit Linux Mint, Peppermint
and the recent PCLinuxOS KDE version.
If there's any other distribution you'd recommend please mention it. As you can see, I'm not a complete
beginner, but my conceptual understanding of the environment and the commands to support it
is pretty weak. (But I'd like to learn more)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
