Filesystem panic - one hd inaccessable under 6-STABLE

[Bernd Walter]

On Fri, Nov 04, 2005 at 01:48:44PM -0600, Eric Anderson wrote:
> Jochen Gensch wrote:
> >Hi!
> >
> >I've encountered a very bad thing here. I was compiling openoffice, when 
> >the system suddenly paniced and rebooted. When it was booting again it 
> >said:
> >
> >Nov  4 19:53:15 incmc kernel: Trying to mount root from ufs:/dev/ad0s3a
> >Nov  4 19:53:15 incmc savecore: reboot after panic: ufs_dirbad: bad dir
> >Nov  4 19:53:15 incmc savecore: writing core to vmcore.0
> >
> >The bad news is, one harddisk, which was attached via firewire lost its 
> >superblock and cannot be used any more. This is my backup drive :-(. A 
> >fsck -t uds /device ends up with:
> >
> >fsck -t ufs /dev/da0s1
> >** /dev/da0s1
> >Cannot find file system superblock
> >ioctl (GCINFO): Inappropriate ioctl for device
> >fsck_ufs: /dev/da0s1: can't read disk label

If you have the filesystem on a slice (e.g. da0s1) and not a partition
(e.g. da0s1e) it shouldn't be an UFS one.

> >both harddrives are running with ufs2 + softupdates

Then check with disklabel da0s1 what partitions you have and use the
4.2BSD ones.

> >I'm scared :-(
> 
> try:
> 
> fsck -b 160 /dev/da0s1

fsck_ufs - fsck won't pass -b option I think, but that requires a 4.2BSD
partition as well.

-- 
B.Walter                   BWCT                http://www.bwct.de
bernd at bwct.de                                  info at bwct.de