I have linux guests whose boot hangs due to failed fsck attempts.
What happens is this:
It's triggered by using the web interface's ACPI shutdown drop-down or button control to turn the machine off.
If I use shutdown -P now it's okay.
When I press the Ctrl-Alt-Delete button from the VNC web console, and then issue the Stop command when it reaches BIOS, the next boot is fine.
In Ubuntu 10.10 the shutdown button / drop-down entry command is ignored completely without acpid installed.
In Debian Sid, they're ignored unless acpid & acpi-support-base is installed.
The behavior is consistent & reproducable with both pve-kernel-2.6.32-4 & pve-kernel-2.6.35-1.
I thought this was why:
Both linux guests have acpid installed in the default configuration, which I thought was the problem until I looked at the script it runs.
All it seems to do is issue shutdown -h now.
This is what I tried:
In the shutdown script at /etc/acpi/powerbtn.sh, I changed it from a -h to shutdown -P now, but there's no change.
Also I changed the FSCKFIX value in /etc/default/rcS from no to yes so the repair happens automatically.
Starting fsck is then automated, but it still fails with exit code 3.
So I'm left with:
The problem remains unrepaired, and all I've accomplished is the ability to proceed past the fsck hang, but then there's another hang afterward anyway.
It seems that somehow grub2 is aware fsck failed, because the countdown doesn't even begin on the boot following.
Surely I'm missing something...
What happens is this:
It's triggered by using the web interface's ACPI shutdown drop-down or button control to turn the machine off.
If I use shutdown -P now it's okay.
When I press the Ctrl-Alt-Delete button from the VNC web console, and then issue the Stop command when it reaches BIOS, the next boot is fine.
In Ubuntu 10.10 the shutdown button / drop-down entry command is ignored completely without acpid installed.
In Debian Sid, they're ignored unless acpid & acpi-support-base is installed.
The behavior is consistent & reproducable with both pve-kernel-2.6.32-4 & pve-kernel-2.6.35-1.
I thought this was why:
Both linux guests have acpid installed in the default configuration, which I thought was the problem until I looked at the script it runs.
All it seems to do is issue shutdown -h now.
This is what I tried:
In the shutdown script at /etc/acpi/powerbtn.sh, I changed it from a -h to shutdown -P now, but there's no change.
Also I changed the FSCKFIX value in /etc/default/rcS from no to yes so the repair happens automatically.
Starting fsck is then automated, but it still fails with exit code 3.
So I'm left with:
The problem remains unrepaired, and all I've accomplished is the ability to proceed past the fsck hang, but then there's another hang afterward anyway.
It seems that somehow grub2 is aware fsck failed, because the countdown doesn't even begin on the boot following.
Surely I'm missing something...
Last edited: