I think this is unrelated to bug 453588. The reporter of that bug says that it was fixed by a firmware update, which suggests to me that it was the consequence of some disk driver problem. That won't be the case here as Dave is testing with up-to-date packages.
I think this is unrelated to bug 453588. The reporter of that bug says that it was fixed by a firmware update, which suggests to me that it was the consequence of some disk driver problem. That won't be the case here as Dave is testing with up-to-date packages.