This is still broken, and it's quite a serious matter because when I
upgrade the machine (which sometimes overwrites /boot/grub/grub.cfg) and
reboot, I lose access to it. It can't boot unless someone is physically
present with the machine, who can remove the lines
recordfail=1
if [ -n ${have_grubenv} ]; then save_env recordfail; fi
from the boot script. Frequently, there's nobody where the machine is,
so it remains totally useless, while chewing up watt-hours, with "Error:
sparse file not allowed" displayed on the console.
Is there something I can do to help debug this mystery? I'd be happy to
do what I can to help!
Linux qat 2.6.31-16-generic #53-Ubuntu SMP Tue Dec 8 04:02:15 UTC 2009 x86_64
GNU/Linux
--
error: sparse file not allowed
https://bugs.launchpad.net/bugs/464743
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
