Re: virtual device both is and isn't a valid file system [complete]
- Date: Tue, 14 May 2019 20:33:40 +0300
- From: Reco <recoverym4n@xxxxxxxxxxxx>
- Subject: Re: virtual device both is and isn't a valid file system [complete]
On Tue, May 14, 2019 at 10:20:47AM -0700, Ross Boylan wrote:
> Noticing the "write on read-only" error, and remembering it should be
> read-only, I added that to the mount options. Which still failed, but
> root@barley:~/tempserver-check# date; strace -f mount -r
> /dev/stretch-vg/boot stretch_boot
> Tue 14 May 2019 10:07:05 AM PDT
> "/root/tempserver-check/stretch_boot", "ext4", MS_RDONLY, NULL) = 0
I don't see a failure here.
> +++ exited with 0 +++
> root@barley:~/tempserver-check# dmesg | tail
> [76983.987331] EXT4-fs (dm-30): mounted filesystem with ordered data
> mode. Opts: (null)
Nor I do not see it here. It should be mounted.
> The bad sector was at 7,724,531,336, 8 sectors long, using 512b
> sectors and decimal numbers.
> The partition sdf2 starts at sector 4096 and ends at 7814035455. Even
> with all the layers, that doesn't seem to be the one reporting the
> error. And on sdf2 reading that location should not be a hardware
> error, just junk data.
"Can't read superblock on ..." is a red herring here.
See my other e-mail.