you seem to have misunderstood something:
- the HD with the problem is sda, which is mounted internally
- because i can’t access sda, i’m using sdb which is connected externally via USB.
actually, i have a backup on a NAS, but i can’t access it. that’s why i started the other thread.
yes, I can see that but what I asking is which drive are you running the OS now?
reason I assume you’re booting from external drive is because your lvm is in sdb and cause the boot failure.
if you’re boot from sdb, it shouldn’t be any issue to boot unless you’re automount sda drive, thus I asked the /etc/fstab to be review - so that you could comment on sda drive and mount it manually.
from what I seeing sdb is the one had issue; just remove it and mount your sda on liveUSB to get your file back
i used to boot from sda, with sdb not even connected. then sda failed to boot, and that’s when i started using sdb to boot from. i was lucky to have an external HD with ubuntu installed.
mounting sda manually is no good because several sectors are corrupted, that’s why it won’t boot. if it was that easy, i would have pulled my files off onto sdb, and this thread wouldn’t exist
is it same error you had now?
this one I’m confuse; you supposed to run fsck on /dev/sda3 instead your lvm (I refer based on this reply). from there, you may mount that partition (if there’s no error).
have you tried mount on liveUSB session? you can fsck from there too.
but I still prefer you run rescue mode and review, because I didn’t see where your LUKS for /dev/sda3 (probably main reason why you can’t fsck or mount the partition).
This topic was automatically closed after 29 days. New replies are no longer allowed.