Hi, I've run into an interesting problem: ad0: 19473MB <Maxtor 92049U6> [39566/16/63] at ata0-master UDMA33 ad1: 19541MB <Maxtor 52049H4> [39703/16/63] at ata0-slave UDMA33 I have swap and two large partitions on ad1: # size offset fstype [fsize bsize bps/cpg] b: 10485760 0 swap # (Cyl. 0 - 10402*) c: 40020561 0 unused 0 0 # (Cyl. 0 - 39702*) e: 25165824 10485760 4.2BSD 1024 8192 16 # (Cyl. 10402*-35368*) f: 4368977 35651584 4.2BSD 1024 8192 16 # (Cyl. 35368*-39702*) However, the f partition will not fsck correctly: %/sbin/fsck -y /dev/ad1s1f ** /dev/ad1s1f BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE LOOK FOR ALTERNATE SUPERBLOCKS? yes USING ALTERNATE SUPERBLOCK AT 32 ** Last Mounted on ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 1 files, 1 used, 2116933 free (13 frags, 264615 blocks, 0.0% fragmentation) UPDATE STANDARD SUPERBLOCK? yes ***** FILE SYSTEM WAS MODIFIED ***** So, running fsck again produces the same identical output. The superblock is not updated. No failures are reported on the console or in the messages file. System is current: FreeBSD 5.0-CURRENT #0: Thu Oct 19 Any ideas on the best way to track this down are appreciated. Thanks, John To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
