fsck woes: no '-b' option?

darren david darren at 3x3x3.org
Tue Oct 18 23:22:51 PDT 2005


hi all-

i had a wonderful crash ( my fault, don't mess with hardware while the 
box is still running, no matter how steady your hands :| ). anyhoo, my 
3ware RAID 5 volume is a bit unhappy now. when running fsck, i get the 
following:

----

# fsck -y /dev/da0s1d
** /dev/da0s1d

CANNOT READ BLK: 1464762144
CONTINUE? yes

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 1464762144, 1464762145, 
1464762146, 1464762147,

LOOK FOR ALTERNATE SUPERBLOCKS? yes

32 is not a file system superblock

CANNOT READ BLK: 458687976
CONTINUE? yes

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 458687976, 458687977, 
458687978, 458687979, 458687980, 458687981, 458687982, 458687983, 
458687984, 458687985, 458687986, 458687987, 458687988, 458687989, 
458687990, 458687991,

CANNOT READ BLK: 917375920
CONTINUE? yes

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 917375920, 917375921, 
917375922, 917375923, 917375924, 917375925, 917375926, 917375927, 
917375928, 917375929, 917375930, 917375931, 917375932, 917375933, 
917375934, 917375935,

CANNOT READ BLK: 1376063864
CONTINUE? yes

THE FOLLOWING DISK SECTORS COULD NOT BE READ: 1376063864, 1376063865, 
1376063866, 1376063867, 1376063868, 1376063869, 1376063870, 1376063871, 
1376063872, 1376063873, 1376063874, 1376063875, 1376063876, 1376063877, 
1376063878, 1376063879,
SEARCH FOR ALTERNATE SUPER-BLOCK FAILED. YOU MUST USE THE
-b OPTION TO FSCK TO SPECIFY THE LOCATION OF AN ALTERNATE
SUPER-BLOCK TO SUPPLY NEEDED INFORMATION; SEE fsck(8).


----

this is all well and good, but according to 'man 8 fsck', there is no 
'-b' option. any thoughts on way around this? I'm running on 5.4-STABLE.

thanks in advance,
darren david


More information about the freebsd-questions mailing list