Date: Thu, 10 Sep 2015 10:35:46 +0100 From: Matthew Seaman <matthew@freebsd.org> To: freebsd-questions@freebsd.org Subject: Re: xenix (sysv) filesystem and FreeBSD Message-ID: <55F14EF2.7060204@freebsd.org> In-Reply-To: <20150910104034.b3439c2c.freebsd@edvax.de> References: <55F13B5A.3070408@pahlevanzadeh.org> <20150910104034.b3439c2c.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --mGImg4iQplmchxoqbk35634RL05xInwuC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On 09/10/15 09:40, Polytropon wrote: > On Thu, 10 Sep 2015 12:42:10 +0430, Mohsen Pahlevanzadeh wrote: >> I have a hdd (scsi), about 1985. I can detect hdd and geometry, But=20 >> maybe linux kernel removed xenix (sysv) filesytem. >> Question is , 1. Can i detect it via freebsd? >=20 > You should at least _try_ it. Depending on the partitioning, > and if I remember correctly, Xenix uses some strange SCI HTFS > and maybe UFS (not entirely sure), and the partitioning is > either some MBR or "dedicated" schema, then, if everything > else works, you should see: >=20 > /dev/da0 > /dev/da0s1 <- a slice > /dev/da0s1a <- a partition > /dev/da0s1d > /dev/da0s1e > and so on, >=20 > or maybe even >=20 > /dev/da0 > /dev/da0a <- a partition without a slice > /dev/da0d > /dev/da0e > and so on, >=20 > if, let's say, da0 corresponds to the SCSI disk. >=20 > Use the command >=20 > # fdisk da0 >=20 > to find out which partitioning schema (if any) has been used, > and then maybe >=20 > # disklabel da0 >=20 > or >=20 > # disklabel da0s1 >=20 > to identify the partitions. Kepp an eye on which files appear > in /dev. >=20 >=20 >=20 >> 2. Can I read xenix (sysv)=20 >> filesytem ? >=20 > You could try "mount -t ufs -o ro <device> /mnt" for each of > the partitions found, but this will probably fail. However, you > can use a "dump | restore" approach, maybe this works. If not, > you can at least resort to forensic tools which will read the > data independently from the file system information; you might > lose file names, but you can recover file contents. This can > be done in "raw reads" from the disk device. >=20 >=20 >=20 > But as far as I know, _native_ support for classic SysV file > systems does not exist on FreeBSD, nor does it on any other > platform. It's an excavation job for the mantally insane. :-) The other thing you should certainly do is use dd(1) to copy the drive contents to a local file on your machine. You can create a file-backed md(4) device using the copy and use that for all your investigations with fdisk(8) etc. It's a lot less stressful should you fat-finger an fdisk(8) and destroy your copy, rather than killing your one and only original drive. Also, a file-backed md on a modern system is probably going to be faster than a 1985-era hard drive... Cheers, Matthew --mGImg4iQplmchxoqbk35634RL05xInwuC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJV8U7yAAoJEABRPxDgqeTnH9UP/jVAlTKskyzp2j/HSoKANm3G n0DpVtMFXoeINJUmdFgqnBh22hYvji6j/H6Y4CyBZRKddOpCIEHq1woGztrBZ3DO XSIipfEmayLLoxxpesywDh4CcwRWMw4BQmXGuwqPppdCrHkj2Q/kWYXYc2zDmret 6pVulQUwEdGBMc6jSvgA7EGN1LRPHPfqyX2VizQU6s6OzfrD7lp7veHe6wiXst5j cAKfIfvCbq1ktfFoTJoE4toSMZksA0mXJa1yUbspXfwD9jyE1LzUS2k3zm0Wy/6d +axALCyx3TRMeNzCwncxveHYHgR+h5QgK/E/T0pGBCFG+cS+R6KsfQLhEu0FrrXs RF2sbHz5wla1LDbzNJ+PUeSEZBM3i/5a1HybrEuGVeXPWWJjkVGDCZsUdwSdPeCS 7MGLS8exh5DmBzduHlVyHwxmwc2Ym8K8xzc93lWbNRjW5Usw3Yel/h4F+rG5GAPM R16Sb8HLiZCjpcSjP2crTW1DvHUZKknXnAHFLKNKUPJ6O/0S0hFigPdrJPV9xu6o SD3dW1yA7JkR/BEWSBGDhoFoVM6bd6V9dRVWwb8TKd/JD69XfZF5rUVYmfEf/OaF yFTX4GJvSP5aV3+WAfELuDK4xY6EzAuZ3s2cKZ4aGNfMb4tE7qNURHqPJN6z60Oe UExo3lyKyXV7Yg+UVfqd =W4NB -----END PGP SIGNATURE----- --mGImg4iQplmchxoqbk35634RL05xInwuC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55F14EF2.7060204>