Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
debian wrote:OK. I added loglevel=3 and now the error message says it could not find my HDD as show in this link or below. I have no idea why it complains my HDD is missing. BTW, I have a Windows XP on a 2nd HDD if that helps.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for suspend/resume device
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ..
done.
done.
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelays= (did the system wait long enough?)
- Missing modules (cat /proc/modules: ls /dev)
ALERT! UUID=5f0f169c-9727-4f7d-b185-b3a3d8c2c88c does not exist. Dropping to a
shell!
BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
try changing 5f0f169c-9727-4f7d-b185-b3a3d8c2c88c to 8720c10a-504e-4fc6-924f-89207fdfbd52 in /boot/grub/grub.cfg then reboot.
debian wrote:OK. I added loglevel=3 and now the error message says it could not find my HDD as show in this link or below. I have no idea why it complains my HDD is missing. BTW, I have a Windows XP on a 2nd HDD if that helps.
Begin: Running /scripts/local-block ... done.
Begin: Running /scripts/local-block ... done.
done.
Gave up waiting for suspend/resume device
done.
Begin: Waiting for root file system ... Begin: Running /scripts/local-block ..
done.
done.
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
- Check rootdelays= (did the system wait long enough?)
- Missing modules (cat /proc/modules: ls /dev)
ALERT! UUID=5f0f169c-9727-4f7d-b185-b3a3d8c2c88c does not exist. Dropping to a
shell!
BusyBox v1.22.1 (Debian 1:1.22.0-19+b3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)
try changing 5f0f169c-9727-4f7d-b185-b3a3d8c2c88c to 8720c10a-504e-4fc6-924f-89207fdfbd52 in /boot/grub/grub.cfg then reboot.
If you read my previous post carefully, I clearly indicated that I had re-installed debian several times since my old post indicates with the old UUID. In my re-installations, I had the HDD reformatted. As such, the UUID got regenerated with a different one. Just to assure you, the current installation, i.e. GRUB menu, etc., does reflect to the new UUID, yet the booting process still ends up with such error messages showing the new UUID. So, no a-ha moment here.
pylkko wrote:Could you please at least try booting with ‘rootdelay=10’, for example.
I tried with rootdelay=10 seconds and/or rootdelay=300 seconds (5 minutes) with the same error messages. I have noticed the later (5 minutes delay) generated a whole lot of the following messages before it ended up prompting with the BusyBox shell prompt. During the messages shown below, I noticed my 3.5" Floppy drive whirling up. I put in a blank formatted 3.5" disc into the floppy drive and the messages kept spitting out. I don't know if this makes any difference.
Would it be possible for you to provide more log info, from either the boot sequence or from any log files on disk? Also, if possible, more info about the hardware.
Since you are getting so many acpi related issues, you could try booting with acpi=off. This is useful for further troubleshooting; if it still fails, then there is some unknown problem. If it doesn't then there is likely a acpi related bug/issue. In this case, there are several other boot params that are not so drastic as entirely disabling acpi that you can try in the next step.