Black Hole
May contain traces of nut
Why? Ah, do they have .0.log, .1.log, .2.log?
Attaching files allows .txt and zip. You can either rename the log file to .txt, or you can zip it.
-
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!
- Thread starter clemenzina
- Start date
OP
clemenzina
Forum Supporter
Even the .zip file is too big for the system to upload it. It's 41,554 KB.
If nothing more can be done, thank you @Black Hole for getting me this far, and thank you @MartinLiddle for repeated encouragement
If nothing more can be done, thank you @Black Hole for getting me this far, and thank you @MartinLiddle for repeated encouragement
Black Hole
May contain traces of nut
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.
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.
----------------------------------------------------------------------
OP
clemenzina
Forum Supporter
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.
Black Hole
May contain traces of nut
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?
Black Hole
May contain traces of nut
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.
OP
clemenzina
Forum Supporter
@Black Hole - this should be a link to OneDrive but I don't consciously use it, it has a mind of its own.
(EDIT - The doc wouldn't open for me, it froze everything.)
(EDIT2 - It seems to be working, I don't belieeeve it
)
fix-disk.0.log.txt
(EDIT - The doc wouldn't open for me, it froze everything.)
(EDIT2 - It seems to be working, I don't belieeeve it
)fix-disk.0.log.txt
Last edited:
Black Hole
May contain traces of nut
You seem to expect things to be instant. When moving large amounts of data around, one needs to be patient. As you uploaded the raw file (not the zip), I am now downloading 355MB!!!
Why the hell is it that big? I realise you have a 2TB HDD, but...
OP
clemenzina
Forum Supporter
No I don't, but I had no idea of its size when this started out, and had no idea why, for such a long time, there were 3 files labelled 0, PART and PART, nor when trying to view in OneDrive, which appeared to upload it completely right away, Firefox said "this page is slowing me down, shall we stop it?".
You are such a hard man, @Black Hole, albeit helluva helpful
EDIT - I'd better delete that file after you've got it.
Last edited:
Black Hole
May contain traces of nut
It takes about 2 minutes just to load into xed!
I have bad news: the HDD might look healthy from a hardware point of view (although the short self-test had to repair a few blocks), but the file system is trashed. sda3 (partition 3, if you like) is only small, and was OK. sda1 (mainly the TSR buffer) is larger and had a vast number of inode errors, but seems to have been fixed up OK. sda2 (the big one, where recordings go) was a repeat of sda1, but being a much bigger partition the list of errors occupies the bulk of the log file (90%? – the sda1 log was big enough!)... but fixdisk runs out of memory and aborts early without completing normally. That's why there is no "summary" at the end. "memory allocation failed" should have been the clue.
In short, your file system is not fixed. A re-run of fixdisk would have told us that. IMO your only ways forward are to connect the HDD to a Linux PC and run commands equivalent to fixdisk (a PC will have much more memory, and be faster – there are instructions somewhere), or reformat the disk in-situ. Those more technically competent than me might have other ideas, but...
If anyone wants to inspect the gory details (without the tedium), I've extracted key elements and sample errors into the spoiler below.
I have bad news: the HDD might look healthy from a hardware point of view (although the short self-test had to repair a few blocks), but the file system is trashed. sda3 (partition 3, if you like) is only small, and was OK. sda1 (mainly the TSR buffer) is larger and had a vast number of inode errors, but seems to have been fixed up OK. sda2 (the big one, where recordings go) was a repeat of sda1, but being a much bigger partition the list of errors occupies the bulk of the log file (90%? – the sda1 log was big enough!)... but fixdisk runs out of memory and aborts early without completing normally. That's why there is no "summary" at the end. "memory allocation failed" should have been the clue.
In short, your file system is not fixed. A re-run of fixdisk would have told us that. IMO your only ways forward are to connect the HDD to a Linux PC and run commands equivalent to fixdisk (a PC will have much more memory, and be faster – there are instructions somewhere), or reformat the disk in-situ. Those more technically competent than me might have other ideas, but...
If anyone wants to inspect the gory details (without the tedium), I've extracted key elements and sample errors into the spoiler below.
Code:
Checking disk sda (4096 byte sectors)
Running short disk self test
Error at LBA 3601079504
Also checking blocks 3601079504 - 3601079511 (8 blocks)
Block 3601079504 - OK
Block 3601079505 - - Repaired
Block 3601079506 - - Repaired
Block 3601079507 - - Repaired
Block 3601079508 - - Repaired
Block 3601079509 - - Repaired
Block 3601079510 - - Repaired
Block 3601079511 - - Repaired
LBA: 3601079504 is on partition /dev/sda2, start: 2104512, bad sector offset: 3598974992
LBA 3601079504 maps to file system block 449871874 on /dev/sda2
Block 449871874 is marked as in use
Block Inode number 449871874 <block not found>
Checking partition /dev/sda3...
/lost+found not found. Create? yes
13 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: 1/1/0
112534 blocks used (4.29%, out of 2622611)
0 bad blocks
1 large file
2 regular files
1 directory
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
3 files
Checking partition /dev/sda1...
*** HUGE LIST OF INODE AND ILLEGAL BLOCK ERRORS. SAMPLES ONLY: ***
Inode 29990 has imagic flag set. Clear? yes
Inode 29990 has a extra size (19510) which is invalid
Special (device/socket/fifo) inode 29990 has non-zero size. Fix? yes
Inode 29991 has EXTENTS_FL flag set on filesystem without extents support.
Inode 29992 is in use, but has dtime set. Fix? yes
Inode 29998 has compression flag set on filesystem without compression support. Clear? yes
*** I PRSUME THOSE MEAN THE HDD WAS FORMATTED ELESWHERE AND ARE MINOR FIXES ***
*** LINES LIKE THESE ARE MORE CONCERNING: ***
Illegal block #0 (3205519938) in inode 30159. CLEARED.
Inode 30159 is too big. Truncate? yes
Block #1 (55807) causes symlink to be too big. CLEARED.
Inode 30159 has INDEX_FL flag set but is not a directory.
Clear HTree index? yes
Inode 30159, i_blocks is 1114114465, should be 0. Fix? yes
Illegal block #0 (1206978739) in inode 29834. CLEARED.
Illegal block #1 (4239998166) in inode 29834. CLEARED.
Illegal block #2 (3120097678) in inode 29834. CLEARED.
Illegal block #3 (1437275640) in inode 29834. CLEARED.
Illegal block #4 (598739552) in inode 29834. CLEARED.
Illegal block #5 (2194670475) in inode 29834. CLEARED.
Illegal block #6 (1597454646) in inode 29834. CLEARED.
Illegal block #7 (440060746) in inode 29834. CLEARED.
Illegal block #8 (947846767) in inode 29834. CLEARED.
Illegal block #9 (4871329) in inode 29834. CLEARED.
Illegal block #10 (3209647023) in inode 29834. CLEARED.
Too many illegal blocks in inode 29834.
Clear inode? yes
*** PASS 1 SUMMARY: ***
Pass 1: I/O read: 58MB, write: 41MB, rate: 3.16MB/s
Restarting e2fsck from the beginning...
Pass 1: Checking inodes, blocks, and sizes
Special (device/socket/fifo/symlink) file (inode 35767) has immutable
or append-only flag set. Clear? yes
Special (device/socket/fifo) inode 35767 has non-zero size. Fix? yes
Running additional passes to resolve blocks claimed by more than one inode...
Pass 1B: Rescanning for multiply-claimed blocks
Multiply-claimed block(s) in inode 8: 1334
Multiply-claimed block(s) in inode 34440: 217
Multiply-claimed block(s) in inode 41189: 1334
Multiply-claimed block(s) in inode 53764: 114
Multiply-claimed block(s) in inode 54020: 114
Multiply-claimed block(s) in inode 54276: 114
Multiply-claimed block(s) in inode 54532: 114
Multiply-claimed block(s) in inode 56068: 114
Pass 1b: Memory used: 696k/0k (664k/33k), time: 4.59/ 0.81/ 1.11
Pass 1b: I/O read: 17MB, write: 0MB, rate: 3.70MB/s
Pass 1C: Scanning directories for inodes with multiply-claimed blocks
Pass 1c: Memory used: 696k/0k (664k/33k), time: 0.04/ 0.00/ 0.00
Pass 1c: I/O read: 1MB, write: 0MB, rate: 22.46MB/s
Pass 1D: Reconciling multiply-claimed blocks
(There are 7 inodes containing multiply-claimed blocks.)
File <The journal inode> (inode #8, mod time Sat Jan 2 00:02:59 1971)
has 1 multiply-claimed block(s), shared with 1 file(s):
... (inode #41189, mod time Wed Dec 18 06:56:00 1912)
Clone multiply-claimed blocks? yes
File ... (inode #34440, mod time Thu Sep 2 15:21:53 2010)
has 1 multiply-claimed block(s), shared with 1 file(s):
<filesystem metadata>
Clone multiply-claimed blocks? yes
.
.
.
Pass 1d: Memory used: 696k/0k (665k/32k), time: 0.41/ 0.27/ 0.00
Pass 1d: I/O read: 1MB, write: 1MB, rate: 2.43MB/s
Pass 1: Memory used: 696k/0k (617k/80k), time: 6.82/ 2.23/ 1.55
Pass 1: I/O read: 33MB, write: 1MB, rate: 4.84MB/s
Pass 2: Checking directory structure
Directory inode 41189 has an unallocated block #0. Allocate? yes
i_faddr for inode 41189 (???) is 620822728, should be zero.
Extended attribute block for inode 41189 (???) is invalid (3025469440).
Directory inode 53764 has an unallocated block #0. Allocate? yes
Directory inode 54020 has an unallocated block #0. Allocate? yes
.
.
.
Directory inode 56068, block #3, offset 0: directory corrupted
Directory inode 41189, block #5, offset 0: directory corrupted
Pass 2: Memory used: 784k/0k (464k/321k), time: 0.06/ 0.04/ 0.00
Pass 2: I/O read: 1MB, write: 1MB, rate: 16.27MB/s
Pass 3: Checking directory connectivity
Peak memory: Memory used: 784k/0k (464k/321k), time: 38.32/17.10/ 8.39
Unconnected directory inode 34440 (/???)
Connect to /lost+found? yes
/lost+found not found. Create? yes
Unconnected directory inode 41189 (/???)
Connect to /lost+found? yes
Unconnected directory inode 53764 (/???)
Connect to /lost+found? yes
.
.
.
Pass 3A: Optimizing directories
Pass 3A: Memory used: 820k/0k (464k/356k), time: 0.00/ 0.00/ 0.00
Pass 3A: I/O read: 1MB, write: 1MB, rate: 210.79MB/s
Pass 3: Memory used: 820k/0k (464k/357k), time: 0.03/ 0.01/ 0.00
Pass 3: I/O read: 1MB, write: 1MB, rate: 34.65MB/s
Pass 4: Checking reference counts
Inode 2 ref count is 0, should be 4. Fix? yes
Inode 29426 (...) has invalid mode (071556).
i_faddr for inode 29429 (...) is 252644878, should be zero.
i_file_acl_hi for inode 29429 (...) is 3084, should be zero.
Extended attribute block for inode 29429 (...) is invalid (185142029).
Unattached inode 29429
Connect to /lost+found? yes
Inode 29429 ref count is 33793, should be 1. Fix? yes
Inode 29430 (...) has invalid mode (02404).
Inode 29432 (...) has invalid mode (0161067).
Inode 29433 (...) is an illegal character device.
.
.
.
Pass 4: I/O read: 8MB, write: 7MB, rate: 2.03MB/s
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (22483, counted=22446).
Free blocks count wrong for group #1 (31273, counted=31272).
Free blocks count wrong (247871, counted=247833).
.
.
.
Pass 5: Memory used: 820k/0k (78k/743k), time: 0.43/ 0.42/ 0.01
Pass 5: I/O read: 0MB, write: 0MB, rate: 0.00MB/s
765 inodes used (1.16%, out of 65808)
2 non-contiguous files (0.3%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 10337/10244/10463
15229 blocks used (5.79%, out of 263062)
0 bad blocks
1 large file
5 regular files
9 directories
192 character device files
183 block device files
220 fifos
4294967289 links
0 symbolic links (0 fast symbolic links)
148 sockets
5 files
Checking partition /dev/sda2...
*** THEN WE GO INTO A REPEAT OF RESULTS FROM SDA1, BUT EVEN MORE SO ***
*** (SDA2 IS THE BIG PARTITION)... EXCEPT MEMORY RUNS OUT AND FIXDISK ***
*** TERMINATES EARLY ***
...
Error storing directory block information (inode=1845529, block=0, num=115744): Memory allocation failed
Last edited: