• The forum software that supports hummy.tv has been upgraded to XenForo 2.3!

    Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.

2tb seagate skyhawk, 1st bad sector after 4 years

R

rodp

Member
I came across the below thread about skyhawk hdd back from 2020 so thought i would reply...
MartinLiddle said:
Several people here have fitted SkyHawks and so far (fingers crossed) nobody has reported problems.
Click to expand...

4 years down the line after buying a 2tb skyhawk around sept 2020, I've just got my first group of bad sectors. However my humax seems to be very hung up about it as the whole system was unresponsive whilst trying to decrypt a recently recorded program (crystal maze). I saw the alert on webif (200 odd unallocated or pending sectors) and so ran fixdisk in maintenace mode (no options). However, I've struggled with this as each time it would pause when it found a bad sector and ask me to type 'y' for each bad sector! Is there a way to automate this? It then ran into errors saying it couldn't find the LBA and so then it ran the long check and after about 4 hours it then started to run debugfs to check again the area which was bad and find which file / path / inode it was affecting. This last process (checking to see if the block is in use then searching for inode) is really really slow. Is there anyway to speed this up as it is still working on the same file 9 hours down the line?

I'm asuming that once it finally fishes it will have saved a log somewhere as my telent client keeps bombing out and i have to reconnect?

Thanks

This is the log so far. Is the message 'LBA not found yet' a worry given it's age?

I will post the smart diagnostics once the humax is up and running again but it might be days at this rate!

Code: 
Humax HDR-Fox T2 (humax) 1.03.12/3.13
humax# menu
Menu version 1.24
      /---------------------------------------------\
      |  M A I N T E N A N C E   M O D E   M E N U  |
      \---------------------------------------------/
  [ Humax HDR-Fox T2 (humax) 1.03.12/3.13 ]
  Note: Some areas of the hard disk are not mounted.
        Not all functions will be available.
        (normal if you have just run a disk check)
*** Note: A hard disk check and repair is in progress. ***
 connect - Connect to running hard disk check and repair.
  cancel - Cancel running hard disk check and repair.
    diag - Run a diagnostic.
     cli - System command line (advanced users).
Please select option: connect
----------------------------------------------------------------------
Sat Nov  9 12:10:47 GMT 2024: Fix-disk run starting...
----------------------------------------------------------------------
Checking disk sda (4096 byte sectors)
Running short disk self test
Error at LBA 3668596752
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668596752 - 3668596759 (8 blocks)
Also checking blocks 3668596752 - 3668596759 (8 blocks)
    Block 3668596752 - OK
    Block 3668596753 -                      - Repaired
                     - Repaired
    Block 3668596754 -                      - Repaired
                     - Repaired
    Block 3668596755 -                      - Repaired
                     - Repaired
    Block 3668596756 -                      - Repaired
                     - Repaired
    Block 3668596757 -                      - Repaired
                     - Repaired
    Block 3668596758 -                      - Repaired
                     - Repaired
    Block 3668596759 -                      - Repaired
                     - Repaired
Running short disk self test
Pending sector error(s) found
LBA has not yet been found
Do you wish to continue? [Y/N]: Running long disk self test
Error at LBA 3668512200
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668512200 - 3668512207 (8 blocks)
Also checking blocks 3668512200 - 3668512207 (8 blocks)
    Block 3668512200 - OK
    Block 3668512201 -                      - Repaired
                     - Repaired
    Block 3668512202 -                      - Repaired
                     - Repaired
    Block 3668512203 -                      - Repaired
                     - Repaired
    Block 3668512204 -                      - Repaired
                     - Repaired
    Block 3668512205 -                      - Repaired
                     - Repaired
    Block 3668512206 -                      - Repaired
                     - Repaired
    Block 3668512207 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668592776
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668592776 - 3668592783 (8 blocks)
Also checking blocks 3668592776 - 3668592783 (8 blocks)
    Block 3668592776 - OK
    Block 3668592777 -                      - Repaired
                     - Repaired
    Block 3668592778 -                      - Repaired
                     - Repaired
    Block 3668592779 -                      - Repaired
                     - Repaired
    Block 3668592780 -                      - Repaired
                     - Repaired
    Block 3668592781 -                      - Repaired
                     - Repaired
    Block 3668592782 -                      - Repaired
                     - Repaired
    Block 3668592783 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668592784
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668592784 - 3668592791 (8 blocks)
Also checking blocks 3668592784 - 3668592791 (8 blocks)
    Block 3668592784 - OK
    Block 3668592785 -                      - Repaired
                     - Repaired
    Block 3668592786 -                      - Repaired
                     - Repaired
    Block 3668592787 -                      - Repaired
                     - Repaired
    Block 3668592788 -                      - Repaired
                     - Repaired
    Block 3668592789 -                      - Repaired
                     - Repaired
    Block 3668592790 -                      - Repaired
                     - Repaired
    Block 3668592791 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668594760
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668594760 - 3668594767 (8 blocks)
Also checking blocks 3668594760 - 3668594767 (8 blocks)
    Block 3668594760 - OK
    Block 3668594761 -                      - Repaired
                     - Repaired
    Block 3668594762 -                      - Repaired
                     - Repaired
    Block 3668594763 -                      - Repaired
                     - Repaired
    Block 3668594764 -                      - Repaired
                     - Repaired
    Block 3668594765 -                      - Repaired
                     - Repaired
    Block 3668594766 -                      - Repaired
                     - Repaired
    Block 3668594767 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668594768
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668594768 - 3668594775 (8 blocks)
Also checking blocks 3668594768 - 3668594775 (8 blocks)
    Block 3668594768 - OK
    Block 3668594769 -                      - Repaired
                     - Repaired
    Block 3668594770 -                      - Repaired
                     - Repaired
    Block 3668594771 -                      - Repaired
                     - Repaired
    Block 3668594772 -                      - Repaired
                     - Repaired
    Block 3668594773 -                      - Repaired
                     - Repaired
    Block 3668594774 -                      - Repaired
                     - Repaired
    Block 3668594775 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668598736
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668598736 - 3668598743 (8 blocks)
Also checking blocks 3668598736 - 3668598743 (8 blocks)
    Block 3668598736 - OK
    Block 3668598737 -                      - Repaired
                     - Repaired
    Block 3668598738 -                      - Repaired
                     - Repaired
    Block 3668598739 -                      - Repaired
                     - Repaired
    Block 3668598740 -                      - Repaired
                     - Repaired
    Block 3668598741 -                      - Repaired
                     - Repaired
    Block 3668598742 -                      - Repaired
                     - Repaired
    Block 3668598743 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668600720
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668600720 - 3668600727 (8 blocks)
Also checking blocks 3668600720 - 3668600727 (8 blocks)
    Block 3668600720 - OK
    Block 3668600721 -                      - Repaired
                     - Repaired
    Block 3668600722 -                      - Repaired
                     - Repaired
    Block 3668600723 -                      - Repaired
                     - Repaired
    Block 3668600724 -                      - Repaired
                     - Repaired
    Block 3668600725 -                      - Repaired
                     - Repaired
    Block 3668600726 -                      - Repaired
                     - Repaired
    Block 3668600727 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668602704
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668602704 - 3668602711 (8 blocks)
Also checking blocks 3668602704 - 3668602711 (8 blocks)
    Block 3668602704 - OK
    Block 3668602705 -                      - Repaired
                     - Repaired
    Block 3668602706 -                      - Repaired
                     - Repaired
    Block 3668602707 -                      - Repaired
                     - Repaired
    Block 3668602708 -                      - Repaired
                     - Repaired
    Block 3668602709 -                      - Repaired
                     - Repaired
    Block 3668602710 -                      - Repaired
                     - Repaired
    Block 3668602711 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668602712
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668602712 - 3668602719 (8 blocks)
Also checking blocks 3668602712 - 3668602719 (8 blocks)
    Block 3668602712 - OK
    Block 3668602713 -                      - Repaired
                     - Repaired
    Block 3668602714 -                      - Repaired
                     - Repaired
    Block 3668602715 -                      - Repaired
                     - Repaired
    Block 3668602716 -                      - Repaired
                     - Repaired
    Block 3668602717 -                      - Repaired
                     - Repaired
    Block 3668602718 -                      - Repaired
                     - Repaired
    Block 3668602719 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668606680
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668606680 - 3668606687 (8 blocks)
Also checking blocks 3668606680 - 3668606687 (8 blocks)
    Block 3668606680 - OK
    Block 3668606681 -                      - Repaired
                     - Repaired
    Block 3668606682 -                      - Repaired
                     - Repaired
    Block 3668606683 -                      - Repaired
                     - Repaired
    Block 3668606684 -                      - Repaired
                     - Repaired
    Block 3668606685 -                      - Repaired
                     - Repaired
    Block 3668606686 -                      - Repaired
                     - Repaired
    Block 3668606687 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668608656
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668608656 - 3668608663 (8 blocks)
Also checking blocks 3668608656 - 3668608663 (8 blocks)
    Block 3668608656 - OK
    Block 3668608657 -                      - Repaired
                     - Repaired
    Block 3668608658 -                      - Repaired
                     - Repaired
    Block 3668608659 -                      - Repaired
                     - Repaired
    Block 3668608660 -                      - Repaired
                     - Repaired
    Block 3668608661 -                      - Repaired
                     - Repaired
    Block 3668608662 -                      - Repaired
                     - Repaired
    Block 3668608663 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668608664
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668608664 - 3668608671 (8 blocks)
Also checking blocks 3668608664 - 3668608671 (8 blocks)
    Block 3668608664 - OK
    Block 3668608665 -                      - Repaired
                     - Repaired
    Block 3668608666 -                      - Repaired
                     - Repaired
    Block 3668608667 -                      - Repaired
                     - Repaired
    Block 3668608668 -                      - Repaired
                     - Repaired
    Block 3668608669 -                      - Repaired
                     - Repaired
    Block 3668608670 -                      - Repaired
                     - Repaired
    Block 3668608671 -                      - Repaired
                     - Repaired
Running select disk self test
Error at LBA 3668765528
Do you wish to attempt repair of the bad block? [Y/N]: This is an advanced-format disk.
This is an advanced-format disk.
Also checking blocks 3668765528 - 3668765535 (8 blocks)
Also checking blocks 3668765528 - 3668765535 (8 blocks)
    Block 3668765528 - OK
    Block 3668765529 -                      - Repaired
                     - Repaired
    Block 3668765530 -                      - Repaired
                     - Repaired
    Block 3668765531 -                      - Repaired
                     - Repaired
    Block 3668765532 -                      - Repaired
                     - Repaired
    Block 3668765533 -                      - Repaired
                     - Repaired
    Block 3668765534 -                      - Repaired
                     - Repaired
    Block 3668765535 -                      - Repaired
                     - Repaired
Running select disk self test
Checking partition tables...
MBR Status: MBR only
GPT Status: not present
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 3668596752
LBA: 3668596752 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666492240
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668596752 maps to file system block 458311530 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458311530 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668512200
LBA: 3668512200 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666407688
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668512200 maps to file system block 458300961 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458300961 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668592776
LBA: 3668592776 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666488264
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668592776 maps to file system block 458311033 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458311033 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668592784
LBA: 3668592784 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666488272
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668592784 maps to file system block 458311034 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458311034 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668594760
LBA: 3668594760 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666490248
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668594760 maps to file system block 458311281 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458311281 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668594768
LBA: 3668594768 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666490256
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668594768 maps to file system block 458311282 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458311282 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668598736
LBA: 3668598736 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666494224
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668598736 maps to file system block 458311778 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458311778 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668600720
LBA: 3668600720 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666496208
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668600720 maps to file system block 458312026 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458312026 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 1786498
The following file contains a corrupt block and can not be fully recovered.
You may wish to delete it or recover from backup.
debugfs 1.42.13 (17-May-2015)
Inode   Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
Dev: /dev/sda LBA: 3668602704
LBA: 3668602704 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666498192
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 3668602704 maps to file system block 458312274 on /dev/sda2
Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 458312274 is marked as in use
Searching for inode...
debugfs 1.42.13 (17-May-2015)
 
rodp said:
I'm asuming that once it finally fishes it will have saved a log somewhere as my telent client keeps bombing out and i have to reconnect?
Click to expand...
/mnt/hd3/fix-disk.0.log viewable in the log file list on the webif diagnostics page

Humax can get very slow if one of the bad sectors is in a file that is frequently accesed or seem unaffected if in a recording not being played,
Fixdisk is best run overnight because of the time it can take.
 
Checking finally done and various points in the log i am not familiar with such as:

Code: 
1, Reconciling multiply-claimed blocks
(There are 7 inodes containing multiply-claimed blocks.)
2, has 7 multiply-claimed block(s), shared with 1 file(s):
3, Pass 5: Checking group summary information
Block bitmap differences:  -16384 -28673 -(19013634--19013744) -(19014184--19014212
4, Free blocks count wrong for group #580 (10, counted=150).
5, The following file contains a corrupt block and can not be fully recovered.
Inode    Pathname
1786498    /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
LBA: 3668608656 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666504144
LBA 3668608656 maps to file system block 458313018 on /dev/sda2
Block 458313018 is marked as in use
Inode: 1786498 (there were 14 reports for the same file)
6,  Inode 74254 was part of the orphaned inode list.
7, Deleted inode 74266 has zero dtime.
8, Inode 75056 was part of the orphaned inode list.
9, Inode 95111 ref count is 2, should be 1.
I assume these are all describing the way ext3 filesystem works but there seemed to be alot of inode related issues.

I read in another thread how skyhawk firmware was meant to be (more) self fixing than other hdd brands / models but the fix-disk process seems to have brought up alot of things it found that needed to be fixed. I had similar issues in my previous (orignal) drive after about 4 years and then there was another 4 years that past before the number of pending and allocated then started to build exponentially.

Summaries are below but i don't understand why bad blocks are zero as it found some and so shouldn't it be reported in the summary?


summry for sda1
Code: 
14 inodes used (0.02%, out of 65808)
           1 non-contiguous file (7.1%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 2/2/0
       17002 blocks used (6.46%, out of 263062)
           0 bad blocks
           1 large file

           2 regular files
           3 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets

Summary for sda2
Code: 
/dev/sda2: ***** FILE SYSTEM WAS MODIFIED *****

       18825 inodes used (0.99%, out of 1896576)
        4046 non-contiguous files (21.5%)
          35 non-contiguous directories (0.2%)
             # of inodes with ind/dind/tind blocks: 6258/3833/19
   369762801 blocks used (76.16%, out of 485492331)
           0 bad blocks
         149 large files

       17515 regular files
         745 directories
           2 character device files
           0 block device files
           0 fifos
           2 links
         554 symbolic links (552 fast symbolic links)
           0 sockets

Summary for sda3

Code: 
18 inodes used (0.00%, out of 655776)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 2/2/0
      374943 blocks used (14.30%, out of 2622611)
           0 bad blocks
           1 large file

           6 regular files
           3 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets

below is the current smart status, uncorrectable and pending are zero now. I assume there is nothing else untoward?

I will do another run overnight. One is never often enough i find!

Thanks

Screenshot_20241110-170229_Chrome.jpg
 
MymsMan said:
Fixdisk is best run overnight because of the time it can take
Click to expand...

Do you always have to enter maintenace mode to run fixdisk to sort problems out?

For the time being I've turned off timeslip / tsr thing as wanted to ensure that area was fully checked too.
 
rodp said:
Do you always have to enter maintenace mode to run fixdisk to sort problems out?
Click to expand...
Yes, to ensure it checks the whole drive without restriction.
rodp said:
For the time being I've turned off timeslip / tsr thing as wanted to ensure that area was fully checked too.
Click to expand...
Not necessary.

It's a good idea to run fixdisk again to confirm there are no more errors after previous run has updated drive (to perform fixes). After the last run (when the log is clear of errors) check SMART attributes again to see if there are significant increases.
 
Last edited:
The messages from fixdisk are mostly e2fsck messages about ext3 filesystem accounting, Like double-entry book-keeping in actual accountancy (so I hear) the ext3fs filesystem keeps duplicate information about the filesystem which can be cross-checked in an audit (but may be inefficient to check in real time).

1, Reconciling multiply-claimed blocks
(There are 7 inodes containing multiply-claimed blocks.)
Click to expand...

Each file or directory in the filesystem has an index listing its blocks. The checker discovered some indexes that refer to the same block. Although this is bad, it can be resolved by replacing all but the first block with copies of the block allocated from the known free blocks ("reconciling"). At least one file of those that shared the block is probably corrupt, but the checker can't tell which.

2, has 7 multiply-claimed block(s), shared with 1 file(s):
Click to expand...

Basically, the same message in reverse, with a bit more detail.

3, Pass 5: Checking group summary information
Block bitmap differences: -16384 -28673 -(19013634--19013744) -(19014184--19014212
Click to expand...

Blocks are allocated to various groups. The filesystem uses bitmaps to record the allocations, but a duplicate copy doesn't match.

4, Free blocks count wrong for group #580 (10, counted=150).
Click to expand...

The checker counted more free blocks than expected, perhaps because some directory entry was lost.

5, The following file contains a corrupt block and can not be fully recovered.
Inode Pathname
1786498 /mnt/hd2/My Video/Crystal Maze/Crystal Maze_20241109_0100.ts
LBA: 3668608656 is on partition /dev/sda2, start: 2104512, bad sector offset: 3666504144
LBA 3668608656 maps to file system block 458313018 on /dev/sda2
Block 458313018 is marked as in use
Inode: 1786498 (there were 14 reports for the same file)
Click to expand...

This is fixdisk cleverness. Using SMART it finds the bad blocks (this can be ridiculously slow if done by trying to read the disk from the OS). Then it can find which, if any file is affected by a bad block. In a media file replacing a bad block with the best copy that can be read, or just a zero block, may just cause a short glitch in playback.

6, Inode 74254 was part of the orphaned inode list.
Click to expand...

A piece of index was not itself indexed elsewhere, perhaps as in (4) above.

7, Deleted inode 74266 has zero dtime.
Click to expand...

An index that was marked as deleted has deleted_time field 0 when it should have been a recent timestamp, perhaps a temporary delete-on-close file where the machine crashed.

8, Inode 75056 was part of the orphaned inode list.
Click to expand...

As (6).

9, Inode 95111 ref count is 2, should be 1.
Click to expand...

This index may have been linked by two different directory entries (eg, hard-linked) but one has been lost.
 
Last edited:
You must log in or register to reply here.
Back
Top