Comment 80 for bug 138691

I went into recovery mode several times today to check my drive and try it out since I've never used it before. I had no "halt:" errors this time, just my usual "ata1.00:" errors. I tried using 'shutdown' with -r, -h, -H, and -HF and all resulted in ata1.00 errors from recovery console and gnome-terminal.

I just tried adding "apm power_off=1" and it made no difference. I got the normal network messages, screen flickered to the splash screen with a completely black bar and the devices inside my tower sounded like they powered down immediately when the splash came up. Then it just sits there until the "ata1.00:" error. Hence, I removed it.

To me, it seems like program 'A' powers down the HDs before program 'B' (the one that produces the "ata1.00:" errors) is done with it. In System > Administration > Services I have both acpid and apmd running (default 8.04 install from LiveCD). This was the same in 7.10; so, it's most likely normal, but I figured it was worth mentioning.

I decided to write down the error and this is what happens:
<After splash screen, hit Ctrl-Alt-F? to bring up messages>
...
*Unmounting temp filesystems...
*Deactivating swap...
*Unmounting local filesystems...
*Will now halt
halt: Unable to iterate IDE devices: No such file or directory
[time] ata1.00: Exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
[time] ata1.00: cmd ea/00:00:00:00:00/00:00:00:00:00/a0 tag 0
[time] ata1.00: status: {DRDY}
[time] ata1.01: revalidation failed (errno=-5)
<About 45 seconds goes by...>
[time] ata1.01: revalidation failed (errno=-5)
<About 45 seconds goes by...>
[time] ata1.01: revalidation failed (errno=-5)
<About 45 seconds goes by...>
[time] ata1.01: revalidation failed (errno=-5)
<About 45 seconds goes by...>
[time] ata1.01: revalidation failed (errno=-5)
<About 45 seconds goes by...>
[time] ata1.01: revalidation failed (errno=-5)
<5 seconds goes by and system powers down!>

So, Yay!? It powers down after awhile...I guess that's good new?