Date: Mon, 09 Jun 2003 12:56:49 -0400 From: "Michael A. Smith" <msmith@code-fu.com> To: questions@freebsd.org Subject: 2 filesystem problems: blst_radix_free and bad inode number Message-ID: <3EE4BC51.8080201@code-fu.com>
next in thread | raw e-mail | index | archive | help
I've got an AMD Duron-700 running FreeBSD 4.8-RC. It's got a Promise IDE
RAID card and two identical 40GB Maxtor drives (less than six months
old) -- mirrored. No floppy, no CD-ROM, no other IDE drives. The machine
is a headless Samba fileserver in my office. A few days ago, it became
unreachable by SSH (filesharing still worked).
I had to power-cycle it to get it down and plugged into a monitor and
keyboard. It's having two problems when booting:
1) if I try to boot normally (multiuser), it panics when loading the
root filesystem, then reboots (again and again...):
panic: blst_radix_free: freeing free block
2) If I boot single-user, it mounts the root filesystem. When I try to
fsck the various filesystems (/, /var, /tmp, /usr) I get this error when
fscking /dev/ar0s1g (/usr):
fsck: bad inode number 132352 to setinodebuf
All the other filesystems come up clean.
I don't know if the problems are related. I disassembled the array and
booted from one of the mirrored drives alone -- same error -- then I
reassambled the array.
Any ideas on how to solve one or both of these problems?
Thanks!
Michael A. Smith
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3EE4BC51.8080201>