30 replies to this topic

[420f00f3]

I have searched this forum and not found answer to my question

I'm running:

Firmware version:    OpenPLi 8.3-release (2023-06-25-release-8.3)
Kernel / Drivers:    3.14.28 / 20190424

I have 3 HDDs connected.
4TB SATA III Internal, 4TB USB3.0 + 2TB USB3.0


But something is not right as after restart I have the SATA III missing
and USB drives are reporting as one in (/media/usb):

Hard disk model: WD (easystore 25FA)
Capacity:    2632.9 GB free / 3.6 TB ("4 TB") total (/media/usb)

Hard disk model: Samsung (M3 Portable)
Capacity:    2632.9 GB free / 1.8 TB ("2 TB") total (/media/usb)


The device has 3 tuners:
Vuplus DVB-C NIM(BCM3148) (DVB-C)
Vuplus DVB-S NIM(45208 FBC) (DVB-S2)
Vuplus DVB-C NIM(TT3L10) (MultiType DVB-C/T2)


I have done some digging, lsscsi, lsblk, sfdisk, mount showing following:
 

root@vuultimo4k:~# lsscsi
[2:0:0:0]       disk    WD      easystore 25FA  1013
[2:0:0:1]       enclosu WD      SES Device      1013
[3:0:0:0]       disk    Samsung M3 Portable     1404

root@vuultimo4k:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    0  3.7T  0 disk
└─sda1         8:1    0  3.7T  0 part /media/usb
sdb            8:16   0  1.8T  0 disk
└─sdb1         8:17   0  1.8T  0 part /media/usb
mtdblock0     31:0    0    2M  0 disk
mtdblock1     31:1    0   64K  0 disk
mtdblock2     31:2    0   64K  0 disk
mtdblock3     31:3    0   64K  0 disk
mtdblock4     31:4    0    4M  0 disk
mmcblk0      179:0    0  3.7G  0 disk
├─mmcblk0p1  179:1    0   16M  0 part
├─mmcblk0p2  179:2    0   16M  0 part
├─mmcblk0p3  179:3    0    2M  0 part
└─mmcblk0p4  179:4    0  3.6G  0 part /
mmcblk0boot0 179:16   0    4M  1 disk
mmcblk0boot1 179:32   0    4M  1 disk
mmcblk0rpmb  179:48   0  512K  0 disk

root@vuultimo4k:~# sfdisk -l
Disk /dev/mtdblock0: 2 MiB, 2097152 bytes, 4096 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


Disk /dev/mtdblock1: 64 KiB, 65536 bytes, 128 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


Disk /dev/mtdblock2: 64 KiB, 65536 bytes, 128 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


Disk /dev/mtdblock3: 64 KiB, 65536 bytes, 128 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


Disk /dev/mtdblock4: 4 MiB, 4194304 bytes, 8192 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


Disk /dev/mmcblk0: 3.66 GiB, 3909091328 bytes, 7634944 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: gpt
Disk identifier: AB...................................FBC

Device         Start     End Sectors  Size Type
/dev/mmcblk0p1  2048   34815   32768   16M Linux filesystem
/dev/mmcblk0p2 34816   67583   32768   16M Linux filesystem
/dev/mmcblk0p3 67584   71679    4096    2M Linux filesystem
/dev/mmcblk0p4 71680 7632895 7561216  3.6G Linux filesystem


Disk /dev/mmcblk0rpmb: 512 KiB, 524288 bytes, 1024 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


Disk /dev/mmcblk0boot1: 4 MiB, 4194304 bytes, 8192 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


Disk /dev/mmcblk0boot0: 4 MiB, 4194304 bytes, 8192 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


Disk /dev/sdb: 1.84 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: M3 Portable     
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: 0x1......ff

Device     Boot Start        End    Sectors  Size Id Type
/dev/sdb1        2048 3907028991 3907026944  1.8T 83 Linux


Disk /dev/sda: 3.65 TiB, 4000752599040 bytes, 7813969920 sectors
Disk model: easystore 25FA  
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: AB.............................FBC

Device     Start        End    Sectors  Size Type
/dev/sda1   2048 7813967871 7813965824  3.7T Linux filesystem

root@vuultimo4k:~# mount
/dev/mmcblk0p4 on / type ext4 (rw,relatime,nodelalloc,data=journal)
devtmpfs on /dev type devtmpfs (rw,relatime,size=800236k,nr_inodes=86265,mode=755)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tmpfs on /media type tmpfs (rw,relatime,size=64k)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime)
/dev/sdb1 on /media/usb type ext4 (rw,relatime,data=ordered)
/dev/sda1 on /media/usb type ext4 (rw,relatime,data=ordered)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)

ls -ilha /
   13 lrwxrwxrwx    1 root     root           9 Sep 10  2022 hdd -> "media/hdd" = RED

shows that /media/hdd is missing, so I tried creating on
 

mkdir /media/hdd

and reboot, but still no luck...

 

[ims]

And what about to use UUID for mount in fstab for each disk ?

[WanWizard]

They are not reported as one, they are both mounted on /media/usb.

 

It looks like you've ran into the problem that the udev mounter is not thread-safe, so two mounts running at the same time can decide to use the same mountpoint.

 

Easiest way to avoid that is to give (one of) them a seperate mountpoint using the e2label command:

e2label /dev/sdb m3

will mount it after a reboot on /media/m3

[420f00f3]

And what about to use UUID for mount in fstab for each disk ?

Not set FSTAB before, so reading up on this, would this look right to you?
 

mkdir /media/xxzz1234
mkdir /media/yyzz4321

nano /etc/fstab
######################################################################################################################################
# Internal / External HDD's
# <file system>                                 <mount point>           <type>  <options>                               <dump>  <pass>
UUID=xxzz1234-abcd-4321-1234-4321abcd1234        /media/xxzz1234            ext4    defaults                                0       2
UUID=yyzz4321-dcba-1234-4321-1234dcba4321         /media/yyzz4321            ext4    defaults                                0       2

#-----------------------------------------------------------
#https://help.ubuntu.com/community/Fstab
#https://help.ubuntu.com/community/LinuxFilesystemsExplained
#-----------------------------------------------------------
# <file system>
# The device/partition (by /dev location or UUID) that contain a file system.  Press space or tab.
# "sudo blkid" will display UUIDs for the HDDs

# <mount point>
# The directory on your root file system (aka mount point) from which it will be possible to access the content of the device/partition (note: swap has no mount point).
# Mount points should not have spaces in the names.
# field created with earlier "mkdir /mnt/scsi". You'd use the appropriate mount point from your system. Press space or tab.

# <type>
# Type of file system (see LinuxFilesystemsExplained).
# we're going to enter ext4 , which is the type of file system on our partition. Press space or tab.

# <options>
# Mount options of access to the device/partition (see the man page for mount).
# or use the options retrieved using "cat /etc/mtab". These are "rw,relatime". Press space or tab.
# ext4 rw,relatime,data=ordered 0 0

# <dump>
# Enable or disable backing up of the device/partition (the command dump). This field is usually set to 0, which disables it. Press space or tab.

# <pass>
# Controls the order in which fsck checks the device/partition for errors at boot time. The root device should be 1. Other partitions should be 2, or 0 to disable checking.

is "FSCK check"  on re/boot a good idea or should I set the "pass" option to "0"?
 

 

 

Can I re-mount with

sudo mount -a

without rebooting and while recording is in progress?
 

[420f00f3]

They are not reported as one, they are both mounted on /media/usb.

 

It looks like you've ran into the problem that the udev mounter is not thread-safe, so two mounts running at the same time can decide to use the same mountpoint.

 

Easiest way to avoid that is to give (one of) them a seperate mountpoint using the e2label command:

e2label /dev/sdb m3

will mount it after a reboot on /media/m3

 

Thank you for your reply, I see, this sound much easier then messing about with FSTAB .....

I will have to wait for the recordings to finish and the then  try it for both:

e2label /dev/sda sda
e2label /dev/sdb sdb

Edited by 420f00f3, 30 December 2023 - 20:57.

[WanWizard]

if you do that, you will no longer have a /media/usb, as that would create /media/sda and /media/sdb. It is probably better to use more meaningful names.

[420f00f3]

if you do that, you will no longer have a /media/usb, as that would create /media/sda and /media/sdb. It is probably better to use more meaningful names.

Thank you, no worries I am happy with sda and sdb ...

Searching for the problem, I have also found this, that is interesting to know that max size the box can handle is 16TB (armv7l)

https://www.satpimps...install-is-16TB

 

[WanWizard]

I find that a bit of an odd story, and a bit of the mark.

 

The limit here is the 32-bit block addressing which was until recently standard in ext4, and which has a 16TiB limit. This can be dealt with by using "-O 64bit" option when creating the filesystem, but for that you need a driver and toolset that is new enough.

 

The toolset is not the issue, it requires e2fsprogs v1.43 or newer, but we currently ship v1.46. So if you use a 20TB disk and you partition and format it in the box (which this guy didn't do), the 64bit flag will be added automatically.

 

The file system driver however is dependent on the kernel version, and some boxes run on ancient kernels...

 

You can check if your ext4 filesystem currently supports it using

tune2fs /dev/sdb1 -l | grep 64bit

Having said that, if you partition and format the disk on the box, we use the "bigalloc" option of ext4, which creates blocks of 256KB, and 2^32 blocks times 256KB gets you way beyond 16TiB.
 

[420f00f3]

I find that a bit of an odd story, and a bit of the mark.

 

The limit here is the 32-bit block addressing which was until recently standard in ext4, and which has a 16TiB limit. This can be dealt with by using "-O 64bit" option when creating the filesystem, but for that you need a driver and toolset that is new enough.

 

The toolset is not the issue, it requires e2fsprogs v1.43 or newer, but we currently ship v1.46. So if you use a 20TB disk and you partition and format it in the box (which this guy didn't do), the 64bit flag will be added automatically.

 

The file system driver however is dependent on the kernel version, and some boxes run on ancient kernels...

 

You can check if your ext4 filesystem currently supports it using

tune2fs /dev/sdb1 -l | grep 64bit

Having said that, if you partition and format the disk on the box, we use the "bigalloc" option of ext4, which creates blocks of 256KB, and 2^32 blocks times 256KB gets you way beyond 16TiB.
 

Thanx for sharing, great to know that there is an option

[WanWizard]

Well, if you're in need of more than 16TB of recording storage (I have 40TB here ), I strongly suggest a NAS instead of an internal disk...

[420f00f3]

Well, if you're in need of more than 16TB of recording storage (I have 40TB here ), I strongly suggest a NAS instead of an internal disk...

Nice  

I was checking amazon deals on storage and 20TB was before x mass for £289.99 - (Saturday, November 25 2023) = £14.4495/TB

The only problem with WD is that the drives in their range (WD 20TB Elements Desktop External Hard Drive - USB 3.0, Black) do not have a SATA port apparently

and best is to always go for Seagate (unless something has changed) ...

Having 16TB would solve the need for the external USB HDD's but luck of 4K content in the DVB-C/S2/T2 is not going to fill out the space anytime soon ...
22TB range still holding onto higher prices cca £19.95 and up o eBuyer ... https://www.ebuyer.c...--Internal/22TB

[420f00f3]

They are not reported as one, they are both mounted on /media/usb.

 

It looks like you've ran into the problem that the udev mounter is not thread-safe, so two mounts running at the same time can decide to use the same mountpoint.

 

Easiest way to avoid that is to give (one of) them a seperate mountpoint using the e2label command:

e2label /dev/sdb m3

will mount it after a reboot on /media/m3

I should have read the manual

https://manpages.ubu.../e2label.8.html

got an error on:

root@vuultimo4k:~# e2label /dev/sda sda
e2label: Bad magic number in super-block while trying to open /dev/sda
Found a gpt partition table in /dev/sda

root@vuultimo4k:~# e2label /dev/sdb sdb
e2label: Bad magic number in super-block while trying to open /dev/sdb
Found a dos partition table in /dev/sdb

So I am setting label on the partition rather then the drive ...so this worked great
thanx again @WanWizard and both USB drives are now showing.

e2label /dev/sda1 sda1
e2label /dev/sdb1 sdb1

All 3 drives are now showing up.
 

root@vuultimo4k:~# lsscsi

[2:0:0:0]    disk    WD    easystore 25FA    1013
[2:0:0:1]    enclosu    WD    SES Device    1013
[3:0:0:0]    disk    Samsung    M3 Portable    1404
[0:0:0:0]    disk    ATA    ST4000LM016-1xx1    0001

and

root@vuultimo4k:~# lsblk
NAME         MAJ:MIN RM  SIZE RO TYPE MOUNTPOINT
sda            8:0    0  3.7T  0 disk
└─sda1         8:1    0  3.7T  0 part /media/hdd
sdb            8:16   0  3.7T  0 disk
└─sdb1         8:17   0  3.7T  0 part /media/sda
sdc            8:32   0  1.8T  0 disk
└─sdc1         8:33   0  1.8T  0 part /media/sdb
mtdblock0     31:0    0    2M  0 disk
mtdblock1     31:1    0   64K  0 disk
mtdblock2     31:2    0   64K  0 disk
mtdblock3     31:3    0   64K  0 disk
mtdblock4     31:4    0    4M  0 disk
mmcblk0      179:0    0  3.7G  0 disk
├─mmcblk0p1  179:1    0   16M  0 part
├─mmcblk0p2  179:2    0   16M  0 part
├─mmcblk0p3  179:3    0    2M  0 part
└─mmcblk0p4  179:4    0  3.6G  0 part /
mmcblk0boot0 179:16   0    4M  1 disk
mmcblk0boot1 179:32   0    4M  1 disk
mmcblk0rpmb  179:48   0  512K  0 disk

Edited by 420f00f3, 31 December 2023 - 12:03.

[WanWizard]

Ah, yes, partitions, sorry for that.

 

As for disks, I mainly use Toshiba's at the moment (using Hitatchi's in the past), sofar turned out to be more reliable than WD. I have a set of Seagate ST0006VN001 (6TB)'s in a NAS, but with 11000 running hours not enough runtime to judge their quality.

 

eBuyer has good deals most of the time, but you always have to shop around for deals, the last time I needed 24 SSD's, CCL beat them by quite a margin...

 

To bad it's still too expensive to just go out and buy a 20TB, just to test if I was right in my assumptions. It is not a size I have a direct need for, and it is quite a single point of failure.

[420f00f3]

No worries
You solved 5y old problem with the box for me...... once again thank you very much.

 

 

CCL added to places to watch for deals, spares thanx.

 

 

I agree

My cheaper/quick solution at the time was to get 4TB inside (SATA III striping 2.5" portable),

4TB on Portable USB (for Back Up of the SATA III) and 2TB on Portable USB for settings/images etc.

(that time no one checked on the trip from US and bags reclaim walk trough the gates how much one brings in...)

but then things gone south and the drives did not work/show properly and there was no time .....

and maybe I will get to the NAS solution one day .......

Edited by 420f00f3, 31 December 2023 - 16:09.

[420f00f3]

As a side effect the channels in my package from the 23.5E stopped decoding.

Both CA and Smart Card are still in place.

 

So I guess could it be that I have left some Oscam files on /media/hdd that I was trying

few years back and once that become visible to the system again they got loaded by E2?

root@vuultimo4k:~# ls -ilha /etc/tuxbox/config/oscam-emu
  25210 drwxr-xr-x    2 root     root        4.0K Dec  3 22:17 .
  25209 drwxr-xr-x    3 root     root        4.0K Jun 29  2021 ..
  25206 -rw-r--r--    1 root     root          29 Dec 31 14:04 oscam.ccache
  24996 -rw-r--r--    1 root     root        1.0K Sep 10  2022 oscam.conf
  25003 -rw-r--r--    1 root     root         759 Nov 27 16:25 oscam.conf-opkg
  25238 -rw-r--r--    1 root     root         504 Aug 21  2021 oscam.conf.bak
  24988 -rw-r--r--    1 root     root          24 Nov 27 16:25 oscam.dvbapi
  25271 -rw-r--r--    1 root     root           0 Dec 31 14:04 oscam.emmcache
  25272 -rw-r--r--    1 root     root           0 Dec 31 14:04 oscam.emmstat
  24990 -rw-r--r--    1 root     root         355 Nov 27 16:25 oscam.provid
  25269 -rw-r--r--    1 root     root        4.9K Dec  3 17:53 oscam.server
  25267 -rw-r--r--    1 root     root        6.1K Nov 27 16:25 oscam.server-opkg
  25282 -rw-r--r--    1 root     root        6.4K Sep 11  2022 oscam.server.bak
  25266 -rw-r--r--    1 root     root         179 Dec  3 22:17 oscam.services
  25270 -rw-r--r--    1 root     root         289 Dec  3 22:17 oscam.services.bak
  24998 -rw-r--r--    1 root     root        6.9K Nov 27 16:25 oscam.srvid
  25274 -rw-r--r--    1 root     root         450 Sep 10  2022 oscam.user
  25273 -rw-r--r--    1 root     root         183 Nov 27 16:25 oscam.user-opkg
  25233 -rw-r--r--    1 root     root         202 Jul 15  2021 oscam.user.bak

What is the best way to reset the system back to defaults and have the card to decode the TV channels until I get the hang of the whole OScam thing ?

 

[WanWizard]

Make sure your looking at the right files.

 

In another topic you've mentioned you installed "oscam", but you're looking at the "oscam-emu" files here.

[420f00f3]

Make sure your looking at the right files.

 

In another topic you've mentioned you installed "oscam", but you're looking at the "oscam-emu" files here.

This is not something I wanted to deal with and not 2day

 

Looking here I see ......Server/Client ? ....

root@vuultimo4k:/etc/tuxbox/config/oscam# find / -name "*oscam*" -print
/usr/bin/oscam-emu
/usr/bin/oscam

 

 

 

So for the TV to work, I need just the Client = Emulator?
 

[WanWizard]

No clue what you are on about.

 

You have installed two different softcams. "Oscam", and "Oscam-emu". Both can work with the irdeto card, but only one can be active, and that one needs the correct reader configuration for the card.

 

So

• decide which one you need
• make sure it is configured properly for your card and cardreader
• make sure it is selected as the active softcam in the CI/Softcam menu

And if it then still doesn't work, work with the oscam log (via the oscam web interface) to figure out why not ( as mentioned in the other thread, you need RSA keys for an Irdeto card ).

[420f00f3]

No clue what you are on about.

 

You have installed two different softcams. "Oscam", and "Oscam-emu". Both can work with the irdeto card, but only one can be active, and that one needs the correct reader configuration for the card.

 

So

• icky partdecide which one you need
• make sure it is configured properly for your card and cardreader
• make sure it is selected as the active softcam in the CI/Softcam menu

And if it then still doesn't work, work with the oscam log (via the oscam web interface) to figure out why not ( as mentioned in the other thread, you need RSA keys for an Irdeto card ).

1] I have uninstalled the Oscam and re-installed "Oscam-emu" thanx for clearing this for me.

2] While I understand that it needs to be conf. properly ...

it's easier said then done ... but I am searching for answers how to do it ...

 

3] OK, just to make sure, the Ultimo has 2 x CA Slots = "/dev/sci0/1"and 2 x Smartcards = "/dev/ttyUSB0/1"?
 

[WanWizard]

No idea what you mean by "2 smartcards". Do you have USB card readers attached?

 

I can't help you with your config I'm afraid, I don't have such a card.