Hello forum and may I first thank the Creator/s for establishing this non-Google support service which I have been wishing for since January 2018.
That was when I installed Qubes OS 3.2 on a 1TB external USB HDD and after a few early revisions it has run extraordinarily nicely ever since … until today, Sunday 20-09-2020.
Excuse me for explaining the almost 100% certain catalyst for this inaugural system failure because even though it seems so unlikely to have caused this ‘read-only file system’ problem on boot, this was the one and only change I have made in over two(2) years, and my system disaster occurred immediately after I foolishly did so.
I wanted to hook up a Zyxel external USB modem dongal to try to increase my Wi-Fi reception better than the built-in Toshiba Satellite laptop’s Wi-Fi modem. After plugging in the USB modem to a USB slot on a 3-way multi-USB adaptor, there was seemingly no recognition by the network devices list, and so I thought it wise to try to tweak the sys-net VM somehow.
I selected the two available Intel USB ‘thingos’ listed and soon discovered that my external KBD and mouse (also connected via the 3-way multi-USB adaptor) lost communication. Oops! I probably should have cleared all the junk off the laptop KBD and touchpad and shutdown properly, but I have often had times when the external USB HDD has been bumped in its socket and had to hold down the power button for the usual ten seconds (10s) an so that is what I did this time too,
Now all hell has broken loose on my beloved Qubes OS system and I can’t boot past the ‘Disk Password’ routine. There are two years of carefully arranged bookmarks on sixteen(16) different VMs at stake, but at least all the data is currently safe and accesible through this Linux Mint system which is the laptop’s default OS when the external USB HDD is disconnected at boot.
Here is the list of error messages which I have written out on pen and paper during the boot process, and then retyped here. Please excuse any errors in my reverse-engineering of the errors.
system:crond.service.failed to load environment files: input/output error Buffer I/O error on dev dom 0, logical block 1, lost async page write Buffer I/O error on dev dom 0, logical block 1036, lost async page write Buffer I/O error on dev dom 0, logical block 1038, lost async page write Buffer I/O error on dev dom 0, logical block 15728641, lost async page write Buffer I/O error on dev dom 0, logical block 15728747, lost async page write Buffer I/O error on dev dom 0, logical block 20971536, lost async page write Buffer I/O error on dev dom 0, logical block 20971554, lost async page write Buffer I/O error on dev dom 0, logical block 20971558, lost async page write Buffer I/O error on dev dom 0, logical block 20971561, lost async page write Buffer I/O error on dev dom 0, logical block 20971564, lost async page write Buffer I/O error on device dm-0, logical block 391505 ... " " " " " " " " 391513 Aborting journal on device dm-0-0. JBD2: Error-5 detected when updating journal superblock for dm-0-0 EXT4-fs error (device dm-0): ext4_journal_check_start:61: detected aborted journal EXT4-fs (dm-0): Remounting filesystem read-only EXT4-fs (dm-0): previous I/O error to superblock detected systemd_journald : Failed to truncate file to its own size: Read-only file system " " " " " " **x 10** " " " " " " " " systemd: systemd_journald.service: Watchdog timeout (limit 3min)!
It appears to me that some sort of flag has left unlowered during my clumsy system crash shutdown but I hope that there might be others here at this forum who can gather from that list above what I might have done wrong and perhaps provide me with some miraculous quick and easy fix to solve my own self-made disaster.
I would rather try to reinstall Qubes OS 3.2 in some way that allows me to retain all the existing VMs and browser bookmark data than have to run a fresh install and then have to reconfigure all the custom VMs and then start restoring the bookmarks list from memory.
Please help if you are able and I apologise for such a long explanation. This is the least information I consider relevant besides the point that I am awaiting my I7 laptop’s depreciation period before buyng a replacement with the newer CPU so I can use version 4.
Thank you for reading and thanks again for this support forum.