Your message dated Fri, 8 Jun 2007 10:53:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#427972: vol_id returns wrong ID_FS_TYPE (vfat instead of
ext3) - system fails to boot
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: udev
Version: 0.105-4
Severity: serious
--- Please enter the report below this line. ---
Hi,
I am reporting this to udev, but it got triggered by the update of
initramfs-tools from 0.87b to 0.88. After this update my system no longer
boots. It drops to busybox shell after reporting that it could not mount root
filesystem and init is missing. Further investigation revealed that vol_id
returns for my root partition the following information:
ID_FS_USAGE=filesystem
ID_FS_TYPE=vfat
ID_FS_VERSION=FAT32
ID_FS_UUID=9E40-3F80
ID_FS_LABEL=
ID_FS_LABEL_SAFE=_
while it is ext3.
Only manual mount -t ext3 /dev/sda1 /root followed by CTRL-D resumes the boot
process.
Should I attach any other info apart from what is included by reportbug-ng?
Cheers
Raf
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.18-4-k7
Debian Release: lenny/sid
550 testing ftp.pl.debian.org
50 unstable ftp.pl.debian.org
--- Package information. ---
Depends (Version) | Installed
==============================-+-=============
libc6 (>= 2.3.6-6) | 2.5-9+b1
libselinux1 (>= 1.32) | 2.0.15-2
libvolume-id0 (>= 0.103-1) | 0.105-4
debconf (>= 0.5) | 1.5.13
OR debconf-2.0 |
lsb-base (>= 3.0-6) | 3.1-23.1
--- End Message ---
--- Begin Message ---
On Jun 08, Rafa? Czarnocki <[EMAIL PROTECTED]> wrote:
> How could it happen
Did you use something else than the standard (c)fdisk to partition your
disk?
> and why for a couple of years it worked without a hitch
> until the latest initramfs-tools update?
I don't know, and the upstream maintainer does not know either.
There have been no recent changes in vol_id, and anyway I have not
uploaded a new udev package in a while.
> And more important: is there a simple non-destructive way to fix it?
dd if=/dev/zero of=/dev/XXX bs=512 count=1
--
ciao,
Marco
--- End Message ---
