-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Wed, Dec 23, 2015 at 09:49:54AM -0300, Renaud OLGIATI wrote: > On Wed, 23 Dec 2015 11:11:08 +0000 > Lisi Reisz <lisi.re...@gmail.com> wrote: > > > On Wednesday 23 December 2015 10:23:41 to...@tuxteam.de wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > > Hash: SHA1 > > > > > > On Wed, Dec 23, 2015 at 07:41:00AM -0300, Renaud OLGIATI wrote: > > > > Given a Sata HD that was part of a RAID1 array on a now defunct Wheezy > > > > system. > > > > > > > > Is there a way to mount it on another Wheezy system to recover the data > > > > ? > > > > > > > > I have tried to mount it, and get > > > > > > > > root@ron:/home/ron # mount -t ext4 /dev/sdi9 /media/eSata > > > > mount: wrong fs type, bad option, bad superblock on /dev/sdi9, > > > > missing codepage or helper program, or other error > > > > In some cases useful info is found in syslog - try > > > > dmesg | tail or so > > > > > > > > What file type should I give for the -t param of mount ? > > > > Try to omit the explicit file system ("-t ext4") in the mount > > > invocation above: mount should be able to find out by itself -- > > > unless you positively know that ext4 is right. > > > If it is demanding a file type, how about "-t auto"? > > root@ron:/home/ron # mount /dev/sdi9 /media/eSata > mount: you must specify the filesystem type > > root@ron:/home/ron # mount -t auto /dev/sdi9 /media/eSata > mount: you must specify the filesystem type
That means mount can't guess what filesystem is on /dev/sdi9. I fear we won't be better at it. But you could try something like: sudo dd if=/dev/sdi9 bs=1024 count=1 | file - Perhaps 'file' can shed some light onto it (it doesn't always) Regards - -- tomás -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlZ6lJIACgkQBcgs9XrR2kYRQgCePkCV+fbq8Y9QKzkSBdQQFrzT GAgAn2cWIzhjNnpg68iKaCzAoVlsuNMT =LdsL -----END PGP SIGNATURE-----