No Recordings, No Disk Capacity?

[Black Hole]

I wish I knew what I've done with my USB-SATA adapter...

 

[Black Hole]

Now connected direct to my motherboard. HDD from a FVP-4000T, Seagate ST1000VM002 (1TB).

So presumably the first thing you are doing is a long Smart test?
Has anyone ever posted any details of the disk layout for one of these boxes? Partitions, filesystems etc.
I don't recall, but then I'm not really that interested as I'll probably never see one.

Here are the details gleaned by GParted:



It seemed to slug my Mint start-up, but the BIOS recognised it in the SATA table, and the system does boot eventually with this disk connected. It seems intact. Now for a long test...

 

[Black Hole]

Extended SMART test completed without errors. I think this is a working drive, 22k hours on it. If it doesn't work when I put it back, the suspicion falls on the FVP's SATA.

 

[prpr]

You need to do sudo e2fsck /dev/sdd1 and likewise for the other partitions to check the filesystems.
It might be interesting to run sudo dumpe2fs -h /dev/sdd1 and likewise also, just for info, before the e2fsck.

the suspicion falls on the FVP's SATA.

Got a spare disk to try?

 

[Black Hole]

Got a spare disk to try?

Not one I could rely on.

I'll get those dumps you mention.

If I wanted to turn this into a "fresh" disk, I guess I could use GParted to make it one big NTFS partition?

 

[Black Hole]

First of all, there's a directory dump attached in case anyone finds it of use for understanding how the FVP-4000T operates, all four partitions.

dumpe2fs:

root@Zen:/# dumpe2fs -h /dev/sdd1
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   hmx_int_stor
Last mounted on:          /media/owl/hmx_int_stor
Filesystem UUID:          1040f890-c49a-48c2-9edf-745f2f30d2dc
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              65152
Block count:              260544
Reserved block count:     13027
Overhead clusters:        8509
Free blocks:              252026
Free inodes:              65138
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      63
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8144
Inode blocks per group:   509
Flex block group size:    256
Filesystem created:       Sun Jan 15 06:05:14 2017
Last mount time:          Mon Jul 27 18:11:03 2026
Last write time:          Mon Jul 27 18:37:26 2026
Mount count:              17520
Maximum mount count:      -1
Last checked:             Sun Jan 15 06:05:14 2017
Check interval:           0 (<none>)
Lifetime writes:          85 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      1281ceaf-b4ec-41cc-8082-53776eef55de
Journal backup:           inode blocks
Journal features:         (none)
Total journal size:       16M
Total journal blocks:     4096
Max transaction length:   4096
Fast commit length:       0
Journal sequence:         0x00000044
Journal start:            0

root@Zen:/# dumpe2fs -h /dev/sdd2
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   hmx_int_stor
Last mounted on:          /media/owl/hmx_int_stor1
Filesystem UUID:          bfc2da68-774f-4df6-ba70-ee0efe113f6d
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              59670528
Block count:              238679713
Reserved block count:     11933985
Overhead clusters:        3796219
Free blocks:              165124569
Free inodes:              59644588
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      967
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    256
Filesystem created:       Sun Jan 15 06:05:14 2017
Last mount time:          Mon Jul 27 18:11:08 2026
Last write time:          Mon Jul 27 18:37:48 2026
Mount count:              17518
Maximum mount count:      -1
Last checked:             Sun Jan 15 06:05:14 2017
Check interval:           0 (<none>)
Lifetime writes:          402 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      5727b5df-4e2d-4000-a2b2-dfd46ce3bb53
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Total journal size:       128M
Total journal blocks:     32768
Max transaction length:   32768
Fast commit length:       0
Journal sequence:         0x00be381e
Journal start:            0

root@Zen:/# dumpe2fs -h /dev/sdd3
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   hmx_int_stor
Last mounted on:          /mnt/hd3
Filesystem UUID:          59e2f94e-24ca-4360-a71e-d24560fb2988
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              655360
Block count:              2620603
Reserved block count:     131030
Overhead clusters:        79657
Free blocks:              2540616
Free inodes:              655324
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      639
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    256
Filesystem created:       Sun Jan 15 06:05:18 2017
Last mount time:          Mon Jul 27 18:11:20 2026
Last write time:          Mon Jul 27 18:37:14 2026
Mount count:              17517
Maximum mount count:      -1
Last checked:             Sun Jan 15 06:05:18 2017
Check interval:           0 (<none>)
Lifetime writes:          11 GB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      5b4e9720-48e1-4eb9-a269-ce8fe3e60de8
Journal backup:           inode blocks
Journal features:         journal_incompat_revoke
Total journal size:       128M
Total journal blocks:     32768
Max transaction length:   32768
Fast commit length:       0
Journal sequence:         0x0000a272
Journal start:            0

root@Zen:/# dumpe2fs -h /dev/sdd4
dumpe2fs 1.47.0 (5-Feb-2023)
Filesystem volume name:   hmx_int_stor
Last mounted on:          <not available>
Filesystem UUID:          93378f3f-443f-4851-ac12-534361c24215
Filesystem magic number:  0xEF53
Filesystem revision #:    1 (dynamic)
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
Filesystem flags:         signed_directory_hash
Default mount options:    user_xattr acl
Filesystem state:         clean
Errors behavior:          Continue
Filesystem OS type:       Linux
Inode count:              655360
Block count:              2620603
Reserved block count:     131030
Overhead clusters:        79657
Free blocks:              2540939
Free inodes:              655348
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      639
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Flex block group size:    256
Filesystem created:       Sun Jan 15 06:05:20 2017
Last mount time:          Mon Jul 27 18:11:30 2026
Last write time:          Mon Jul 27 18:37:11 2026
Mount count:              17517
Maximum mount count:      -1
Last checked:             Sun Jan 15 06:05:20 2017
Check interval:           0 (<none>)
Lifetime writes:          199 MB
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:              256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      8a4be8cc-7d18-4cce-8b54-5553c1da5cc9
Journal backup:           inode blocks
Journal features:         (none)
Total journal size:       128M
Total journal blocks:     32768
Max transaction length:   32768
Fast commit length:       0
Journal sequence:         0x00000015
Journal start:            0

As for e2fsck, nothing to see here:

root@Zen:/# e2fsck /dev/sdd1
e2fsck 1.47.0 (5-Feb-2023)
hmx_int_stor: clean, 14/65152 files, 8518/260544 blocks
root@Zen:/# e2fsck /dev/sdd2
e2fsck 1.47.0 (5-Feb-2023)
hmx_int_stor: clean, 25940/59670528 files, 73555144/238679713 blocks
root@Zen:/# e2fsck /dev/sdd3
e2fsck 1.47.0 (5-Feb-2023)
hmx_int_stor: clean, 36/655360 files, 79987/2620603 blocks
root@Zen:/# e2fsck /dev/sdd4
e2fsck 1.47.0 (5-Feb-2023)
hmx_int_stor: clean, 12/655360 files, 79664/2620603 blocks

It's weird there is a Recordings folder (where the off-air recordings are) and a Media > Recordings folder (empty). The .ts files appear to be encrypted.

 

[EEPhil]

It's weird there is a Recordings folder (where the off-air recordings are) and a Media > Recordings folder (empty). The .ts files appear to be encrypted.

It's not weird, it's ruddy peculiar. From FTP and Humax menu access there's a recordings area, a download area and an internal HDD area. The download area can be FTPd to and from, the internal HDD can only be FTPd from and the files can't be deleted. Files are moved from the download area to the internal HDD from a Humax menu.
The recordings are encrypted. Decryption of StdDef is by copy to USB or using DLNA server. Not sure how it behaves as a network drive.

 

[EEPhil]

I was going to ask about how the disk is laid out - but I see that info is in the dump file. That should make interesting reading!

 

[prpr]

First of all, there's a directory dump attached in case anyone finds it of use for understanding how the FVP-4000T operates, all four partitions.

It's more reminiscent of what I remember from the Foxsat than it is of the T2.
What the hell are all those old .jpg files doing on there...

Just wondered what was in these:

.:
-rw-r--r--   1 root root   50176 Jun 15 20:56 .1519754427.db
-rw-r--r--   1 root root    3415 Sep 13  2021 .umount-proc-info

./diskstore:
-rw------- 1 root root 1734 Jun 15 17:18 manifest

The thing seems to have suddenly stopped working just after 21:00 on 15 Jun.

 

[Black Hole]

What the hell are all those old .jpg files doing on there...

In the .cache? They seem to be thumbnails, but a variable number per recording (up to about 5). I've grabbed them for one recording at random:

-Recordings-Abandoned_Engineering-20200728-0709_hjm-10.jpg
-Recordings-Abandoned_Engineering-20200728-0709_hjm-1752.jpg
-Recordings-Abandoned_Engineering-20200728-0709_hjm-2416.jpg
-Recordings-Abandoned_Engineering-20200728-0709_hjm-2968.jpg
-Recordings-Abandoned_Engineering-20200728-0709_hjm-729.jpg

I wonder if the numbers are seconds from the start of the recording, but I have no idea how those offsets might have been chosen, and can't explain why similar length recordings might have only one or two of these thumbnails.

Just wondered what was in these:

See post attachments.