Posted 2 January 2024 - 11:29
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.
Nope ...
The Vu+ Ultimo 4K has on the front 4 slots:
2 x CI Slots
2 x Smartcards
and I am trying to figure out which is which ....so I can perhaps prod the devices and see any data ....
"/dev/sci0"and = CI Slots reaader upper
"/dev/sci1"and = CI Slots reaader lowwer
"/dev/ttyUSB0" = Smartcard upper
"/dev/ttyUSB1" = Smartcard lower
Vu+ Duo4K SE with 45308X FBC and BCM3466 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Vu+ Ultimo4K with BCM3148, 45208 FBC and TT3L10 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Posted 2 January 2024 - 12:14
Eh, no.
CI slots are not accessable in linux, none of my VU+ boxes have a ttyUSB0 and ttyUSB1.
The smartcard readers are sci0 and sci1.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 2 January 2024 - 12:35
My HDDs problems continue after another restart 
and "/media/hdd" (that is the internal 4TB HDD) drive that I had yet not set the LABEL for
is again not showing up after numerous restarts.
I have changed the LABEL naming, just in case, to first part of UUID of each HDD:
e2label /dev/sda1 xxzz1234 e2label /dev/sdb1 yyzz4321 e2label /dev/sdc1 zzzz4321 #I'm awaiting for the drive to show up again to SET the LABEL
I have previously recorded it's UUID, so tried setting the FSTAB for all 3 HDD as follows:
mkdir /media/xxzz1234 mkdir /media/yyzz4321 mkdir /media/zzzz4312
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 UUID=zzzz4312-dcab-1234-4321-1234dcba4321 /media/zzzz4312 ext4 defaults 0 2
But the "third" (Internal SATA III) HDD is again not showing up and completely missing after numerous reboots
root@vuultimo4k:~# lsscsi -d [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:~# cat /proc/scsi/scsi Attached devices: Host: scsi2 Channel: 00 Id: 00 Lun: 00 Vendor: WD Model: easystore 25FA Rev: 1013 Type: Direct-Access ANSI SCSI revision: 06 Host: scsi2 Channel: 00 Id: 00 Lun: 01 Vendor: WD Model: SES Device Rev: 1013 Type: Enclosure ANSI SCSI revision: 06 Host: scsi3 Channel: 00 Id: 00 Lun: 00 Vendor: Samsung Model: M3 Portable Rev: 1404 Type: Direct-Access ANSI SCSI revision: 06
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/xxzz1234 sdb 8:16 0 1.8T 0 disk └─sdb1 8:17 0 1.8T 0 part /media/yyzz4321 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:~# 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/sda1 on /media/xxzz1234 type ext4 (rw,relatime,data=ordered) /dev/sdb1 on /media/yyzz4321 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)
root@vuultimo4k:~# ls -l /sys/class/ata_port/ lrwxrwxrwx 1 root root 0 Jan 1 1970 ata1 -> ../../devices/platform/brcmstb-ahci.0/ata1/ata_port/ata1 lrwxrwxrwx 1 root root 0 Jan 1 1970 ata2 -> ../../devices/platform/brcmstb-ahci.0/ata2/ata_port/ata2
root@vuultimo4k:~# cat /sys/bus/ide/devices/0.0/serial cat: can't open '/sys/bus/ide/devices/0.0/serial': No such file or directory
root@vuultimo4k:~# ls -l /dev/disk/by-path/ lrwxrwxrwx 1 root root 13 Jan 1 1970 platform-f03e0200.sdhci -> ../../mmcblk0 lrwxrwxrwx 1 root root 18 Jan 1 1970 platform-f03e0200.sdhci-boot0 -> ../../mmcblk0boot0 lrwxrwxrwx 1 root root 18 Jan 1 1970 platform-f03e0200.sdhci-boot1 -> ../../mmcblk0boot1 lrwxrwxrwx 1 root root 15 Jan 2 11:24 platform-f03e0200.sdhci-part1 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 Jan 1 1970 platform-f03e0200.sdhci-part2 -> ../../mmcblk0p2 lrwxrwxrwx 1 root root 15 Jan 2 11:24 platform-f03e0200.sdhci-part3 -> ../../mmcblk0p3 lrwxrwxrwx 1 root root 15 Jan 1 1970 platform-f03e0200.sdhci-part4 -> ../../mmcblk0p4 lrwxrwxrwx 1 root root 9 Jan 2 11:24 platform-f0470300.ehci_v2-usb-0:1:1.0-scsi-0:0:0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 Jan 2 11:24 platform-f0470300.ehci_v2-usb-0:1:1.0-scsi-0:0:0:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 Jan 2 11:24 platform-f0471000.xhci_v2-usb-0:2:1.0-scsi-0:0:0:0 -> ../../sda lrwxrwxrwx 1 root root 10 Jan 2 11:24 platform-f0471000.xhci_v2-usb-0:2:1.0-scsi-0:0:0:0-part1 -> ../../sda1
I have now installed the "smartmontools - 7.0-r0.6 - Control and monitor storage systems using S.M.A.R.T"
opkg install smartmontools smartmontools-doc
and trying to get the drive to show up again ....but the drive not even showing up on boot
root@vuultimo4k:~# dmesg | grep -i scsi [ 1.960918] scsi2 : usb-storage 2-2:1.0 [ 2.968352] scsi 2:0:0:0: Direct-Access WD easystore 25FA 1013 PQ: 0 ANSI: 6 [ 2.976687] scsi 2:0:0:1: Enclosure WD SES Device 1013 PQ: 0 ANSI: 6 [ 2.985710] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 2.996294] scsi 2:0:0:1: Attached scsi generic sg1 type 13 [ 4.788579] scsi3 : usb-storage 3-1:1.0 [ 5.252163] sd 2:0:0:0: [sda] Attached SCSI disk [ 5.794665] scsi 3:0:0:0: Direct-Access Samsung M3 Portable 1404 PQ: 0 ANSI: 6 [ 5.803620] sd 3:0:0:0: Attached scsi generic sg2 type 0 [ 5.910962] sd 3:0:0:0: [sdb] Attached SCSI disk
But on the positive side,
decoding channels from the top CI that has CA (Irdeto) and SkyLink card works again ......
Could it be, because one of the USB disks takes position on "/dev/sda" or could it be, that there is something wrong with the drive itself?
But previously, after one of the restarts it was working and all 3 HDD showed up (but CI that has CA Irdeto and SkyLink SmartCard) did not decode TV channels:
How could this be related??
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-1N21 0001
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, 2 January 2024 - 12:38.
Vu+ Duo4K SE with 45308X FBC and BCM3466 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Vu+ Ultimo4K with BCM3148, 45208 FBC and TT3L10 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Posted 2 January 2024 - 12:44
The more you do, the more you make it worse.
You don't need to label the harddisk, and you definitely don't have to add anything to fstab. So remove that all, it will interfere with the udev automounter.
The rules in the automounter are pretty simple:
and you can override this mechanism by labeling the device, after which the device is mounted on /media/<label>.
In all cases, if there is a name collision, the automounter reverts back to /media/<devicename>.
This covers 99.99% of all users.
Labeling may be needed for people using more than one USB device, as you can't control the order in which the kernel detects the USB devices, which makes the mountpoint unpredictable.
p.s. OpenPLi 9 has locking in the automounter, preventing concurrency issues, and multiple devices assigned to the same mointpoint.
Edited by WanWizard, 2 January 2024 - 12:49.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 2 January 2024 - 13:04
OK,
I have removed the FSTAB entry, reboot and same thing,
the internal SATA III HDD is still not showing up
root@vuultimo4k:~# dmesg | grep -i scsi [ 0.046354] SCSI subsystem initialized [ 0.264343] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252) [ 1.187321] scsi0 : ahci_platform [ 1.190983] scsi1 : ahci_platform [ 1.959989] scsi2 : usb-storage 2-2:1.0 [ 2.966392] scsi 2:0:0:0: Direct-Access WD easystore 25FA 1013 PQ: 0 ANSI: 6 [ 2.974724] scsi 2:0:0:1: Enclosure WD SES Device 1013 PQ: 0 ANSI: 6 [ 2.983745] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 2.994320] scsi 2:0:0:1: Attached scsi generic sg1 type 13 [ 3.502907] scsi3 : usb-storage 2-1:1.0 [ 4.508379] scsi 3:0:0:0: Direct-Access Samsung M3 Portable 1404 PQ: 0 ANSI: 6 [ 4.525309] sd 3:0:0:0: Attached scsi generic sg2 type 0 [ 4.612984] sd 3:0:0:0: [sdb] Attached SCSI disk [ 5.252432] sd 2:0:0:0: [sda] Attached SCSI disk
What is strange that when the internal SATA III drive mounts, there is no error and it performs as it should ....but decoding channels does not work ...
What would
# poweroff
do to the box?
Edited by 420f00f3, 2 January 2024 - 13:05.
Vu+ Duo4K SE with 45308X FBC and BCM3466 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Vu+ Ultimo4K with BCM3148, 45208 FBC and TT3L10 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Posted 2 January 2024 - 13:06
dmesg | grep -i sd
is more relevant, a lot of info is missing now.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 2 January 2024 - 13:14
Eh, no.
CI slots are not accessable in linux, none of my VU+ boxes have a ttyUSB0 and ttyUSB1.
The smartcard readers are sci0 and sci1.
Thanx for clarifying this for me 
How does the Box then access the two CI slots and decodes the channels?
Is that done withing the E2?
The smartcard readers "sci0" and "sci1" are there any bash/CLI tools to prod about and read/check the smart card?
Vu+ Duo4K SE with 45308X FBC and BCM3466 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Vu+ Ultimo4K with BCM3148, 45208 FBC and TT3L10 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Posted 2 January 2024 - 13:16
dmesg | grep -i sdis more relevant, a lot of info is missing now.
root@vuultimo4k:~# dmesg | grep -i sd [ 0.263064] Installing knfsd (copyright (C) 1996 okir@monad.swb.de). [ 1.972248] sdhci: Secure Digital Host Controller Interface driver [ 1.972250] sdhci: Copyright(c) Pierre Ossman [ 1.972251] sdhci-pltfm: SDHCI platform and OF driver helper [ 2.060034] mmc0: SDHCI controller on f03e0200.sdhci [f03e0200.sdhci] using ADMA [ 2.983745] sd 2:0:0:0: Attached scsi generic sg0 type 0 [ 2.984125] sd 2:0:0:0: [sda] Spinning up disk... [ 4.517516] sd 3:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 4.525309] sd 3:0:0:0: Attached scsi generic sg2 type 0 [ 4.525520] sd 3:0:0:0: [sdb] Write Protect is off [ 4.525525] sd 3:0:0:0: [sdb] Mode Sense: 33 00 00 08 [ 4.525750] sd 3:0:0:0: [sdb] No Caching mode page found [ 4.525753] sd 3:0:0:0: [sdb] Assuming drive cache: write through [ 4.547676] sd 3:0:0:0: [sdb] No Caching mode page found [ 4.553009] sd 3:0:0:0: [sdb] Assuming drive cache: write through [ 4.598101] sdb: sdb1 [ 4.601547] sd 3:0:0:0: [sdb] No Caching mode page found [ 4.606876] sd 3:0:0:0: [sdb] Assuming drive cache: write through [ 4.612984] sd 3:0:0:0: [sdb] Attached SCSI disk [ 4.990258] sd 2:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 4.997707] sd 2:0:0:0: [sda] 7813969920 512-byte logical blocks: (4.00 TB/3.63 TiB) [ 5.005468] sd 2:0:0:0: [sda] 4096-byte physical blocks [ 5.010901] sd 2:0:0:0: [sda] Write Protect is off [ 5.015709] sd 2:0:0:0: [sda] Mode Sense: 47 00 10 08 [ 5.015911] sd 2:0:0:0: [sda] No Caching mode page found [ 5.021240] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 5.027759] sd 2:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 5.035593] sd 2:0:0:0: [sda] No Caching mode page found [ 5.040919] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 5.230180] sda: sda1 [ 5.233189] sd 2:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). [ 5.240988] sd 2:0:0:0: [sda] No Caching mode page found [ 5.246320] sd 2:0:0:0: [sda] Assuming drive cache: write through [ 5.252432] sd 2:0:0:0: [sda] Attached SCSI disk [ 62.701204] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) [ 63.063559] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 84.760639] sd 3:0:0:0: [sdb] [ 84.767680] sd 3:0:0:0: [sdb]
Vu+ Duo4K SE with 45308X FBC and BCM3466 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Vu+ Ultimo4K with BCM3148, 45208 FBC and TT3L10 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Posted 2 January 2024 - 14:58
I only see two devices being detected here, sda and sdb? Which I guess are both USB devices?
scsi 0:0:0:0 isn't detected at all.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Posted 2 January 2024 - 17:16
I only see two devices being detected here, sda and sdb? Which I guess are both USB devices?
scsi 0:0:0:0 isn't detected at all.
That is correct, sometimes it gets detected and works, sometimes does not show up and it does not get detected
Vu+ Duo4K SE with 45308X FBC and BCM3466 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Vu+ Ultimo4K with BCM3148, 45208 FBC and TT3L10 running OpenPLi 8.3-release (2023-06-25-release-8.3)
Posted 2 January 2024 - 17:37
That suggests an issue at the hardware level: power cable, SATA cable, disk itself.
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
0 members, 2 guests, 0 anonymous users
