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. By chance, I did manage to stash away the dmesg from the last failed boot, before the fsck destroyed the filesystem. Just for posterity, some system details: - Qubes 3.1 - USB->Sata controller was ID 152d:2329 JMicron Technology Corp. / JMicron USA Technology Corp. JM20329 SATA Bridge - AMD64 dual core system, 4G RAM - Drive was a Samsung HM500LI Qubes reported errors on it during the excitement, but repeated badblocks scans from Tails showed zero errors on the drive. Relevant portions from the dmesg save: ---------------------------- ... [Wed Aug 17 06:42:41 2016] usb 1-8: new high-speed USB device number 6 using ehci-pci [Wed Aug 17 06:42:41 2016] usb 1-8: New USB device found, idVendor=152d, idProduct=2329 ... [Wed Aug 17 06:42:41 2016] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=5 [Wed Aug 17 06:42:41 2016] usb 1-8: Product: USB to ATA/ATAPI Bridge [Wed Aug 17 06:42:41 2016] usb 1-8: Manufacturer: JMicron [Wed Aug 17 06:42:41 2016] usb 1-8: SerialNumber: xxxxxxxxxxxx [Wed Aug 17 06:42:41 2016] usb-storage 1-8:1.0: USB Mass Storage device detected [Wed Aug 17 06:42:41 2016] usb-storage 1-8:1.0: Quirks match for vid 152d pid 2329: 8020 [Wed Aug 17 06:42:41 2016] scsi host7: usb-storage 1-8:1.0 ... [Wed Aug 17 06:42:41 2016] scsi 4:0:0:0: Direct-Access SAMSUNG HM500LI PQ: 0 ANSI: 2 CCS [Wed Aug 17 06:42:41 2016] sd 4:0:0:0: Attached scsi generic sg2 type 0 [Wed Aug 17 06:42:41 2016] sd 4:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB) [Wed Aug 17 06:42:41 2016] sd 4:0:0:0: [sdb] Write Protect is off [Wed Aug 17 06:42:41 2016] sd 4:0:0:0: [sdb] Mode Sense: 34 00 00 00 [Wed Aug 17 06:42:41 2016] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [Wed Aug 17 06:42:41 2016] sdb: sdb1 sdb2 [Wed Aug 17 06:42:41 2016] sd 4:0:0:0: [sdb] Attached SCSI disk ... [Wed Aug 17 06:42:52 2016] EXT4-fs (dm-2): INFO: recovery required on readonly filesystem [Wed Aug 17 06:42:52 2016] EXT4-fs (dm-2): write access will be enabled during recovery [Wed Aug 17 06:42:52 2016] EXT4-fs warning (device dm-2): ext4_clear_journal_err:4737: Filesystem error recorded from previous mount: IO failure [Wed Aug 17 06:42:52 2016] EXT4-fs warning (device dm-2): ext4_clear_journal_err:4738: Marking fs in need of filesystem check. [Wed Aug 17 06:42:52 2016] EXT4-fs (dm-2): recovery complete [Wed Aug 17 06:42:52 2016] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null) [Wed Aug 17 06:42:53 2016] systemd-journald[84]: Received SIGTERM ... [Wed Aug 17 06:43:04 2016] Adding 3948540k swap on /dev/mapper/qubes_dom0-swap. Priority:-1 extents:1 across:3948540k FS [Wed Aug 17 06:43:17 2016] EXT4-fs (dm-2): re-mounted. Opts: (null) [Wed Aug 17 06:43:17 2016] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [Wed Aug 17 06:43:17 2016] systemd-journald[638]: Received request to flush runtime journal from PID 1 [Wed Aug 17 06:43:18 2016] sd 4:0:0:0: [sdb] FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [Wed Aug 17 06:43:18 2016] sd 4:0:0:0: [sdb] CDB: Write(10) 2a 00 1d 4c 41 a8 00 00 08 00 [Wed Aug 17 06:43:18 2016] blk_update_request: I/O error, dev sdb, sector 491536808 [Wed Aug 17 06:43:18 2016] Aborting journal on device dm-2-8. [Wed Aug 17 06:43:18 2016] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal [Wed Aug 17 06:43:18 2016] EXT4-fs (dm-2): Remounting filesystem read-only [Wed Aug 17 06:43:18 2016] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal [Wed Aug 17 06:43:18 2016] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal [Wed Aug 17 06:43:18 2016] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal [Wed Aug 17 06:43:18 2016] EXT4-fs error (device dm-2): ext4_journal_check_start:56: Detected aborted journal ... [Wed Aug 17 06:50:11 2016] EXT4-fs (dm-4): recovery complete [Wed Aug 17 06:50:11 2016] EXT4-fs (dm-4): mounted filesystem with ordered data mode. Opts: (null) ----------------------------------------- The systemd-journald receiving a SIGTERM seems a bit odd. And the DID_ERROR line is where things really went south, causing things to flip into readonly mode and the boot to fail. I've done r/w tests on the sector that it reported as bad, and it seems there's nothing wrong with the drive or controller. Due to paranoia (err, caution) I don't want to include the full dmesg dump on the mailing list, but if any developer wants it, I'll send it along via email. I didn't have anything super-critical on any of the VM's, just the configuration, some saved web pages, and lists of packages added to Debian-8 and such, which I can probably recover from the /var/lib/qubes disk images in lost+found. (Where does all the information about templates and VM live? Is it all contained in /var/lib/qubes? Or are there other references to the templates, vm's, etc., scattered throughout the filesystem? There's no hope in plunking that saved /var/lib/qubes in a fresh install, is there?) Cheers. -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/0fa9ea3aef50b98c37329ffa3b24d454.webmail%40localhost. For more options, visit https://groups.google.com/d/optout.
