gnewsense-users
[Top][All Lists]
Advanced

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

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


From: Christophe Jarry
Subject: Re: [gNewSense-users] I am unable to boot from vmlinuz-2.6.33.3-libre-lemote since upgrade
Date: Sat, 16 Jul 2011 12:48:48 +0200

> OK, but what's the output of mount?

    sudo mount /dev/hda2 /media/tmp
    mount: you must specify the filesystem type

> /lib/init/rw/rootdev is a temporary device node created by 
> /etc/init.d/checkroot.sh for fsck. It means there's probably something 
> wrong with /etc/fstab. Try this on both kernels:
> 
> grep UUID /etc/fstab | while read dev other ; do sudo findfs $dev ; done
> 
> It should give you the device files of all file systems that should be 
> mounted by UUID.

Under both kernels:

    $ grep UUID /etc/fstab | while read dev other ; do sudo findfs $dev ; done
    findfs: unable to resolve 'UUID="c8ebb5c8-eafa-4532-8535-3c4312e7a7c4"'
    findfs: unable to resolve 'UUID="35892cba-5fe1-425e-9227-cd6121c9159d"'
    Usage: findfs LABEL=<label>|UUID=<uuid>
    Usage: findfs LABEL=<label>|UUID=<uuid>
    Usage: findfs LABEL=<label>|UUID=<uuid>
    Usage: findfs LABEL=<label>|UUID=<uuid>

Under 2.6.37, manually,:

    $ sudo findfs UUID="c8ebb5c8-eafa-4532-8535-3c4312e7a7c4"
    /dev/sda1
    $ sudo findfs UUID="35892cba-5fe1-425e-9227-cd6121c9159d"
    /dev/sda2

Under 2.6.33.3, manually:

    $ sudo findfs UUID="c8ebb5c8-eafa-4532-8535-3c4312e7a7c4"
    findfs: unable to resolve 'UUID=c8ebb5c8-eafa-4532-8535-3c4312e7a7c4'
    $ sudo findfs UUID="35892cba-5fe1-425e-9227-cd6121c9159d"
    findfs: unable to resolve 'UUID=35892cba-5fe1-425e-9227-cd6121c9159d'

> Also try blkid on both kernels to check if they both see the same UUIDs.

Under 2.6.37:

    $ sudo blkid
    /dev/sda1: UUID="c8ebb5c8-eafa-4532-8535-3c4312e7a7c4" TYPE="ext3" 
    /dev/sda2: UUID="35892cba-5fe1-425e-9227-cd6121c9159d" TYPE="ext3" 
    /dev/sda3: TYPE="swap" 
    /dev/sda4: UUID="910f2301-8ef8-413f-90a8-36155e996626" SEC_TYPE="ext2"
TYPE="ext3" 

Under 2.6.33.3:

    $ sudo blkid
    $

> A manual fsck doesn't hurt and you'd know for sure.

fsck does check my partitions from time to time, without error. Is it required
that I run it manually?

Christophe



reply via email to

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