Re: [qubes-users] Emergency shell on boot; qubes_dom0-pool00_tmeta: read failed: Input/output error
On Tuesday, August 20, 2019 at 6:41:36 AM UTC-4, Chris Laprise wrote: > > On 8/19/19 7:08 PM, Dave C wrote: > > Following this thread: > https://groups.google.com/forum/m/#!searchin/qubes-users/Lvconvert/qubes-users/bPxKHOfZ3Mg > > > > > ... I edited my locking mode (from 4 to 1) in /etc/lvm/lvm.conf, then > retried the 'lvm lvconvert --repair ...' > > > > That command has logged one error so far, "print_req_error: critical > medium error, dev nvme1n1, sector [number]" > > Since that one error, it hasn't shown anything. Its been running at > least ½ hour. I'm not sure if its still at work or has failed but hasn't > exited. > > Hi Dave, > > Did the repair operation finish? > > The "critical medium error" indicates a basic hardware access issue, > such as a bad hardware sector or block. Best to run a command like > 'smartctl -H ' to check drive health status. You could also run > a thorough test with 'smartctl -t long '. > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > I was not able to get anything helpful from `smartctl`. But I ran the diagnostics built into my bios on the disk, and that showed read errors. I'm pretty confident the disk has hardware problems. I was able to run `ddrescue` on the disk, so now I am working with a copy of the partition, on a good drive. Unfortunately I still cannot activate the volumes. But I do get different errors: $ sudo lvconvert --repair qubes_dom0/pool00 WARNING: Not using lvmetad because of repair. WARNING: Disabling lvmetad cache for repair command. bad checksum in superblock, wanted 823063976 Repair of thin metadata volume of thin pool qubes_dom0/pool00 failed ( status:1). Manual repair required! I've been searching the web for a next step, but haven't found it. I'm not sure what "manual repair" would entail or whether it is possible at this point. `ddrescue` indicated it was able to rescue 99.99% of the corrupt partition. So I remain hopeful that I can still extract some of the data, but at this point I still cannot activate any volumes in qubes_dom0/pool00. I'm open to any suggestions! -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/86efd8aa-22b6-423e-af23-6672146c84eb%40googlegroups.com.
Re: [qubes-users] Emergency shell on boot; qubes_dom0-pool00_tmeta: read failed: Input/output error
On Tue, Aug 20, 2019, at 3:41 AM, Chris Laprise wrote: > On 8/19/19 7:08 PM, Dave C wrote: > > Following this thread: > > https://groups.google.com/forum/m/#!searchin/qubes-users/Lvconvert/qubes-users/bPxKHOfZ3Mg > > > > ... I edited my locking mode (from 4 to 1) in /etc/lvm/lvm.conf, then > > retried the 'lvm lvconvert --repair ...' > > > > That command has logged one error so far, "print_req_error: critical medium > > error, dev nvme1n1, sector [number]" > > Since that one error, it hasn't shown anything. Its been running at least ½ > > hour. I'm not sure if its still at work or has failed but hasn't exited. > > Hi Dave, > > Did the repair operation finish? Hi Chris, No. It did nothing further, and i eventually used ctrl-C to quit. > > The "critical medium error" indicates a basic hardware access issue, > such as a bad hardware sector or block. Best to run a command like > 'smartctl -H ' to check drive health status. You could also run > a thorough test with 'smartctl -t long '. I very much appreciate the suggestion. Looks like I'll need a recovery usb to run smartctl, which I don't have with me (rookie mistake). I'll spend some time today setting one up. I will post results here when i have them. Thanks, -Dave > > -- > > Chris Laprise, tas...@posteo.net > https://github.com/tasket > https://twitter.com/ttaskett > PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/6ea874ff-16b0-4250-9fed-7f73a808812e%40www.fastmail.com.
Re: [qubes-users] Emergency shell on boot; qubes_dom0-pool00_tmeta: read failed: Input/output error
On 8/19/19 7:08 PM, Dave C wrote: Following this thread: https://groups.google.com/forum/m/#!searchin/qubes-users/Lvconvert/qubes-users/bPxKHOfZ3Mg ... I edited my locking mode (from 4 to 1) in /etc/lvm/lvm.conf, then retried the 'lvm lvconvert --repair ...' That command has logged one error so far, "print_req_error: critical medium error, dev nvme1n1, sector [number]" Since that one error, it hasn't shown anything. Its been running at least ½ hour. I'm not sure if its still at work or has failed but hasn't exited. Hi Dave, Did the repair operation finish? The "critical medium error" indicates a basic hardware access issue, such as a bad hardware sector or block. Best to run a command like 'smartctl -H ' to check drive health status. You could also run a thorough test with 'smartctl -t long '. -- Chris Laprise, tas...@posteo.net https://github.com/tasket https://twitter.com/ttaskett PGP: BEE2 20C5 356E 764A 73EB 4AB3 1DC4 D106 F07F 1886 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/3e9d2f9b-f923-c6ff-697c-f2d8f812ab58%40posteo.net.
[qubes-users] Emergency shell on boot; qubes_dom0-pool00_tmeta: read failed: Input/output error
Following this thread: https://groups.google.com/forum/m/#!searchin/qubes-users/Lvconvert/qubes-users/bPxKHOfZ3Mg ... I edited my locking mode (from 4 to 1) in /etc/lvm/lvm.conf, then retried the 'lvm lvconvert --repair ...' That command has logged one error so far, "print_req_error: critical medium error, dev nvme1n1, sector [number]" Since that one error, it hasn't shown anything. Its been running at least ½ hour. I'm not sure if its still at work or has failed but hasn't exited. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/308b2c20-ce2e-450e-8740-5a922a375419%40googlegroups.com.
[qubes-users] Emergency shell on boot; qubes_dom0-pool00_tmeta: read failed: Input/output error
Cant start qubes on my laptop. The problem started last successful boot. I closed the lid, normally the laptop sleeps with a "breathing" led. But instead the led stayed solid, opening the lid did not turn the screen back on. I couldn't interact with the laptop at that point, so i powered down (for fear of draining the battery to zero). Now I've rebooted, I provide the disk password, then it fails to boot, I'm dropped into dracut emergency shell. To make matters worse, I'm traveling and my only backups are thousands of miles away. Based on advice in similar threads, I've run 'lvm_scan', which shows errors including... /dev/mapper/qubes_dom0-pool00_tmeta: read failed: Input/output error I've also tried 'lvm lvconvert --repair qubes_dom0/pool00', which fails with Read-only locking type set. Write locks are prohibited. I'm comfortable with command lines, but I'm not at all familiar with these lvm commands. Any help is greatly appreciated! What should I try next? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/68f54bff-84d6-4d05-9cd5-ad745dbda6b4%40googlegroups.com.
