Thanks for the feedback. The fact USB is a bad idea all around for security (and potentially stability), and the fact I was getting minor corruption, should have been a warning to me to move the drive right onto the SATA bus, rather than risking worse corruption. I guess I only have myself to blame.
I guess I'll "get back on the horse," lol, with the 3.2 release candidate, and an internal drive. Qubes offers enough to keep on tryin'. Thankfully I run things in a relatively "amnesiac" fashion to start with, so any useful or valuable data was on a separate, internal, encrypted hard drive, and unharmed. Thanks. > [email protected]: >> Well, my wild enthusiasm with Qubes has turned into complete frustration >> and exasperation this morning. >> >> The "mild" corruption I was seeing on boot (running Qubes from a USB >> 2.5" >> HD) wasn't quite so mild the last time I booted. >> >> This time, rather than "recovering journal... done," the fsck spewed >> more >> than I've ever seen an fsck spew, and the filesystem was trashed. /var >> ended up as a symlink to liblber-2.4.so.2.10.2. I found /var/lib/qubes >> in >> lost+found (along with 350 other directories). Argh! >> >> I'd highly recommend that nobody run Qubes 3.1 from an external USB >> drive. >> >> I'm going back to another OS as my daily system. >> >> I'll probably give Qubes 3.2rc a try on an internal hard drive, as a >> secondary OS, to see if that solves my HD and video corruption issues. >> If >> not, I'll probably wait for Qubes to mature a bit more before using it >> in >> any serious manner. > > I've run Qubes 3.0rc1 and Qubes 3.2rc1 from an external USD hard drive > (for about a month each). 3.0rc1 encountered kernel panics about once > per day (which wasn't the case when run from an internal drive) and > booted much slower than from an internal drive, but I didn't notice any > obvious drive corruption from it. 3.2rc1 had no issues whatsoever and > wasn't much slower than internal. I haven't tried any release of 3.1. > > So, my guess is that the issue you're encountering either was fixed > between 3.1 and 3.2rc1 (and didn't seem to exist in 3.0rc1), or is in > some way unique to your setup. Maybe a hardware issue? > > Cheers, > -Jeremy Rand > > -- > You received this message because you are subscribed to the Google Groups > "qubes-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/qubes-users/df5ff24c-c6ce-8dda-dfac-5f07bea4f9c0%40airmail.cc. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "qubes-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/242ab62b9fdfba9c77ebf9748842b412.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
