Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Reco
Hi. 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 > differently: > root@barley:~/tempserver-check# date; strace -f mount -r > /dev

Re: virtual device both is and isn't a valid file system [solved]

2019-05-14 Thread Ross Boylan
On Tue, May 14, 2019 at 10:20 AM 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 > differently: Well, it failed differently in the sense that it succeeded :) Yay! I was fooled by t

Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Ross Boylan
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 differently: root@barley:~/tempserver-check# date; strace -f mount -r /dev/stretch-vg/boot stretch_boot Tue 14 May 2019 10:07:05 AM PDT execve("/usr/bin/mount

Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Reco
Hi. On Tue, May 14, 2019 at 09:52:10AM -0700, Ross Boylan wrote: > Here's the info: Nothing interesting in the strace output, short of: : ... mount("/dev/mapper/stretch--vg-boot", "/root/tempserver-check/stretch_boot", "ext4", 0, NULL) = -1 EIO (Input/output error) ... The reason being

Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Ross Boylan
Here's the info: root@barley:~/tempserver-check# date; strace -f mount /dev/stretch-vg/boot stretch_boot Tue 14 May 2019 09:33:01 AM PDT execve("/usr/bin/mount", ["mount", "/dev/stretch-vg/boot", "stretch_boot"], 0x7ffed2c87238 /* 26 vars */) = 0 brk(NULL) = 0x5575487e

Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Reco
Hi. On Tue, May 14, 2019 at 01:28:47PM -, Curt wrote: > On 2019-05-14, Reco wrote: > > Hi. > > > >> I am trying to read some files off of a virtual disk without running > >> the entire virtual machine. > > > > Can you post the output of (in that order): > > > > strace -f mount /de

Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Curt
On 2019-05-14, Reco wrote: > Hi. > >> I am trying to read some files off of a virtual disk without running >> the entire virtual machine. > > Can you post the output of (in that order): > > strace -f mount /dev/stretch-vg/boot stretch_boot > dmesg | trail I looked for trail (it's not in my

Re: virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Reco
Hi. > I am trying to read some files off of a virtual disk without running > the entire virtual machine. Can you post the output of (in that order): strace -f mount /dev/stretch-vg/boot stretch_boot dmesg | trail e2fsck -fn /dev/stretch-vg/boot Reco

virtual device both is and isn't a valid file system [complete]

2019-05-14 Thread Ross Boylan
[Sorry: original sent before complete; ignore earlier message] I am trying to read some files off of a virtual disk without running the entire virtual machine. (Running a VM would involve at least using a later version of the VirtualBox, or a switch to KVM, and I already have enough complexity).

virtual device both is and isn't a valid file system

2019-05-14 Thread Ross Boylan
When I attempt to mount a block device, I get the error: - root@barley:~/tempserver-check# date; mount /dev/stretch-vg/boot stretch_boot Mon 13 May 2019 11:42:15 PM PDT mount: /root/tempserver-check/stretch_boot: can't read superblock on /dev/mapper/stretch--vg-boot.