Results 1 to 4 of 4
After switching my Debian from squeeze to unstable, the kernel will not boot at all.
It does not recognize any of the UUIDs in fstab.
All the articles I found ...
- 05-22-2011 #1Just Joined!
- Join Date
- Mar 2011
- Posts
- 3
Cannot resolve UUID. No blkid ouput
After switching my Debian from squeeze to unstable, the kernel will not boot at all.
It does not recognize any of the UUIDs in fstab.
All the articles I found say to use blkid to find the UUID and match them, but after booting into maintenance blkid produces no output for any of the partitions so I don't know what it is seeing in 2.6.39.
Ive had this problem before on a laptop which caused me to switch it out for Gentoo after I could not fix it, but since this is the second time Id prefer to figure out what keeps going on.
kernel 2.6.32 still boots fine
kernel 2.6.39 is the issue.
Below is the output of a few commands when running the 2.6.32 kernel.
2.6.39 gives no output at all for blkid and fdisk -l (Ill try ls -l /dev/disk/by-uuid right now but I have to log off since the machine is my router)
*EDIT: There is no /dev/disk folder when booting into 2.6.39 maintanence mode*
fstab
ls -l /dev/disk/by-uuidCode:# <file system> <mount point> <type> <options> <dump> <pass> proc /proc proc defaults 0 0 # /dev/hdb3 / ext3 errors=remount-ro 0 1 UUID=34c70d38-8237-4a30-9d00-906d7c736d7a / ext3 errors=remount-ro 0 1 # /dev/hdb1 /boot ext2 defaults 0 2 UUID=b089c119-148c-4faa-8f58-3151c13a6e31 /boot ext2 defaults 0 2 # /dev/hdb7 /home ext3 defaults 0 2 UUID=f7caf73a-3a24-43fc-9ed9-e9b21077bc62 /home ext3 defaults 0 2 # /dev/hdb6 /tmp ext3 defaults 0 2 UUID=bd1cbe97-0c0c-4d48-b0d0-748e01f19e36 /tmp ext3 defaults 0 2 # /dev/hdb5 /var ext3 defaults 0 2 UUID=7e5d8a22-6472-4c4a-8e11-eca3b7ff224e /var ext3 defaults 0 2 # /dev/hdb2 none swap sw 0 0 UUID=ad02068c-8518-4e69-8b74-49d5b9e82c69 none swap sw 0 0 # /dev/hdc /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/cdrom /media/cdrom0 udf,iso9660 user,noauto 0 0 /dev/fd0 /media/floppy0 auto rw,user,noauto 0 0
blkidCode:lrwxrwxrwx 1 root root 10 May 22 12:24 0000-0001 -> ../../sdb1 lrwxrwxrwx 1 root root 10 May 22 12:24 34c70d38-8237-4a30-9d00-906d7c736d7a -> ../../sda3 lrwxrwxrwx 1 root root 10 May 22 12:24 7e5d8a22-6472-4c4a-8e11-eca3b7ff224e -> ../../sda5 lrwxrwxrwx 1 root root 10 May 22 12:24 ad02068c-8518-4e69-8b74-49d5b9e82c69 -> ../../sda2 lrwxrwxrwx 1 root root 10 May 22 12:24 b089c119-148c-4faa-8f58-3151c13a6e31 -> ../../sda1 lrwxrwxrwx 1 root root 10 May 22 12:24 bd1cbe97-0c0c-4d48-b0d0-748e01f19e36 -> ../../sda6 lrwxrwxrwx 1 root root 10 May 22 12:24 f7caf73a-3a24-43fc-9ed9-e9b21077bc62 -> ../../sda7
fdisk -lCode:/dev/sda1: LABEL="/boot" UUID="b089c119-148c-4faa-8f58-3151c13a6e31" TYPE="ext2" /dev/sda2: UUID="ad02068c-8518-4e69-8b74-49d5b9e82c69" TYPE="swap" /dev/sda3: LABEL="/" UUID="34c70d38-8237-4a30-9d00-906d7c736d7a" TYPE="ext3" /dev/sda5: LABEL="/var" UUID="7e5d8a22-6472-4c4a-8e11-eca3b7ff224e" TYPE="ext3" /dev/sda6: LABEL="/tmp" UUID="bd1cbe97-0c0c-4d48-b0d0-748e01f19e36" TYPE="ext3" /dev/sda7: LABEL="/home" UUID="f7caf73a-3a24-43fc-9ed9-e9b21077bc62" TYPE="ext3"
Any suggestions would be appreciated.Code:Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x87a28449 Device Boot Start End Blocks Id System /dev/sda1 * 1 608 4883728+ 83 Linux /dev/sda2 609 851 1951897+ 82 Linux swap / Solaris /dev/sda3 852 2067 9767520 83 Linux /dev/sda4 2068 9729 61545015 5 Extended /dev/sda5 2068 8146 48829536 83 Linux /dev/sda6 8147 8632 3903763+ 83 Linux /dev/sda7 8633 9729 8811621 83 Linux
Thanks
- 05-22-2011 #2Linux Guru
- Join Date
- Oct 2007
- Location
- Tucson AZ
- Posts
- 1,935
Your fstab output show all the partitions as hdx,y while your blkid and ls -l commands show as sdx,y. So where is the fstab file you posted? What else is on this machine?
Also, what does "the kernel will not boot at all" mean? Do you get any messages? Exactly what happens?
- 05-23-2011 #3Just Joined!
- Join Date
- Mar 2011
- Posts
- 3
The fstab is /etc/fstab
When I say it wont boot, I mean that full boot fails with"Cannot Resolve UUID X" and Im left with the screen that says "Press Control-D for maintanance mode or enter root password"
The machine is a gateway/firewall. So nothing but firewall and IDS stuff. Everything is CLI only including the iptables firewall.
The hdaX in fstab versus the sdaX in everything else, is actually how its all showing up when running the commands from the 2.6.32 kernel. The change might have come about when I moved from stable to sqeeze last year. So that may be what happended. Although 2.6.32 has never complained. I didnt even notice that until I posted. It is strange though.
Ill log off and reboot it and what other info I can get.
- 05-23-2011 #4Just Joined!
- Join Date
- Mar 2011
- Posts
- 3
I suppose you could say that is still does boot, but most services fail including udev, exim, etc.
Networking does start though.
I can see my / filesystem but still blkid and the other commands show no output
Also, the hdaX references were commented out so it shouldnt affect mounting the partitions. The backup from when it was changed to UUID is dated Nov 2010.Last edited by nightg0at; 05-23-2011 at 12:33 AM.


Reply With Quote
