LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.

Notices

Reply
 
Search this Thread
Old 08-12-2005, 11:25 PM   #1
orgcandman
Member
 
Registered: May 2002
Location: dracut MA
Distribution: Ubuntu; PNE-LE; LFS (no book)
Posts: 594

Rep: Reputation: 102Reputation: 102
After updating SuSE 9.2 packages, system fails boot without mounting /dev/hda2


I've recently used synaptic to update SuSE 9.2 system. I thought all went well, until I rebooted the machine this morning. It no longer boots after getting past kernel initialization. I can see the compiled-in modules loading, however the system stops with:

Quote:
Freeing unused memory from kernel: 212k freed (this is normal I think)
mount: no such file or directory
starting udev
creating devices
loading kernel/fs/reiserfs/reiserfs.ko
waiting for device /dev/hda2 to appear: .....not found; exiting to /bin/sh
sh: can't access tty: job control turned off
$
I'm fairly certain that this has to do with the recent updates that were made.

Some questions:
- Has anyone encountered this before?
- Is there anyway to restore the system to a previous state?

Pre-emptive answers to questions:
- The filesystem on /dev/hda2 is intact and well. I can boot the system from a special rescue disk that I was smart enough to build a long time ago, and mount the partitions and even chroot into /dev/hda2 and start using it for internet browsing, etc. Obviously this is not an ideal setup.

- Equally important to note is that I already tried installing an RPM version of the 2.6.8-24 default kernel that came with suse 9.2 disks. This didn't fix the problem.

- I also edited the udev.conf and made sure that the defaults were 0666 just as a test (obviously not ideal operations).

Thanks for any help,
Aaron
 
Old 08-13-2005, 12:15 AM   #2
bigrigdriver
LQ Addict
 
Registered: Jul 2002
Location: East Centra Illinois, USA
Distribution: Debian Squeeze
Posts: 5,785

Rep: Reputation: 311Reputation: 311Reputation: 311Reputation: 311
Try booting from your boot disk. Do not mount /dev/hda2. If it mounts, then umount /dev/hda2.

Then run 'fsck -N /dev/hda2' (run fsck on /dev/hda2 but do not change anything, just show what would be done).

Study the output carefully. If it doesn't look like any major damage will be done, then run 'fsck /dev/hda2' to see if it fixes anything. You may have to run the command more than once for error corrections to take place.

Reboot after each fun of fsck without the -N option. It's the only way I know to see if it worked.

Since you can still access the partition after booting from rescue disk, it's a fair bet that fsck can fix the problem.
 
Old 08-13-2005, 07:48 AM   #3
orgcandman
Member
 
Registered: May 2002
Location: dracut MA
Distribution: Ubuntu; PNE-LE; LFS (no book)
Posts: 594

Original Poster
Rep: Reputation: 102Reputation: 102
it wasn't an fsck, or corrupt HD issue. That was the first thing I suspected, and under my first bullet, I should have mentioned that I fsck'd it already. Sorry about that.

Actually, I solved it. Apparently, synaptic updated to mkinitrd-1.2-28, which for some reason can't properly create an initrd image for me. Perhaps this is a known issue, or just a localized problem to me. I'm going to investigate it further, and see what the problem is.

I fixed it by re-installing mkinitrd-1.1-7 off of my installation CD, and using that to re-create an initrd. After that, it booted fine.

Thanks,
Aaron
 
Old 08-13-2005, 10:24 PM   #4
gd2shoe
Member
 
Registered: Jun 2004
Location: Northern CA
Distribution: Debian
Posts: 835

Rep: Reputation: 49
Odd. I thought the initrd shipped as part of the kernel package. If that was the case, then the mkinitrd package shouldn't have mattered at all. Maybe it builds the initrd locally? Odd. Something to think about.
 
Old 08-15-2005, 12:39 PM   #5
orgcandman
Member
 
Registered: May 2002
Location: dracut MA
Distribution: Ubuntu; PNE-LE; LFS (no book)
Posts: 594

Original Poster
Rep: Reputation: 102Reputation: 102
actually, it seems that when the kernel rpm installs, it runs mkinitrd, to create a more tailored initial ramdisk.

-Aaron
 
Old 08-16-2005, 08:59 PM   #6
gd2shoe
Member
 
Registered: Jun 2004
Location: Northern CA
Distribution: Debian
Posts: 835

Rep: Reputation: 49
Uh, that's what I meant by locally. It is interesting to think about, though.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
KDE fails to start after updating the system rthdesign Linux - Newbie 4 07-27-2005 03:29 PM
swap, /dev/hda2 by /dev/hands :) kaN5300 Slackware 2 09-13-2004 03:45 AM
/dev/hda2 negative size? yozd Linux - Hardware 4 07-24-2004 08:41 PM
mount point for /dev/hda2 (my boot partition) annihilate Slackware - Installation 5 05-23-2004 03:38 AM
error in /dev/hda2??? Volcom Slackware 1 06-12-2003 01:30 AM


All times are GMT -5. The time now is 11:30 PM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration