Re: fsck not working on messed-up file system

2012-09-20 Thread Thomas Mueller
> * PLEASE RERUN FSCK * > > Script done on Wed Sep 19 04:17:27 2012 > > Would this indicate a software bug, or is my Western Digital Caviar Green > > 3 TB hard drive failing? > Either something was referencing sectors off the end of the disc, > or the drive is failing. I'd be in

Re: fsck not working on messed-up file system

2012-09-19 Thread Erich Dollansky
Hi, On Wed, 19 Sep 2012 06:05:06 -0400 "Thomas Mueller" wrote: > Script started on Wed Sep 19 04:15:02 2012 > fsck_ffs /dev/ada0p9 just to make sure: the partition was not mounted when you started fsck? > Now I wonder if the file system is really fixed, with possibly some > files in /pkgsrc su

Re: fsck not working on messed-up file system

2012-09-19 Thread Steve O'Hara-Smith
On Wed, 19 Sep 2012 06:05:06 -0400 "Thomas Mueller" wrote: > THE FOLLOWING DISK SECTORS COULD NOT BE READ: 7584318, 7584319, > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 1475900 files, 4638292 used, 211624

fsck not working on messed-up file system

2012-09-19 Thread Thomas Mueller
I have or had a problem with a file system (FreeBSD UFS2) messed up, either by errant software or system freeze/crash. I successfully cross-compiled, from FreeBSD 9.0-STABLE, a NetBSD 5.1_STABLE i386 system to install on 8 GB USB stick. I have both the NetBSD system source as well as pkgsrc and