I was going to reply on the forum thread I originally started, but it's locked now. sigh. http://ubuntuforums.org/showthread.php?t=625076
Anyway, the solution to my problem was an updated firmware for my WD5000YS hard drive. http://wdc.custhelp.com/cgi-bin/wdc.cfg/php/enduser/std_adp.php?p_faqid=1493&p_created=1168299631&p_sid=mN5O5Wsi&p_accessibility=0&p_redirect=&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd19jbnQ9NDkmcF9wcm9kcz0mcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPXNlYXJjaF9mbmwmcF9wYWdlPTEmcF9zZWFyY2hfdGV4dD1yYWlk&p_li=&p_topview=1 or a shorter URL that also has a link to it: http://www.3ware.com/KB/article.aspx?id=15065 --- [...] Cause: WD hard drives have an internal routine that is periodically executed as part of the internal “Data Lifeguard” process that enhances the operational life expectancy. While the drive is running this routine, if the drive encounters an error, the drive’s internal host/device timer for this routine is NOT cancelled causing the drive to be locked in this routine, never becoming accessible to the host computer/controller. This condition can only be reset by a Power Cycle. [...] --- sounds exactly like what I was seeing. I upgraded my firmware several months ago, and I haven't seen the problem since. -- Seagate ST980813ASG on Dell Vostro 1700 HD stops https://bugs.launchpad.net/bugs/196076 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
