Leonard den Ottolander [EMAIL PROTECTED] writes:
Hi Alan,
Downsizing has taken it toll in my company and now I've got the job of
recovering the files from a couple of projects off a couple of drives
a co-worker was using on a FreeBSD OS box. With all the other
filesystems addressed
Hi Alan,
mount -t ufs -o ufstype=44bsd /dev/sdb[5-8] /mnt/BSD
meaning, for each of the entries under the extended partition entry
each rendering the generic and not too helpful message:
mount: wrong fs type, bad option, bad superblock on /dev/hda[5-8],
or too many mounted file
Hi Alan,
mount -t ufs -o ufstype=44bsd /dev/sdb[5-8] /mnt/BSD
Partition check:
sdb: sdb1
sdb1: sdb5 sdb6 sdb7 sdb8
Iirc you have to mount the whole slice at once. The subpartitions are then
recognized. In your case that would be mount -t ufs -o ufstype=44bsd /dev/sdb1
Downsizing has taken it toll in my company and now I've got the job of
recovering the files from a couple of projects off a couple of drives
a co-worker was using on a FreeBSD OS box. With all the other
filesystems addressed by kernel modules, I was sure I'd be able to
scan the drive. Now I'm
Hi Alan,
Downsizing has taken it toll in my company and now I've got the job of
recovering the files from a couple of projects off a couple of drives
a co-worker was using on a FreeBSD OS box. With all the other
filesystems addressed by kernel modules, I was sure I'd be able to
scan the
