Your message dated Sun, 17 Apr 2011 20:50:16 +1000
with message-id <201104172050.16826....@otaku42.de>
and subject line Re: [Pkg-sysvinit-devel] Bug#623003: initscripts: checkfs
fails with already mounted error after lenny to squeeze upgrade
has caused the Debian Bug report #623003,
regarding initscripts: checkfs fails with already mounted error after lenny to
squeeze upgrade
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 this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
623003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initscripts
Version: 2.88dsf-13.1
Severity: critical
Tags: squeeze
Justification: breaks unrelated software
After upgrade from lenny to squeeze my system no longer boots.
Here is the boot up text:
"
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
Using makefile-style concurrent boot in runlevel S.
Starting the hotplug events dispatcher: udevdudevd[179]: SYSFS{}= will be
removed in a future udev version, please use ATTR{}= to match the event device,
or ATTRS{}= to match a parent device, in /etc/udev/rules.d/024_hpmud.rules:24
udevd[179]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:26
udevd[179]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:28
udevd[179]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:30
udevd[179]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:32
..
[ 5.779858] udev[180]: starting version 164
udevd[180]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:24
..
[ 5.779858] udev[180]: starting version 164
udevd[180]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:24
udevd[180]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:26
udevd[180]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:28
udevd[180]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:30
udevd[180]: SYSFS{}= will be removed in a future udev version, please use
ATTR{}= to match the event device, or ATTRS{}= to match a parent device, in
/etc/udev/rules.d/024_hpmud.rules:32
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...[ 6.221138] input: PC Speaker as
/devices/platform/pcspkr/input/input0
[ 6.291937] AMD Geode RNG detected
[ 7.053147] padlock: VIA PadLock not detected.
[ 7.213202] geode-aes: GEODE AES engine enabled.
[ 7.299985] Error: Driver 'pcspkr' is already registered, aborting...
[ 7.554242] kjournald starting. Commit interval 5 seconds
[ 7.603203] kjournald starting. Commit interval 5 seconds
[ 7.686370] kjournald starting. Commit interval 5 seconds
[ 7.692588] EXT3 FS on sdb3, internal journal
[ 7.697022] EXT3 FS on sdb2, internal journal
[ 7.701965] EXT3-fs: mounted filesystem with ordered data mode.
[ 7.707988] EXT3 FS on sdb5, internal journal
[ 7.712420] EXT3-fs: mounted filesystem with ordered data mode.
[ 7.718384] EXT3-fs: mounted filesystem with ordered data mode.
done.
Activating swap...[ 8.216609] Adding 497972k swap on /dev/sdb1. Priority:-1
extents:1 across:497972k
done.
Checking root file system...fsck from util-linux-ng 2.17.2
/: clean, 57717/137360 files, 316504/549360 blocks
done.
[ 8.995602] leds_alix2: system is recognized as "PC Engines ALIX.2"
[ 9.027061] Registered led device: alix:1
[ 9.065850] Registered led device: alix:2
Cleaning up ifupdown....
[ 9.095594] Registered led device: alix:3
Loading kernel modules...done.
Setting up networking....
Activating lvm and md swap...done.
Checking file systems...fsck from util-linux-ng 2.17.2
/dev/sdb2 is mounted. e2fsck: Cannot continue, aborting.
/dev/sdb3 is mounted. e2fsck: Cannot continue, aborting.
/dev/sdb5 is mounted. e2fsck: Cannot continue, aborting.
fsck died with exit status 8
failed (code 8).
File system check failed. A log is being saved in /var/log/fsck/checkfs if that
location is writable. Please repair the file system manually. ... failed!
A maintenance shell will now be started. CONTROL-D will terminate this shell
and resume system boot. ... (warning).
Give root password for maintenance
(or type Control-D to continue): [ 14.297635] usb 1-2: new high speed USB
device using ehci_hcd and address 2
[ 14.435250] usb 1-2: New USB device found, idVendor=1058, idProduct=1003
[ 14.441984] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 14.449147] usb 1-2: Product: External HDD
[ 14.453634] usb 1-2: Manufacturer: Western Digital
"
The /var/log/fsck/checkfs files does not say anything more then the error given
here.
With ctrl+d the system boots normally, however this is a headless system, and I
rather not have to keep attaching a serial cable..
Thank you
Thorben
-- System Information:
Debian Release: 6.0.1
APT prefers stable
APT policy: (990, 'stable')
Architecture: i386 (i586)
Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages initscripts depends on:
ii coreutils 8.5-1 GNU core utilities
ii debianutils 3.4 Miscellaneous utilities specific t
ii libc6 2.11.2-10 Embedded GNU C Library: Shared lib
ii lsb-base 3.2-23.2squeeze1 Linux Standard Base 3.2 init scrip
ii mount 2.17.2-9 Tools for mounting and manipulatin
ii sysv-rc 2.88dsf-13.1 System-V-like runlevel change mech
ii sysvinit-utils 2.88dsf-13.1 System-V-like utilities
Versions of packages initscripts recommends:
ii e2fsprogs 1.41.12-2 ext2/ext3/ext4 file system utiliti
ii psmisc 22.11-1 utilities that use the proc file s
initscripts suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 17 Apr 2011 07:59:52 PM Thorben wrote:
> Hi Kel,
>
> I have been looking further into this and I now see what's going on.
>
> In short, I have to apologise for the false bug report.
Not needed.
>
> The long version of what happened follows:
>
> For context, fstab:
>
> "proc /proc proc defaults 0 0
> UUID=8cc10acc-3233-4ed3-ae07-a16c7feaf4e4 / ext2
> defaults,noatime,errors=remount-ro 0 1
>
> UUID=4b494be4-8d11-4024-9266-d5a972d4786a /usr ext3 defaults 0 1
> UUID=1c088681-9628-4240-8e2c-6cf08a6a3570 /var ext3 defaults 0 2
> UUID=ae27781c-0d8c-4b1d-8107-00b048984656 none swap sw 0 0
> UUID=834624fb-c582-49e9-ad7f-4d01d1dce83f /keep ext3 defaults 0 2
>
> UUID=2000c67a-06d3-43a3-a445-fd74a7b1f33c /keep/pele ext3 defaults 0 3
> UUID=2f0ba551-f483-4478-861a-e2c63bcbb52f /home ext3 defaults 0 3
>
>
> /keep /srv/keep none rw,bind 0 0
> /keep/pele /srv/keep/pele none rw,bind 0 0
> "
>
> The other thing to know is that on this system has some disks are
> connected via the USB bus. (It's an ALIX.2)
> The boot disk is a small CF card. The rest of the system is on other
> attached disks.
>
> When I first setup the system some time ago, I had the problem of not
> all disks being discovered before the boot process got to checkfs.
This is the root of the problem. Its a known limitation of the sysvinit
boot system - it is not event based, it just charges ahead at full
speed without any knowledge that the system is ready for the next step...
> My solution back then was a "S09pause" in rcS with just "sleep 10s" in
> it and to have usb_storage and friends in initrd. All disks would be
> discovered before boot proceeded.
>
> This weekend I upgrade to squeeze and the init process was changed to
> a dependancy based one. The system no longer booted. checkfs
> complained that it could not find any disks with the given UUID.
> I found out that my S09pause would no longer be called, or at least
> not in the right place.
Understandable - depending on the dependency information in the script (if any)
insserv would have reordered sequence numbers for script execution at boot.
>
> I google for solutions, as you do...
> I found one that did something with udev (a system I'm still not 100%
> familiar with). So I deleted my S09pause and it seemed to work, but
> boot broke again.
>
> More googling and asking of questions in #debian on freenode, but no progress.
>
> In the end I filed this report. (with hindsight erroneously)
>
> Now we come to the present.
>
> Based on your email, it became obvious to me that the udev solution
> was not only mounting the USB partitions, but also those of the CF
> disk. Giving the problem reported.
>
> My new solution, which seems to work now:
>
> I removed all the stuff installed into udev and put fstab back as given above
> .
> I have stuck a "sleep 10s" in /etc/init.d/rcS before the exec rc S call.
It's disappointing to admit that this is probably a good workaround to the
problems you face with the boot system.
>
> Since all USB modules were loaded in the initrd, and with rc-init
> waiting 10 secs, all disks are discovered before boot proceeds.
> It might not be the most elegant solution, but this system only ever
> reboots on power failures and upgrades...
>
> Thank you for your time.
No problem.
I'm going to close this particular bug report - there are plenty in the BTS
about fsck bailing out because devices are not yet present.
Thanks, Kel.
--- End Message ---
