• 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.

Fixdisk repeatedly unable to find partition 1

prpr said:
I would cancel it. It's only in read-only mode, and you haven't set up your swap file yet, so it'll probably fail at some point down the line anyway. And it can take several hours, so don't let that put you off.
Click to expand...
It has actually just finished (or, at least, it has ended without me canceling it). Here's the output:

Code: 
humax# e2fsck -n /dev/sda2
e2fsck 1.42.13 (17-May-2015)
Warning: skipping journal recovery because doing a read-only filesystem check.
The filesystem size (according to the superblock) is 485492325 blocks
The physical size of the device is 485492324 blocks
Either the superblock or the partition table is likely to be corrupt!
Abort? no

/dev/sda2 contains a file system with errors, check forced.
Pass 1: Checking inodes, blocks, and sizes
^[[15~Pass 2: Checking directory structure
Entry 'Maps_ Power, Plunder and Possession_20151110_2246.hmt' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235553.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.hmt' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.ts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235554.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.ts' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.nts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235555.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.nts' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.thm' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235556.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.thm' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.hmt' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235557.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.hmt' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.ts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235558.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.ts' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.nts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235559.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.nts' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.thm' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235560.  Clear? no

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.thm' in /My Video/Maps_ Power, Plunder and Possession (21505) has an incorrect filetype (was 1, should be 0).
Fix? no

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(241215488--241216978) -(241217536--241217541) -(241219584--241221048) -(241225728--241225749) -(241229824--241238015) -(241238024--241270783) -(241270792--241303551) -(241303560--241336319) -(241336328--241369087) -(241369096--241401855) -(241401864--241434623) -(241434632--241467391) -(241467400--241500159) -(241500168--241532927) -(241532936--241565695) -(241565704--241598463) -(241598472--241631231) -(241631240--241663999) -(241664008--241696767) -(241696776--241729535) -(241729544--241762303) -(241762312--241795071) -(241795080--241827839) -(241827848--241860607) -(241860612--241893375) -(241893384--241926143) -(241926152--241958911) -(241958920--241991679) -(241991688--242024447) -(242024456--242057215) -(242057224--242089983) -(242089992--242122751) -(242122760--242155519) -(242155528--242188287) -(242188296--242221055) -(242221064--242253823) -(242253832--242286591) -(242286600--242319359) -(242319368--242352127) -(242352136--242384895) -(242384904--242417663) -(242417672--242450431) -(242450440--242478746)
Fix? no

Inode bitmap differences:  -(235553--235560)
Fix? no


/dev/sda2: ********** WARNING: Filesystem still has errors **********

/dev/sda2: 3150/474144 files (30.3% non-contiguous), 449373316/485492325 blocks
humax#

It doesn't seem like a roaring success - which I suppose is expected given I still need to adjust the partition table again - but I'm somewhat heartened to see actual filenames of recordings I recognise in there, even if they are errors.
 
prpr said:
But, if the partition table is now correct, then you could just run fix-disk again and it should do it all for you, but make sure you use the option to omit the SMART checks
Click to expand...
Just to clarify, should I still mount P3 and do the swapon command after updating the partition table? Or just run fix-disk (without SMART) straight after updating the table?
 
thoughton said:
It doesn't seem like a roaring success
Click to expand...
I think it's pretty good. Whether it's affected the recording or not remains to be seen, but I guess it will only cause a small glitch if it does. And remember that you really did have several bad sectors.
thoughton said:
Just to clarify, should I still mount P3 and do the swapon command after updating the partition table?
Click to expand...
Yes. It won't hurt anything if the swap isn't needed. You need to fix P2 and P1 still.
 
I've updated the partition table so it now looks like this:

Code: 
Command (m for help): p

Disk /dev/sda: 2000 GB, 2000396321280 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907024065 sectors
Units = sectors of 1 * 512 = 512 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1              56     2104575     1060258   83  Linux
Warning: Partition 1 does not end on cylinder boundary.
/dev/sda2         2104576  3886043175  1941969330   83  Linux
Warning: Partition 2 does not end on cylinder boundary.
/dev/sda3      3886043176  3907024070    10490445   83  Linux
Warning: Partition 3 does not end on cylinder boundary.

I "rebooted" by exiting Maintenance mode and entering it again. (Is there a better command-line way of rebooting in these situations?)

I re-ran the sda3 checks which looked clean, and then mounted it successfully, but there does not seem to be a .swap file present:

Code: 
humax# e2fsck -n /dev/sda3
e2fsck 1.42.13 (17-May-2015)
/dev/sda3: clean, 13/655776 files, 933209/2622611 blocks
humax#
humax# e2fsck /dev/sda3
e2fsck 1.42.13 (17-May-2015)
/dev/sda3: clean, 13/655776 files, 933209/2622611 blocks
humax#
humax# mount /dev/sda3 /mnt/hd3
humax#
humax# ls -l /mnt/hd3/.swap
ls: /mnt/hd3/.swap: No such file or directory
humax#
humax# ls -l /mnt/hd3/
-rw-r--r--    1 root     root     3492414161 Nov  9  2016 Streamer_down_file
-rw-r--r--    1 root     root           634 Feb 25  2014 cookie.txt
drwx------    2 root     root         16384 Jan  1  2000 lost+found

Do I need to somehow manually create the swap file before continuing?
 
You need ls -la to show hidden files (those starting with a dot).

But as you've already proved it doesn't exist, then do this:
Code: 
dd if=/dev/zero of=/mnt/hd3/.swap bs=1M count=128
mkswap /mnt/hd3/.swap
swapon /mnt/hd3/.swap

This creates the 'standard' 128MB swap file, not a 1MB one!
Fix-disk seems to use a 1024MB file.
 
prpr said:
You need ls -la to show hidden files (those starting with a dot).
Click to expand...

Whoops, good point!

Creating the swap seems to have been successful:

Code: 
humax# dd if=/dev/zero of=/mnt/hd3/.swap bs=1M count=128
128+0 records in
128+0 records out
134217728 bytes (128.0MB) copied, 2.337000 seconds, 54.8MB/s
humax#
humax# mkswap /mnt/hd3/.swap
Setting up swapspace version 1, size = 134213632 bytes
UUID=061a553e-d4dc-497f-96ca-804d6e73688a
humax#
humax# swapon /mnt/hd3/.swap
humax#
humax# ls -la /mnt/hd3/.swap
-rw-------    1 root     root     134217728 Nov 21 14:18 /mnt/hd3/.swap
humax#
 
Ah, just attempted a fixdisk and immediately encountered this:

Code: 
Please select option: fixdisk
Any additional options (-h for list or press return for none): -d -P -y
Are you sure you wish to run the hard disk checker (-d -P -y)? [Y/N] y
Running /bin/fix-disk
PART: [3 1 2]
FSCKOPTS: []

Checking disk sda (4096 byte sectors)

Partition /dev/sda1 is already unmounted
Partition /dev/sda2 is already unmounted
umount: can't umount /mnt/hd3: Device or resource busy
fix-disk: session terminated with exit status 1

Press return to continue:

Presumably this is due to having mounted sda3 and turning the swap on? Is it just the case that I need to unmount sda3 before the fixdisk?
 
thoughton said:
Presumably this is due to having mounted sda3 and turning the swap on? Is it just the case that I need to unmount sda3 before the fixdisk?
Click to expand...
Yes to both (and obviously you need to turn swap off again before unmounting).
If you're running fixdisk then there's no need to do all this stuff manually, unless you want to learn and/or don't trust fixdisk and/or need to do things step by step just in case.
 
Ok I re-ran fixdisk again after rebooting, and it wasn't particularly successful...

Code: 
Please select option: fixdisk
Any additional options (-h for list or press return for none): -d -P -y
Are you sure you wish to run the hard disk checker (-d -P -y)? [Y/N] y
Running /bin/fix-disk
PART: [3 1 2]
FSCKOPTS: []

Checking disk sda (4096 byte sectors)

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

Skipped pending sector error tests

Checking partition tables...

MBR Status: MBR only
GPT Status: not present

Partition sda1 - Unrecognised partition type, aborting...
fix-disk: session terminated with exit status 1

Press return to continue:
 
I would just format P1 and be done with it: mkfs.ext3 -m 0 -O sparse_super /dev/sda1

You're certainly exposing all the deficiencies in fix-disk here!
 
prpr said:
I would just format P1 and be done with it: mkfs.ext3 -m 0 -O sparse_super /dev/sda1
Click to expand...

Formatting P1 seems to have gone without issue.

Code: 
humax# mkfs.ext3 -m 0 -O sparse_super /dev/sda1
mke2fs 1.42.13 (17-May-2015)
Creating filesystem with 263065 4k blocks and 65808 inodes
Filesystem UUID: 678912f7-5c03-4270-b955-e2b2d9d75cee
Superblock backups stored on blocks:
        32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done

humax#

Should I try running fix-disk again next?
 
Yep, just P2 to check/fix and you should hopefully be back in business.

I was expecting 263064 blocks on P1, but reading back I see you left the start as 56 not 64, so that's right. It makes no practical difference.
 
prpr said:
I was expecting 263064 blocks on P1, but reading back I see you left the start as 56 not 64, so that's right. It makes no practical difference.
Click to expand...

Oh whoops, sorry! Could that be why my previous fix-disk failed...?

Looks like my fix-disk after formatting P1 was potentially more successful though:

Code: 
Please select option: fixdisk
Any additional options (-h for list or press return for none): -d -P -y
Are you sure you wish to run the hard disk checker (-d -P -y)? [Y/N] y
Running /bin/fix-disk
PART: [3 1 2]
FSCKOPTS: []

Checking disk sda (4096 byte sectors)

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

Skipped pending sector error tests

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


Mon Nov 22 20:13:25 GMT 2021: Checking partition /dev/sda3...
e2fsck 1.42.13 (17-May-2015)
/dev/sda3: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 240k/0k (157k/84k), time: 20.25/ 8.55/ 4.46
Pass 1: I/O read: 167MB, write: 0MB, rate: 8.25MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 340k/0k (259k/82k), time:  0.01/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 112.79MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time: 21.25/ 9.12/ 4.55
Pass 3A: Memory used: 340k/0k (259k/82k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 340k/0k (259k/82k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 340k/0k (53k/288k), time:  1.18/ 1.18/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Free blocks count wrong (1689402, counted=1656601).
Fix? yes

Free inodes count wrong (655763, counted=655762).
Fix? yes

Pass 5: Memory used: 340k/0k (53k/288k), time:  3.01/ 2.36/ 0.04
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.33MB/s

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

          14 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
      966010 blocks used (36.83%, out of 2622611)
           0 bad blocks
           2 large files

           3 regular files
           2 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           5 files
Memory used: 340k/0k (53k/288k), time: 25.47/12.66/ 4.59
I/O read: 168MB, write: 1MB, rate: 6.60MB/s
Mon Nov 22 20:13:51 GMT 2021

Mon Nov 22 20:13:51 GMT 2021: Checking partition /dev/sda1...
e2fsck 1.42.13 (17-May-2015)
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 140k/0k (61k/80k), time:  0.53/ 0.18/ 0.13
Pass 1: I/O read: 17MB, write: 0MB, rate: 31.97MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (71k/70k), time:  0.00/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 1019.37MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (71k/70k), time:  0.68/ 0.22/ 0.14
Pass 3A: Memory used: 140k/0k (71k/70k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 140k/0k (71k/70k), time:  0.00/ 0.00/ 0.00
Pass 3: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 140k/0k (50k/91k), time:  0.09/ 0.09/ 0.00
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: Memory used: 140k/0k (50k/91k), time:  0.29/ 0.23/ 0.00
Pass 5: I/O read: 1MB, write: 0MB, rate: 3.41MB/s

          11 inodes used (0.02%, out of 65808)
           0 non-contiguous files (0.0%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 0/0/0
       12668 blocks used (4.82%, out of 263065)
           0 bad blocks
           1 large file

           0 regular files
           2 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           0 symbolic links (0 fast symbolic links)
           0 sockets
------------
           2 files
Memory used: 140k/0k (50k/91k), time:  1.08/ 0.55/ 0.14
I/O read: 17MB, write: 1MB, rate: 15.68MB/s
Mon Nov 22 20:13:52 GMT 2021

Mon Nov 22 20:13:53 GMT 2021: Checking partition /dev/sda2...
e2fsck 1.42.13 (17-May-2015)
/dev/sda2: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 1: Memory used: 1536k/468k (959k/578k), time: 7726.83/4861.99/59.52
Pass 1: I/O read: 1836MB, write: 0MB, rate: 0.24MB/s
Pass 2: Checking directory structure
Entry 'Maps_ Power, Plunder and Possession_20151110_2246.hmt' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235553.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.ts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235554.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.nts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235555.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151110_2246.thm' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235556.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.hmt' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235557.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.ts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235558.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.nts' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235559.  Clear? yes

Entry 'Maps_ Power, Plunder and Possession_20151117_2301.thm' in /My Video/Maps_ Power, Plunder and Possession (21505) has deleted/unused inode 235560.  Clear? yes

Pass 2: Memory used: 1536k/468k (1030k/507k), time:  0.99/ 0.25/ 0.04
Pass 2: I/O read: 1MB, write: 1MB, rate: 1.01MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 1536k/468k (1030k/507k), time: 7733.22/4866.39/59.63
Pass 3A: Memory used: 1536k/468k (1033k/504k), time:  0.00/ 0.00/ 0.00
Pass 3A: I/O read: 0MB, write: 0MB, rate: nanMB/s
Pass 3: Memory used: 1536k/468k (1028k/509k), time:  0.03/ 0.03/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 36.29MB/s
Pass 4: Checking reference counts
Pass 4: Memory used: 1536k/468k (864k/673k), time:  1.35/ 1.27/ 0.07
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Block bitmap differences:  -(241215488--241216978) -(241217536--241217541) -(241219584--241221048) -(241225728--241225749) -(241229824--241238015) -(241238024--241270783) -(241270792--241303551) -(241303560--241336319) -(241336328--241369087) -(241369096--241401855) -(241401864--241434623) -(241434632--241467391) -(241467400--241500159) -(241500168--241532927) -(241532936--241565695) -(241565704--241598463) -(241598472--241631231) -(241631240--241663999) -(241664008--241696767) -(241696776--241729535) -(241729544--241762303) -(241762312--241795071) -(241795080--241827839) -(241827848--241860607) -(241860612--241893375) -(241893384--241926143) -(241926152--241958911) -(241958920--241991679) -(241991688--242024447) -(242024456--242057215) -(242057224--242089983) -(242089992--242122751) -(242122760--242155519) -(242155528--242188287) -(242188296--242221055) -(242221064--242253823) -(242253832--242286591) -(242286600--242319359) -(242319368--242352127) -(242352136--242384895) -(242384904--242417663) -(242417672--242450431) -(242450440--242478746)
Fix? yes

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Free blocks count wrong (36119009, counted=37370616).
Fix? yes

Inode bitmap differences:  -(235553--235560)
Fix? yes

Free inodes count wrong for group #7361 (24, counted=32).
Fix? yes

Free inodes count wrong (470994, counted=471002).
Fix? yes

Pass 5: Memory used: 1652k/468k (861k/792k), time: 155.40/30.89/ 4.34
Pass 5: I/O read: 116MB, write: 0MB, rate: 0.75MB/s

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

        3142 inodes used (0.66%, out of 474144)
         952 non-contiguous files (30.3%)
           1 non-contiguous directory (0.0%)
             # of inodes with ind/dind/tind blocks: 1495/1361/71
   448121709 blocks used (92.30%, out of 485492325)
           0 bad blocks
         398 large files

        3053 regular files
          79 directories
           0 character device files
           0 block device files
           0 fifos
           0 links
           1 symbolic link (1 fast symbolic link)
           0 sockets
------------
        3133 files
Memory used: 1652k/468k (861k/792k), time: 7954.85/4899.47/65.38
I/O read: 1954MB, write: 117MB, rate: 0.26MB/s
Mon Nov 22 22:26:28 GMT 2021
Removing extra swap space.

Finished
fix-disk: session terminated with exit status 0

Press return to continue:
 
Holy moly, it looks like it's worked! No more error message on startup, I can pause/rewind again, and my recordings are all present!

/df said:
Now you just need to try playing the two suspect recordings!
Click to expand...

I couldn't find these two recordings listed in the Media anymore, but honestly it's not a problem; that's a small price to pay. The random selection of other recordings I've tried so far all worked great.

Thank you so much to all who helped! It's been quite the learning experience. Donation made - thanks again!
 
thoughton said:
Oh whoops, sorry! Could that be why my previous fix-disk failed...?
Click to expand...
No, it was because the filesystem seemed quite corrupted.
Looks like my fix-disk after formatting P1 was potentially more successful though
Click to expand...
Indeed. I'm slightly concerned how P3 has all those errors again, seeing as it was clean a couple of days ago.
Keep an eye on those SMART stats. - as I said before, I'm not totally happy with that disk.
thoughton said:
Thank you so much to all who helped! It's been quite the learning experience.
Click to expand...
I hope you've learnt something useful. I've certainly learnt a couple of things.

I think I worked out where you got the numbers from for partitioning the disk too - the 2TB disk installation blog - which I guess you must have done originally, rather than letting the Humax do it. It would have saved lots of time if you'd mentioned this, but we might not have learnt as much!
 
prpr said:
...
Keep an eye on those SMART stats. - as I said before, I'm not totally happy with that disk.
Click to expand...
I notice attribute 5 is at 200 - so will you consider this to be fine as long as it doesn't increase much or should OP prepare for a drive replacement?

thoughton said:
And here's the output from the smartctl -a /dev/sda command from post #26 (sorry I missed this one somehow):

Code: 
...
ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  1 Raw_Read_Error_Rate     0x000f   091   091   006    Pre-fail  Always       -       168521614
  3 Spin_Up_Time            0x0003   095   095   000    Pre-fail  Always       -       0
  4 Start_Stop_Count        0x0032   095   095   020    Old_age   Always       -       5937
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       200
...
Click to expand...
 
thoughton said:
I couldn't find these two recordings listed in the Media anymore, but honestly it's not a problem; that's a small price to pay. The random selection of other recordings I've tried so far all worked great.
Click to expand...
Fragments of the missing recordings may be in /mnt/hd2/lost+found/
 
bottletop said:
I notice attribute 5 is at 200 - so will you consider this to be fine as long as it doesn't increase much or should OP prepare for a drive replacement?
Click to expand...
200 is ok; I have seen drives working fine with well over a thousand. As you suggest, I think it is the rate that the reallocated sectors increase that is a very good indicator of the need for drive replacement.
 
You must log in or register to reply here.
Back
Top