On a 5.4-pre system as of the last few days, If I mount a spun down hard disk (one I am using only for backup): # mount /backup/usr I get ad1: TIMEOUT _ READ DMA retrying (2 retries left) LBA=7340273 ad0: WARNING - removed from configuration ad1: WARNING - removed from configuration at0-slave: FAILURE - READ DMA Timeout mount:/dev/ad1s1g : Input/Output error ata0-slave: timeout state=0 unexpected initiate_write_filepage: already started initiate_write_filepage: already started (repeat until reset is pushed) Nothing works because all of the disks are unmounted. Can't even shut down. This worked great in 4.10, and also 5.3 (where the initial mount generated an error, but I could do the mount again after the disk spun up). Anybody else get the same thing? I'll open a bug report if so... -- Mike Harding <mvh@ix.netcom.com>
Diomidis Spinellis
2005-Apr-06 01:56 UTC
Mounting a powered-down HDD renders system unusable
Mike Harding wrote:> On a 5.4-pre system as of the last few days, If I mount a spun down hard > disk (one I am using only for backup):This does not answer your question, but may help you solve the problem. Try detaching the disk after you are done using it, and attaching it again before you mount it. I use this procedure for my backup disk. It has the advantage of allowing me to physically isolate the disk from the computer. The disk lives on a detachable disk drawer-style cabinet; by pulling the disk drawer out an inch I severe the electrical connections between the disk and the computer. The idea is that even if the computer gets electrically fried by lightning, the disk will survive. Thus, the procedure I use is: atacontrol attach 0 mount /backup # Perform backup umount /backup atacontrol detach 0 -- Diomidis Spinellis - http://www.spinellis.gr