Hello folks - My OpenBSD 4.1/i386 firewall crashed last week(seems to be on the 31st), fortunately it did not stop passing packets. There is no log and the console didn't show anything(serial console). I rebooted it today, and it came up in single user mode telling me to run fsck manually, which I tried, but it fails within 2 seconds:
# fsck_ffs -y /dev/rsd0a ** /dev/rsd0a cannot alloc 30231937 bytes for typemap I ran a couple searches and came across this: http://www.openbsd.org/faq/faq14.html#LargeDrive which states "[..]A rough guideline is the system should have at least 1M of available memory for every 1G of disk space to successfully fsck the disk." The filesystem is 228G (disks are 250GB in hardware raid 1) I have 768MB of memory in the machine - real mem = 804859904 (785996K) avail mem = 726327296 (709304K) That is more than triple the amount of memory that the docs say is needed to check a disk of this size, yet it still fails. if I exit out and continue booting it won't let me fsck from multiuser (I expect it would of since the volume is mounted read-only) # fsck_ffs -y /dev/rsd0a ** /dev/rsd0a (NO WRITE) ** Last Mounted on / ** Root file system ** Phase 1 - Check Blocks and Sizes INCORRECT BLOCK COUNT I=21267992 (448 should be 384) CORRECT? no PARTIALLY TRUNCATED INODE I=21267993 SALVAGE? no INCORRECT BLOCK COUNT I=21267996 (8864 should be 8832) CORRECT? no INCORRECT BLOCK COUNT I=21267997 (1152 should be 1120) CORRECT? no INCORRECT BLOCK COUNT I=21267998 (244 should be 128) CORRECT? no INCORRECT BLOCK COUNT I=21268001 (168 should be 160) CORRECT? no INCORRECT BLOCK COUNT I=21268002 (40 should be 32) CORRECT? no [..] Hardware: Intel P3-800 (don't recall what motherboard) 768MB memory 3Ware 8006-2 RAID controller 2 x 250GB Western Digital Raid edition drives in RAID 1 3COM 3c59x PCI 10/100 NIC(management) Intel 4 port 10/100 NIC (DEC 21142/3 chipset) - 2 ports are for a bridging firewall, the other 2 are not used The system ran fine for several weeks, it was about a week after I enabled several rsnapshot jobs that it seemed to crash. I'm not as concerned right now about the crash but of course the inability to run fsck. Any suggestions? thanks nate
