[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gNewSense-users] I am unable to boot from vmlinuz-

From: xdrudis
Subject: Re: [gNewSense-users] I am unable to boot from vmlinuz- since upgrade
Date: Thu, 14 Jul 2011 14:45:48 +0200
User-agent: Mutt/1.5.21 (2010-09-15)

On Thu, Jul 14, 2011 at 09:39:37AM +0200, Christophe Jarry wrote:
> > What does mount say if you call it after login ?
> When I boot from, after login, /dev does contain no "hd*" nor 
> "sd*"...
> But when "/dev/hda1" was being checked under by "fsck from
> util-linux-ng 2.17.2" (after "* Checking root file system..." message), it was
> named "/lib/init/rw/rootdev" instead of "/dev/hda1".    

May it be just the name in some initrd ? 
If you just call mount, without arguments, after login, it should tell 
you the name of each device and itsmountpoint in the filesystem. 
> > dmesg ?
> `dmesg | grep EXT3` after login under gives me this:
>     [   10.028000] EXT3-fs (hda1): mounted filesystem with writeback data mode
>     [  150.992000] EXT3-fs (hda1): using internal journal

And nothing about hda2 (/home) ? 

> > might it be that there is some error in the /home filesystem ?
> If it is the case, linux-2.6.37 would not mount /home either I think.

Yes, you're right.
> > Are both / and /home formatted the same ?
> Yes, ext3 for both.

I guess the UUIDs that blkid shows are the same if you try under one 
kernel than under the other. That's the idea, but then it should work...
> > Might it be some module missing in one of the two kernels ?
> How do I know if it is the case?

you could 

diff /boot/config- /boot/config-2.6.37-libre-lemote

But if both partitions are formated exactly equal I can't see 
why it would mount / and not /home ...

reply via email to

[Prev in Thread] Current Thread [Next in Thread]