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

Failed recordings - and more!

I suppose all that's really needed is the summary report in the last couple of dozen lines, but my logs are only a few kB each. That suggests an awful lot of repairing.

I still recommend you run another fix-disk and see whether it comes up clean, no fixing. It should be very quick this time.

Code: 
----------------------------------------------------------------------
Mon Nov 20 14:43:38 GMT 2023: Fix-disk run starting...
----------------------------------------------------------------------

Checking disk sda (512 byte sectors)

Running short disk self test

No pending sectors found - skipping sector repair
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 20 14:44:48 GMT 2023: Checking partition /dev/sda3...
Pass 1: Checking inodes, blocks, and sizes
Pass 1: I/O read: 164MB, write: 0MB, rate: 22.01MB/s
Pass 2: Checking directory structure
Pass 2: I/O read: 1MB, write: 0MB, rate: 50.84MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 340k/0k (260k/81k), time:  8.04/ 2.92/ 2.53
Pass 3A: Memory used: 340k/0k (260k/81k), 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: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: I/O read: 1MB, write: 0MB, rate: 0.38MB/s

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

           7 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
------------
           9 files
Memory used: 340k/0k (53k/288k), time: 11.72/ 5.83/ 2.58
I/O read: 165MB, write: 1MB, rate: 14.08MB/s
Mon Nov 20 14:45:01 GMT 2023

Mon Nov 20 14:45:01 GMT 2023: Checking partition /dev/sda1...
Pass 1: Checking inodes, blocks, and sizes
Pass 1: I/O read: 17MB, write: 0MB, rate: 20.92MB/s
Pass 2: Checking directory structure
Pass 2: Memory used: 140k/0k (72k/69k), time:  0.02/ 0.00/ 0.00
Pass 2: I/O read: 1MB, write: 0MB, rate: 58.22MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 140k/0k (72k/69k), time:  0.96/ 0.27/ 0.43
Pass 3A: Memory used: 140k/0k (72k/69k), 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: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: I/O read: 1MB, write: 0MB, rate: 2.96MB/s

          15 inodes used (0.02%, out of 65808)
           1 non-contiguous file (6.7%)
           0 non-contiguous directories (0.0%)
             # of inodes with ind/dind/tind blocks: 2/2/0
       16733 blocks used (6.36%, out of 263064)
           0 bad blocks
           1 large file

           3 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
------------
           6 files
Memory used: 140k/0k (50k/91k), time:  1.44/ 0.66/ 0.43
I/O read: 17MB, write: 1MB, rate: 11.80MB/s
Mon Nov 20 14:45:02 GMT 2023

Creating swap file...

Mon Nov 20 14:45:26 GMT 2023: Checking partition /dev/sda2...
Pass 1: Checking inodes, blocks, and sizes
Pass 1: I/O read: 7609MB, write: 0MB, rate: 4.72MB/s
Pass 2: Checking directory structure
Pass 2: I/O read: 5MB, write: 0MB, rate: 1.18MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 1004k/9344k (845k/160k), time: 1636.19/923.27/85.83
Pass 3A: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 3: Memory used: 1004k/9344k (838k/167k), time:  0.07/ 0.05/ 0.00
Pass 3: I/O read: 1MB, write: 0MB, rate: 13.48MB/s
Pass 4: Checking reference counts
Pass 4: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
Pass 5: Checking group summary information
Pass 5: I/O read: 29MB, write: 0MB, rate: 0.24MB/s

       15100 inodes used (0.05%, out of 29860704)
        1366 non-contiguous files (9.0%)
          23 non-contiguous directories (0.2%)
             # of inodes with ind/dind/tind blocks: 1576/701/3
    82488974 blocks used (69.20%, out of 119209984)
           0 bad blocks
          21 large files

       13573 regular files
         596 directories
           2 character device files
           0 block device files
           0 fifos
          17 links
         919 symbolic links (913 fast symbolic links)
           1 socket
------------
       15108 files
Memory used: 1292k/0k (721k/572k), time: 1801.84/1057.34/87.07
I/O read: 7643MB, write: 1MB, rate: 4.24MB/s
Mon Nov 20 15:15:29 GMT 2023
Removing extra swap space.

----------------------------------------------------------------------
Mon Nov 20 15:15:31 GMT 2023: Fix-disk run ended.
----------------------------------------------------------------------
 
Black Hole said:
all that's really needed is the summary report in the last couple of dozen lines
Click to expand...
I can open the file and scroll thru to the end but I can't see any indication of "summary", and the final "group" has been repeated a few times earlier, making it unremarkable... if you see what I mean.

I will run fixdisk again when it can be slotted in (mentally as well as temporally 😜) and report back.

Thanks again.
 
clemenzina said:
the final "group" has been repeated a few times earlier, making it unremarkable... if you see what I mean.
Click to expand...
It should be three times – there are three partitions on the HDD, each is dealt with in turn. The last (and largest) one is the important partition for media and CF.

Did you scroll down my log (posted above, in a scrolling code section) to see what the final report should look like?
 
clemenzina said:
I've got 3 files, the Attach files method only sees the empty one:

So I'll C&P:


No I won't. The 3 files, after a l-o-n-g time, resolved into one but it's too large to upload, and umpteen C&P tries have left me frozen and crashed this page, so I must leave it for now.
Click to expand...
What you were seeing there was the internal workings of a web download, not the actual file (or file set). You were trying to do things with the download before the download had completed.

Please upload it to a file sharing site (do you use Dropbox? Google Drive?), I would like to have a look at it.
 
You must log in or register to reply here.
Back
Top