• The forum software that supports hummy.tv will be upgraded to XenForo 2.3 on Wednesday the 20th of November 2024 starting at 7pm

    There will be some periods where the forum is unavailable, please bear with us. More details can be found in the upgrade thread.

Storage must be formatted error - fix-disk advice needed please

3

3rddawn

New Member
Hi
HDR-FOX-T2, turned on and after a long time got this message "Storage must be formatted ..."
Read on the forums and realise some hard disk maintenance may be in order.
Have got as far as running fix-disk (no additional options) and get this:-
Code: 
Running /bin/fix-disk
Custom firmware version 3.03

Checking disk sda

Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted

Running short disk self test
Error at LBA 1932539176
Do you wish to attempt repair of the bad block? [Y/N]:

If I press Y, it does the waiting countdown for a few seconds then the same message for the same block number.
It only goes on if I say N
Then I get this
Skipped repair of LBA 1932539176
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 32768 on sda3

Checking partition /dev/sda3...
e2fsck 1.42.10 (18-May-2014)
/usr/lib/ext2/bin/e2fsck: Attempt to read block from filesystem resulted in shor
t read while trying to open /dev/sda3
Could this be a zero-length partition?

Checking partition /dev/sda1...
e2fsck 1.42.10 (18-May-2014)
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
☻☺/dev/sda1: |========================================================| 100.0%
☻☺
☻/dev/sda1: 15/65808 files (6.7% non-contiguous), 15044/263064 blocks
mount: mounting /dev/sda3 on /mnt/hd3 failed: Invalid argument

Press return to continue:

Do any of the fix-disk experts know what I should be doing?

Thanks in anticipation
3rddawn
 
Last edited:
Hey, at least you included your current firmware version in the post! : )

I don't think fix-disk will be able to repair this one by itself but let's see how it goes.
 
Thanks for the advice. Upgraded and we did indeed get further.
Code: 
Running /bin/fix-disk
Custom firmware version 3.10


Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Partition /dev/sda3 is already unmounted


Running short disk self test
Error at LBA 1932539176
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 1932539176: succeeded
This is an advanced-format disk.
Also checking blocks 1932539176 - 1932539183 (8 blocks)
    Block 1932539176 - OK
    Block 1932539177 - FAILED: Input/output error
                     - Repaired
    Block 1932539178 - FAILED: Input/output error
                     - Repaired
    Block 1932539179 - FAILED: Input/output error
                     - Repaired
    Block 1932539180 - FAILED: Input/output error
                     - Repaired
    Block 1932539181 - FAILED: Input/output error
                     - Repaired
    Block 1932539182 - FAILED: Input/output error
                     - Repaired
    Block 1932539183 - FAILED: Input/output error
                     - Repaired

Running short disk self test

Pending sector error(s) found

LBA has not yet been found
A long test is required - this could take 2 hour(s) 19 minutes
Do you wish to continue? [Y/N]: y
Running long disk self test

Assume I did the correct thing in letting it do a long test? If there are other things to check/deal with before doing that, please tell me and I'll cancel it (if that's possible).
 
Well it ran and ran and finished with some fixing going on and now it all seems to be working fine - all files and folders seem intact.
Is there anything else I should run as a precaution, or do you want to see the telnet details to see if there are any other issues I should do anything about?

This morning I also got this in an email.
Overall Health: PASSED
Reallocated sectors: 8 (was 8)
Pending sectors: 13 (was 5)
Offline sectors: 13 (was 5)
 
Last edited:
That's good news. It's worth checking the state of your disk to see whether you should be planning to replace it. Post the details from the Diagnostics->Hard Disk page in the web interface and the telnet output (or fix-disk.log file) would be useful too.
 
Telnet output from the fixdisk process:
Code: 
Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Partition /dev/sda3 is already unmounted


Running short disk self test
Error at LBA 1932539176
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 1932539176: succeeded
This is an advanced-format disk.
Also checking blocks 1932539176 - 1932539183 (8 blocks)
    Block 1932539176 - OK
    Block 1932539177 - FAILED: Input/output error
                     - Repaired
    Block 1932539178 - FAILED: Input/output error
                     - Repaired
    Block 1932539179 - FAILED: Input/output error
                     - Repaired
    Block 1932539180 - FAILED: Input/output error
                     - Repaired
    Block 1932539181 - FAILED: Input/output error
                     - Repaired
    Block 1932539182 - FAILED: Input/output error
                     - Repaired
    Block 1932539183 - FAILED: Input/output error
                     - Repaired

Running short disk self test

Pending sector error(s) found

LBA has not yet been found
A long test is required - this could take 2 hour(s) 19 minutes
Do you wish to continue? [Y/N]: y
Running long disk self test
Error at LBA 577252608
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 577252608: succeeded
This is an advanced-format disk.
Also checking blocks 577252608 - 577252615 (8 blocks)
    Block 577252608  - OK
    Block 577252609  - OK
    Block 577252610  - OK
    Block 577252611  - FAILED: Input/output error
                     - Repaired
    Block 577252612  - FAILED: Input/output error
                     - Repaired
    Block 577252613  - FAILED: Input/output error
                     - Repaired
    Block 577252614  - FAILED: Input/output error
                     - Repaired
    Block 577252615  - FAILED: Input/output error
                     - 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 32768 on sda3
Dev: /dev/sda LBA: 1932539176
LBA: 1932539176 is on partition /dev/sda3, start: 1932539175, bad sector offset:
1
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 32768
Block size: 4096
LBA 1932539176 maps to file system block 0 on /dev/sda3

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
testb: Invalid block number 0
Block 0 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
Block Inode number 0 <block not found>
Dev: /dev/sda LBA: 577252608
LBA: 577252608 is on partition /dev/sda2, start: 2104515, bad sector offset: 575
148093
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 0
Block size: 4096
LBA 577252608 maps to file system block 71893511 on /dev/sda2

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 71893511 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
Inode: 5964313

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
5964313 /mnt/hd2/My Video/L/The Big Bang Theory/Season 5/The Big Bang Theory_201
51010_1331.thm


Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
/usr/lib/ext2/bin/e2fsck: Superblock invalid, trying backup blocks...
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
/dev/sda3: recovering journal
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
☻☺
☻Free blocks count wrong for group #0 (31616, counted=27520).
Fix? yes

Free blocks count wrong for group #1 (9150, counted=1).
Fix? yes

Free blocks count wrong for group #2 (21926, counted=0).
Fix? yes

Free blocks count wrong for group #3 (31618, counted=2).
Fix? yes

Free blocks count wrong for group #4 (32260, counted=4).
Fix? yes

Free blocks count wrong for group #5 (31618, counted=2).
Fix? yes

Free blocks count wrong for group #6 (32260, counted=4).
Fix? yes

Free blocks count wrong for group #7 (31618, counted=6).
Fix? yes

Free blocks count wrong for group #8 (32260, counted=31223).
Fix? yes

Free blocks count wrong (2542881, counted=2347317).
Fix? yes

☻☺/dev/sda3: |========================================================| 100.0%
☻☺
☻Free inodes count wrong for group #0 (8086, counted=8083).
Fix? yes

Directories count wrong for group #0 (1, counted=2).
Fix? yes

Free inodes count wrong for group #3 (8096, counted=8093).
Fix? yes

Free inodes count wrong (655766, counted=655760).
Fix? yes


/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 16/655776 files (6.3% non-contiguous), 275294/2622611 blocks

Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
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
☻☺/dev/sda1: |========================================================| 100.0%
☻☺
☻/dev/sda1: 15/65808 files (0.0% non-contiguous), 13929/263064 blocks

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=0b6ac367-3daf-4525-8836-92eb6a6bec8a

Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
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
☻☺/dev/sda2: |========================================================| 100.0%
☻☺
☻/dev/sda2: 7492/60334080 files (11.4% non-contiguous), 184713835/241304332 bloc
ks
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: n
Skipped

Finished

Diagnostics Disk info:
In attached images
 

Attachments

  • Hm1.PNG
    Hm1.PNG
    53.3 KB · Views: 14
  • Hm2.PNG
    Hm2.PNG
    56.2 KB · Views: 16
  • Hm3.PNG
    Hm3.PNG
    63.6 KB · Views: 15
That all looks fine to me. Your main problem (and what made the Humax report that it needed formatting) was a lost superblock on the third partition which fix-disk has successfully repaired thanks to xyz321 foreseeing this kind of problem and adding logic to deal with it. That partition doesn't contain any recordings so no harm done there. Separate to that, the only corrupt file is a .thm one which is just a thumbnail shown alongside a recording. You could delete the file if you wanted.

Your disk now has 16 reallocated sectors. That isn't a problem but do keep an eye on it in case the number starts to rapidly increase. If you're subscribed to the RS service (which it looks like you are based on the fact that you got a disk alert email) then you will be told if this happens; the on-box web interface will also notify you when you access it.
 
And it all seems to be behaving again :)
Thank you af123 for your generous support.
And I also want to thank xyz321 and everyone else who has contributed to providing and continually improving the custom firmware experience for us Hummy users. You are all amazing to give so much of your time and knowledge to others.
Cheers!:cheers:
 
Spoke too soon ...
Watched some of a recording tonight and it went blank in the middle of playing, then no response to any buttons ... pause, stop etc. Had to turn off with the switch at the back, trying to run fixdisk again ...
 
Last edited:
Fixdisk is getting as far as 29 on the Waiting count and then repeatedly cycling with this ...

Code: 
/dev/sda:
re-writing sector 0: succeeded
This is an advanced-format disk.
Also checking blocks 0 - 7 (8 blocks)
    Block 0          - OK
    Block 1          - OK
    Block 2          - OK
    Block 3          - OK
    Block 4          - OK
    Block 5          - OK
    Block 6          - OK
    Block 7          - OK

Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]:

If I say Y it just goes round the loop again and again.
So I said N and it continued. Here's the full log

Code: 
Running /bin/fix-disk
Custom firmware version 3.10


Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Unmounted /dev/sda3


Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 0: succeeded
This is an advanced-format disk.
Also checking blocks 0 - 7 (8 blocks)
    Block 0          - OK
    Block 1          - OK
    Block 2          - OK
    Block 3          - OK
    Block 4          - OK
    Block 5          - OK
    Block 6          - OK
    Block 7          - OK

Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 0: succeeded
This is an advanced-format disk.
Also checking blocks 0 - 7 (8 blocks)
    Block 0          - OK
    Block 1          - OK
    Block 2          - OK
    Block 3          - OK
    Block 4          - OK
    Block 5          - OK
    Block 6          - OK
    Block 7          - OK

Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]: n
Skipped repair of LBA 0

Checking partition tables...

MBR Status: not present
GPT Status: not present

Partition table is missing/corrupt. If the disk has not been formatted by
the Humax, recovery by fix-disk may not be successful.

Searching for partitions...

Partition 1 starts @ 2, ends @ 2104514
Partition 2 starts @ 2104515, ends @ 1932539174
Partition 3 starts @ 1932539175, ends @ 1953520064
Do you wish to attempt repair of the partition table? [Y/N]: y

/dev/sda:
re-reading partition table
New partition table has been created
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0xbe420847

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1                2    2104513    2104512     1G 83 Linux
/dev/sda2          2104515 1932539173 1930434659 920.5G 83 Linux
/dev/sda3       1932539175 1953520063   20980889    10G 83 Linux
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 0 on sda3
Dev: /dev/sda LBA: 0
Dev: /dev/sda LBA: 0


Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
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
☻☺/dev/sda3: |========================================================| 100.0%
☻☺
☻Error writing file system info: Attempt to write block to filesystem resulted i
n short write

/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****

Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Resize inode not valid.  Recreate? yes

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
Free blocks count wrong for group #0 (23216, counted=23217).
Fix? yes

Free blocks count wrong (248825, counted=248826).
Fix? yes

☻☺/dev/sda1: |========================================================| 100.0%
☻☺
☻
/dev/sda1: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda1: 15/65808 files (0.0% non-contiguous), 14238/263064 blocks
mount: mounting /dev/sda3 on /mnt/hd3 failed: Invalid argument

Press return to continue:

I have restarted and will see what happens ...
 
Last edited:
3rddawn said:
Should I say N and see what else is revealed?
Click to expand...
There's no point endlessly cycling, so you might as well.

I didn't like the look of attributes 187 and 189 from your SMART data.
I think I'd be thinking of a replacement.
 
Thanks, I did, results are in the previous post ... I did it and edited the same post cos wasn't sure if anyone was round tonight.:(
Not looking so healthy ... attached attributes. Should I attempt fixdisk again?
 

Attachments

  • Hm2 2.PNG
    Hm2 2.PNG
    56.5 KB · Views: 7
Ran fixdisk again and got this ...
Code: 
Running /bin/fix-disk
Custom firmware version 3.10


Checking disk sda (4096 byte sectors)

Unmounted /dev/sda1
Unmounted /dev/sda2
Partition /dev/sda3 is already unmounted


Running short disk self test
Error at LBA 1932539176
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 1932539176: succeeded
This is an advanced-format disk.
Also checking blocks 1932539176 - 1932539183 (8 blocks)
    Block 1932539176 - OK
    Block 1932539177 - FAILED: Input/output error
                     - Repaired
    Block 1932539178 - FAILED: Input/output error
                     - Repaired
    Block 1932539179 - FAILED: Input/output error
                     - Repaired
    Block 1932539180 - FAILED: Input/output error
                     - Repaired
    Block 1932539181 - FAILED: Input/output error
                     - Repaired
    Block 1932539182 - FAILED: Input/output error
                     - Repaired
    Block 1932539183 - FAILED: Input/output error
                     - Repaired

Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]: n
Skipped repair of LBA 0

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 32768 on sda3
Dev: /dev/sda LBA: 1932539176
LBA: 1932539176 is on partition /dev/sda3, start: 1932539175, bad sector offset:
1
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 32768
Block size: 4096
LBA 1932539176 maps to file system block 0 on /dev/sda3

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
testb: Invalid block number 0
Block 0 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
icheck: Attempt to read block from filesystem resulted in short read while calli
ng ext2fs_block_iterate
Block Inode number 0 <block not found>


Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
/usr/lib/ext2/bin/e2fsck: Attempt to read block from filesystem resulted in shor
t read while trying to open /dev/sda3
Could this be a zero-length partition?

Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
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
☻☺/dev/sda1: |========================================================| 100.0%
☻☺
☻/dev/sda1: 15/65808 files (0.0% non-contiguous), 15275/263064 blocks
mount: mounting /dev/sda3 on /mnt/hd3 failed: Invalid argument

Press return to continue:

Not sure what it means ...
 
P.S. New HDD now ordered :confused: but in the meantime would appreciate help trying to keep this one afloat until I'm able to do a swap and copy job :thumbsup:
 
Well here is the latest full fixdisk log ...

Code: 
Please select option: fixdisk
Any additional options (or press return for none):
Are you sure you wish to run the hard disk checker? [Y/N] y
Running /bin/fix-disk
Custom firmware version 3.10


Checking disk sda (4096 byte sectors)

Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
Partition /dev/sda3 is already unmounted


Running short disk self test
Error at LBA 1932539184
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 1932539184: succeeded
This is an advanced-format disk.
Also checking blocks 1932539184 - 1932539191 (8 blocks)
    Block 1932539184 - OK
    Block 1932539185 - FAILED: Input/output error
                     - Repaired
    Block 1932539186 - FAILED: Input/output error
                     - Repaired
    Block 1932539187 - FAILED: Input/output error
                     - Repaired
    Block 1932539188 - FAILED: Input/output error
                     - Repaired
    Block 1932539189 - FAILED: Input/output error
                     - Repaired
    Block 1932539190 - FAILED: Input/output error
                     - Repaired
    Block 1932539191 - FAILED: Input/output error
                     - Repaired

Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]: y

/dev/sda:
re-writing sector 0: succeeded
This is an advanced-format disk.
Also checking blocks 0 - 7 (8 blocks)
    Block 0          - OK
    Block 1          - OK
    Block 2          - OK
    Block 3          - OK
    Block 4          - OK
    Block 5          - OK
    Block 6          - OK
    Block 7          - OK

Running short disk self test
Error at LBA 0
Do you wish to attempt repair of the bad block? [Y/N]: n
Skipped repair of LBA 0

Checking partition tables...

MBR Status: not present
GPT Status: not present

Partition table is missing/corrupt. If the disk has not been formatted by
the Humax, recovery by fix-disk may not be successful.

Searching for partitions...

Partition 1 starts @ 2, ends @ 2104514
Partition 2 starts @ 2104515, ends @ 1932539174
Partition 3 starts @ 1932539175, ends @ 1953520064
Do you wish to attempt repair of the partition table? [Y/N]: y

/dev/sda:
re-reading partition table
New partition table has been created
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5b236da6

Device     Boot      Start        End    Sectors   Size Id Type
/dev/sda1                2    2104513    2104512     1G 83 Linux
/dev/sda2          2104515 1932539173 1930434659 920.5G 83 Linux
/dev/sda3       1932539175 1953520063   20980889    10G 83 Linux
Using superblock 0 on sda1
Using superblock 0 on sda2
Using superblock 32768 on sda3
Dev: /dev/sda LBA: 1932539184
LBA: 1932539184 is on partition /dev/sda3, start: 1932539175, bad sector offset:
9
dumpe2fs 1.42.13 (17-May-2015)
Using superblock 32768
Block size: 4096
LBA 1932539184 maps to file system block 1 on /dev/sda3

Checking to see if this block is in use...
debugfs 1.42.13 (17-May-2015)
Block 1 is marked as in use

Searching for inode...
debugfs 1.42.13 (17-May-2015)
Block Inode number 1 <block not found>
Dev: /dev/sda LBA: 0


Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
ext2fs_open2: Bad magic number in super-block
/usr/lib/ext2/bin/e2fsck: Superblock invalid, trying backup blocks...
Resize inode not valid.  Recreate? yes

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
☻☺
☻Free blocks count wrong for group #0 (31615, counted=27480).
Fix? yes

Free blocks count wrong for group #1 (9150, counted=1).
Fix? yes

Free blocks count wrong for group #2 (21926, counted=0).
Fix? yes

Free blocks count wrong for group #3 (31618, counted=2).
Fix? yes

Free blocks count wrong for group #4 (32260, counted=4).
Fix? yes

Free blocks count wrong for group #5 (31618, counted=2).
Fix? yes

Free blocks count wrong for group #6 (32260, counted=4).
Fix? yes

Free blocks count wrong for group #7 (31618, counted=7).
Fix? yes

Free blocks count wrong for group #8 (32260, counted=31223).
Fix? yes

Free blocks count wrong (2542880, counted=2347278).
Fix? yes

☻☺/dev/sda3: |========================================================| 100.0%
☻☺
☻Free inodes count wrong for group #0 (8086, counted=8080).
Fix? yes

Directories count wrong for group #0 (1, counted=2).
Fix? yes

Free inodes count wrong for group #3 (8096, counted=8094).
Fix? yes

Free inodes count wrong (655766, counted=655758).
Fix? yes


/dev/sda3: ***** FILE SYSTEM WAS MODIFIED *****
/dev/sda3: 18/655776 files (5.6% non-contiguous), 275333/2622611 blocks

Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
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
☻☺/dev/sda1: |========================================================| 100.0%
☻☺
☻/dev/sda1: 15/65808 files (0.0% non-contiguous), 15275/263064 blocks

Creating swap file...
Setting up swapspace version 1, size = 1073737728 bytes
UUID=53b51c30-c460-4bab-8047-e80c92ea28d4

Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
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
☻☺/dev/sda2: |========================================================| 100.0%
☻☺
☻/dev/sda2: 7105/60334080 files (9.6% non-contiguous), 161348465/241304332 block
s
Removing extra swap space.
Are you having problems with a delete loop? [Y/N]: n
Skipped

Finished

Now the disk warning on reboot says
Disk realloc sector count is: 40 (was 16)
Disk pending sector count is: 24
Disk offline sector count is: 24

There are still 2 red rows in the Attributes table (attached). Please can someone explain what that means and whether I should not use the Hummy?
 

Attachments

  • Hm2 3.PNG
    Hm2 3.PNG
    57.5 KB · Views: 8
It means new problems are currently surfacing (!) as quickly as old ones are being fixed. 187 and 189 continue to rise as well.
It might be better not to be writing to the disk until you have managed to backup whatever you want to keep from it.
 
You must log in or register to reply here.
Back
Top