I have a hard disk with a filesystem created by an old version of System V Unix that I would like to mount read-only on Linux. fdisk shows me:
/dev/sda1 * 2048 86015 41984 63 GNU HURD or SysV
But when I try to mount it:
mount -t sysv /dev/sda1 /mnt/tmp mount: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error In some cases useful info is found in syslog - try dmesg | tail or so
Here is what I get when I take a look at dmesg immediately after trying the mount command.
root@debian:/# dmesg | tail [ 52.495696] FS-Cache: Netfs 'cifs' registered for caching [ 52.557019] CIFS VFS: default security mechanism requested. The default security mechanism will be upgraded from ntlm to ntlmv2 in kernel release 3.3 [ 157.888559] VFS: Found a SystemV FS (block size = 1024) on device sda1 [ 362.223025] sd 0:0:5:0: [sda] No Caching mode page found [ 362.223034] sd 0:0:5:0: [sda] Assuming drive cache: write through [ 362.230168] sd 0:0:5:0: [sda] No Caching mode page found [ 362.230174] sd 0:0:5:0: [sda] Assuming drive cache: write through [ 362.320058] sda: sda1 [ 362.320059] sda1: <unixware: sda5 > [ 362.397863] VFS: unable to find oldfs superblock on device sda1
I don't seem to be able to run fsck on this file system. Here are my two attempts:
root@debian:/# fsck /dev/sda1 fsck from util-linux 2.20.1 e2fsck 1.42.5 (29-Jul-2012) ext2fs_open2: Bad magic number in super-block fsck.ext2: Superblock invalid, trying backup blocks... fsck.ext2: Bad magic number in super-block while trying to open /dev/sda1 The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> root@debian:/# fsck -t sysv /dev/sda1 fsck from util-linux 2.20.1 fsck: fsck.sysv: not found fsck: error 2 while executing fsck.sysv for /dev/sda1
The file command on the drive device gives:
root@debian:/home/whg# file -s /dev/sda /dev/sda: sticky x86 boot sector; partition 1: ID=0x63, active, starthead 0, startsector 2048, 83968 sectors, code offset 0xc0
I'll appreciate suggestions for anything else I can try.
file -s /dev/sdain it.