From mboxrd@z Thu Jan 1 00:00:00 1970 From: quanstro@labs.coraid.com (erik quanstrom) Date: Fri, 18 Mar 2011 21:27:05 -0400 Subject: [9fans] New venti install won't boot after 05:00 crash In-Reply-To: <973184192fb7daeae9297506df7285e3@ladd.quanstro.net> References: <59cb47ba46ce1beed6addaef2f8b0023@quintile.net> <973184192fb7daeae9297506df7285e3@ladd.quanstro.net> Message-ID: Topicbox-Message-UUID: bd14c8e0-ead6-11e9-9d60-3106f5b1d025 On Fri Mar 18 21:08:09 EDT 2011, quanstro at quanstro.net wrote: > On Fri Mar 18 20:03:00 EDT 2011, rminnich at gmail.com wrote: > > I don't know guys, these sure look like disk errors to me ... > > no need to guess, fill the partitions with 0s with dd. if that > works, then we know it's a bug in venti. more detail. i think it's reasonable to suspect that something's going wrong in user land. there are about 10 different ways to get Eio from devsd. one is that for writes, sdbio() returns Eio if the block is not within bounds. also, at least the 9atom version of the ide (or, sdata, sic) prints this if an actual ata error occurs if(drive->status & Err){ qunlock(ctlr); print("atagenio: %llud:%d\n", lba, drive->count); [...] and dumps the ata state to the console if the i/o never returns. - erik