Re: UNEXPECTED INCONSISTENCY - fsck
John wrote: pid 22 (fsck), uid 0: exited on signal 11 Segmentation fault # And what's happend if you reboot and do this again ? This happens every time I reboot, same messages, if I just do a fsck (no -y) and answer no to this Clear? question, I get a second, similar BAD/DUP FILE I= 3219137 ... It might be worth while if you can get a second disk, to do a dump, or dd of the first disk over to it, and then trying to fsck with a newer version on the copy (so you can go back if you need to). FreeSBIE would be an ideal choice for this: http://www.freesbie.org (eg. put the two disks in a machine, boot from the FreeSBIE CD, copy the one disk over, fsck the copy, and then try and boot the copy). I suspect you'll need to use dd because of the filesystem corruption. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
RE: UNEXPECTED INCONSISTENCY - fsck
There was recently a power outage in the area, which lasted longer than the UPS did. ... ** Phase 4 - Check Reference Counts BAD/DUP FILE I=3219136 OWNER=13273856 MODE=103210 SIZE=57005967061714584 MTIME=Jun 3 16:08 1970 CLEAR? [yn] yes pid 22 (fsck), uid 0: exited on signal 11 Segmentation fault # And what's happend if you reboot and do this again ? This happens every time I reboot, same messages, if I just do a fsck (no -y) and answer no to this Clear? question, I get a second, similar BAD/DUP FILE I= 3219137 ... A yes this time results in the Segmentation fault again, a no tells me the file system is still dirty, and to run fsck again. I suspect that the drive itself is now damaged. It is FreeBSD 3.4, 2 * 17GB HITACHI SCSI Drives and 128MB RAM. Woouuahhthat's old ;-)) I know, but time and resources have prevented an update so far (not to mention my even more out of date knowledge), I resisted the urge to update until I could do things properly. Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. Heure local/Local time: Sat Oct 29 23:11:05 CEST 2005 Unfortunately, I was not involved with the initial construction and configuration of this system, it just falls to me to get it working again. Looks like it may now be time to do that upgrade. John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
UNEXPECTED INCONSISTENCY - fsck
Hi, There was recently a power outage in the area, which lasted longer than the UPS did. By the time I was notified the server had already crashed. When the power was restored, the computer was restarted, but failed to boot correctly. The error was: /dev/rda0s1e: 1920298835 BAD I=3219136 /dev/rda0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: /dev/rda0s1e (/usr) Automatic files system check failed... help! Ok, so I ran fsck -y, which resulted in: ... ** /dev/rda0s1e ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes 1920298835 BAD I=3219136 ... ( 9 lines cut all ending BAD I=3219136) 1869182049 BAD I=3219136 EXCESSIVE BAD BLKS I=3219136 CONTINUE? [yn] yes 741880625 BAD I=3219137 ... ( 9 lines cut all ending BAD I=3219137) 153103648 BAD I=3219137 EXCESSIVE BAD BLKS I=3219137 CONTINUE? [yn] yes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts BAD/DUP FILE I=3219136 OWNER=13273856 MODE=103210 SIZE=57005967061714584 MTIME=Jun 3 16:08 1970 CLEAR? [yn] yes pid 22 (fsck), uid 0: exited on signal 11 Segmentation fault # It is FreeBSD 3.4, 2 * 17GB HITACHI SCSI Drives and 128MB RAM. I have very little knowledge of the system, and would appreciate any help in solving this problem. Thanks John ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: UNEXPECTED INCONSISTENCY - fsck
Le 29/10/2005 20:41:56+0100, John a ?crit Hi, There was recently a power outage in the area, which lasted longer than the UPS did. By the time I was notified the server had already crashed. When the power was restored, the computer was restarted, but failed to boot correctly. The error was: /dev/rda0s1e: 1920298835 BAD I=3219136 /dev/rda0s1e: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY. THE FOLLOWING FILE SYSTEM HAD AN UNEXPECTED INCONSISTENCY: /dev/rda0s1e (/usr) Automatic files system check failed... help! Ok, so I ran fsck -y, which resulted in: ... ** /dev/rda0s1e ** Last Mounted on /usr ** Phase 1 - Check Blocks and Sizes 1920298835 BAD I=3219136 ... ( 9 lines cut all ending BAD I=3219136) 1869182049 BAD I=3219136 EXCESSIVE BAD BLKS I=3219136 CONTINUE? [yn] yes 741880625 BAD I=3219137 ... ( 9 lines cut all ending BAD I=3219137) 153103648 BAD I=3219137 EXCESSIVE BAD BLKS I=3219137 CONTINUE? [yn] yes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts BAD/DUP FILE I=3219136 OWNER=13273856 MODE=103210 SIZE=57005967061714584 MTIME=Jun 3 16:08 1970 CLEAR? [yn] yes pid 22 (fsck), uid 0: exited on signal 11 Segmentation fault # And what's happend if you reboot and do this again ? It is FreeBSD 3.4, 2 * 17GB HITACHI SCSI Drives and 128MB RAM. Woouuahhthat's old ;-)) Regards. -- Albert SHIH Universite de Paris 7 (Denis DIDEROT) U.F.R. de Mathematiques. Heure local/Local time: Sat Oct 29 23:11:05 CEST 2005 ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
