mounting a qemu-img'd file error?

[gaikokuji...@gmail.com]

I converted a vdi file over to a raw file which seemed to go fine but mounting it is not going so well. mount seems to be having problems with the file sys. I have tried auto but no luck, I tried manually specifying but no luck. It was whonix so I assumed it was ext3 or 4 (or 2, tried em all) but no luck.
I have tried specifying offset points (2480 here) and just "loop" etc... nada

fdisk -l tells me:
Disk whonix.raw: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x3d6b07dc

Device Boot Start End Sectors Size Id Type
whonix.raw1 2048 8388607 8386560 4G 83 Linux

thoughts?

[gaikokuji...@gmail.com]

No thoughts? Anyone? Perhaps avid whonix people have run into this? or know of other ways to get stuff off a whonix vdi file?

[Drew White]

What did you use to convert it?
What version did you use to convert it?
What version VDI was it?

[gaikokuji...@gmail.com]

doh, sorry bout that

> What did you use to convert it?

qemu-img

> What version did you use to convert it?

v2.4.1

> What version VDI was it?

... really not sure :(
It was made about 1-1.5 years ago

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Try `losetup -P /dev/loop0 whonix.raw`, then mount /dev/loop0p1.

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX9xJiAAoJENuP0xzK19csoNMH/jUcyBOwKFmyHsYVaEt/3TrX
HU48pwq0WOTrwNwvtFl0WQW0PTH44vMrwoBlhYRsqlZ+S6PqBJXPukdnlyx2T6V4
imZU1DgymFCBMNvkdlq1tFDEU8nt0JjkS7USL3Vfc0pyS+WXwSobHIJaS7mIbWzL
XYr0mECzsVhVE1WH4QXcZO9J3v68tRPKmFKTj7jpThsFDgvRx5868Bj7URw1CqUZ
uhAEmTd33ka3mgvHi3+ityC10AQ8/DhMt+MgSpfwH231L2apuPXkVAQ3TegafboW
0YmRxP3n0r6HalYmH0Gdr160avkkM7qXmHgJO5IaaIGheAcnLC+PUC4xkRkHM0U=
=ANsq
-----END PGP SIGNATURE-----

[gaikokuji...@gmail.com]

Assuming I got it right I am still getting filesystem errors (or "can't find in fstab), here is what I have tried:

[user@untrusted MV]$ sudo losetup -P /dev/loop0 whonix.raw
[user@untrusted MV]$ mount /dev/loop0p1
mount: can't find /dev/loop0p1 in /etc/fstab
[user@untrusted MV]$ sudo mount -t auto /dev/loop0p1 ~/whonix/
mount: wrong fs type, bad option, bad superblock on /dev/loop0p1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.
[user@untrusted MV]$ sudo mount /dev/loop0p1 ~/whonix/
mount: wrong fs type, bad option, bad superblock on /dev/loop0p1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.
[user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 ~/whonix/
mount: can't find /home/user/whonix/ in /etc/fstab
[user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 whonix.raw ~/whonix/
mount: /dev/loop1 is write-protected, mounting read-only
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.

[Marek Marczykowski-Górecki]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, Oct 07, 2016 at 11:30:58AM -0700, gaikokuji...@gmail.com wrote:
> On Thursday, October 6, 2016 at 11:11:47 PM UTC-4, Marek Marczykowski-Górecki wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On Mon, Oct 03, 2016 at 06:51:39PM -0700, gaikokuji...@gmail.com wrote:
> > > I converted a vdi file over to a raw file which seemed to go fine but mounting it is not going so well. mount seems to be having problems with the file sys. I have tried auto but no luck, I tried manually specifying but no luck. It was whonix so I assumed it was ext3 or 4 (or 2, tried em all) but no luck.
> > > I have tried specifying offset points (2480 here) and just "loop" etc... nada
> > >
> > > fdisk -l tells me:
> > > Disk whonix.raw: 4 GiB, 4294967296 bytes, 8388608 sectors
> > > Units: sectors of 1 * 512 = 512 bytes
> > > Sector size (logical/physical): 512 bytes / 512 bytes
> > > I/O size (minimum/optimal): 512 bytes / 512 bytes
> > > Disklabel type: dos
> > > Disk identifier: 0x3d6b07dc
> > >
> > > Device Boot Start End Sectors Size Id Type
> > > whonix.raw1 2048 8388607 8386560 4G 83 Linux
> > >
> > > thoughts?
> >
> > Try `losetup -P /dev/loop0 whonix.raw`, then mount /dev/loop0p1.
> >
>

> Assuming I got it right I am still getting filesystem errors (or "can't find in fstab), here is what I have tried:
>
> [user@untrusted MV]$ sudo losetup -P /dev/loop0 whonix.raw
> [user@untrusted MV]$ mount /dev/loop0p1
> mount: can't find /dev/loop0p1 in /etc/fstab
> [user@untrusted MV]$ sudo mount -t auto /dev/loop0p1 ~/whonix/
> mount: wrong fs type, bad option, bad superblock on /dev/loop0p1,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
> [user@untrusted MV]$ sudo mount /dev/loop0p1 ~/whonix/
> mount: wrong fs type, bad option, bad superblock on /dev/loop0p1,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.
> [user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 ~/whonix/
> mount: can't find /home/user/whonix/ in /etc/fstab
> [user@untrusted MV]$ sudo mount -t auto -o /dev/loop0p1 whonix.raw ~/whonix/
> mount: /dev/loop1 is write-protected, mounting read-only
> mount: wrong fs type, bad option, bad superblock on /dev/loop1,
> missing codepage or helper program, or other error
>
> In some cases useful info is found in syslog - try
> dmesg | tail or so.

Have you followed this suggestion: dmesg | tail
Maybe this filesystem is really broken?

- --
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJX9/NuAAoJENuP0xzK19cs9S0H/j+lhoUjPFu7plLipSnHmZ1b
U4nuO5DMEANLX8sKeC4zPQlatpyObqUSeseCcuKDeP/xcFymtYPbZIVaxuGHjvBa
1Aa6Z3A2A3i9P7p8efMZWB3qHlDtapxUDURcwuYsakYyKjAy+16g+BD7rSyEX7zx
tHV/zYO8BRq9arB3TNGbwDaz0+HMyQ0mjemyKlk3OCNm+VMAo5JQyeMPv6xP0o8E
fibOlZd9YTH2UBYrgVFarsapJYOypb6UxjRQCZGuARbuWCV3NoURD2IbNp6QRcWZ
VkYDgcCMsuChOhiiO91vGrZCe7A5kn83LirzZ9Fd0HOynyUde8SSSEuW597SQQA=
=d3fr
-----END PGP SIGNATURE-----