On 02/10/2016 07:35 PM, TWS Admin wrote: > Please remove julius.robe...@wildernes.org.au > <mailto:julius.robe...@wildernes.org.au> from this list, he's no longer > working with us. > > thanks, > > the Wilderness society > > On 9 February 2016 at 19:57, Ritesh Raj Sarraf <r...@researchut.com > <mailto:r...@researchut.com>> wrote: > > Hello, > > On my RPi2, I saw the following reported by my kernel. > > [156278.815976] sd 1:0:0:0: [sdb] UNKNOWN(0x2003) Result: > hostbyte=0x00 driverbyte=0x00 > [156278.823864] sd 1:0:0:0: [sdb] CDB: opcode=0x28 28 00 9a 40 04 47 > 00 00 08 00 > [156278.831152] blk_update_request: I/O error, dev sdb, sector > 2587886663 > > > This got me worried so I ran an fsck on my drive. Following is the > report. > > 130 pi@pi:~$ sudo fsck -cvkv /dev/sdb1 > [sudo] password for pi: > fsck from util-linux 2.25.2 > e2fsck 1.42.12 (29-Aug-2014) > Checking for bad blocks (read-only test): done > > SEAGATE: Updating bad block inode. > Pass 1: Checking inodes, blocks, and sizes > Pass 2: Checking directory structure > Pass 3: Checking directory connectivity > Pass 4: Checking reference counts > Pass 5: Checking group summary information > > SEAGATE: ***** FILE SYSTEM WAS MODIFIED ***** > > 20013 inodes used (0.02%, out of 122101760) > 8944 non-contiguous files (44.7%) > 53 non-contiguous directories (0.3%) > # of inodes with ind/dind/tind blocks: 0/0/0 > Extent depth histogram: 16695/3216/62 > 416471936 blocks used (85.28%, out of 488378008) > 0 bad blocks > 63 large files > > 17086 regular files > 2885 directories > 0 character device files > 0 block device files > 0 fifos > 0 links > 33 symbolic links (32 fast symbolic links) > 0 sockets > ------------ > 20004 files > 1 pi@pi:~$ > > > From the report, it says that there are 0 bad blocks. So is this a > bug in e2fsprogs ? > > > -- > Ritesh Raj Sarraf > RESEARCHUT -- http://www.researchut.com > "Necessity is the mother of invention" > > fsck checks primarily a directory structure not the hard drives. you might want to try
badblocks -svn /dev/sdb Like always, backup your drive before you do this. -- Joseph Loo j...@acm.org
