12 replies to this topic

[SwedishChef]

Hello! 

 

Tested on three OpenPLi 9.1; 8.3 and Develop images.

 

My SSD connected to USB and initialized in OpenPLi is visible (telnet mount) as read-only.

PVR does not work !!! Can only be written to a FAT23 pendrive. 

 

The same SSD on OpenATV works and records.

 

Maybe someone has solved this problem?

[WanWizard]

Look in the dmesg output as to why it is mounted readonly.

 

Mounting is not image related, it is basic linux, and should be the same on every image.

[SwedishChef]

 telnet                          

openpli 9.1-release h8     

h8 login:
root@h8:~# mount
ubi0:rootfs on / type ubifs (rw,relatime)
devtmpfs on /dev type devtmpfs (rw,relatime,size=170092k,nr_inodes=42523,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)
configfs on /sys/kernel/config type configfs (rw,relatime)                  
tmpfs on /media type tmpfs (rw,relatime,size=64k,nr_inodes=42558)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /run type tmpfs (rw,nosuid,nodev,size=170488k,nr_inodes=42622,mode=755)
tmpfs on /var/volatile type tmpfs (rw,relatime,size=170488k,nr_inodes=42622)
/dev/sda1 on /media/usb type ext4 (ro,relatime,data=ordered)                              <---- my SSD
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620)
nfsd on /proc/fs/nfsd type nfsd (rw,relatime)                                

[Tech]

That's not dmesg output but the output from 'mount' and doesn't provide enough info to find out why the ssd is mounted as read-only.

[Pr2]

There is menu where you can perform a fsck (file systemcheck) of your disk, it can be helpful to run it.

[SwedishChef]

root@h8:/# fsck.ext4 /dev/sda1
/dev/sda1 is mounted.
e2fsck: Cannot continue, aborting.

dmesg

blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write 

TNX all for your interest in my problem.

[SwedishChef]

I zeroed the SSD of each cluster using [DMDE] in Windows. It didn't report any errors.

SMART also doesn't report any errors.

I would like to mention that on OpenATV and Ext4 everything works like a charm.

The disk is set to write R/W

 

For now I use a pendrive on the same USB port in OpenPLi and I have no problems with it on FAT32 systems. NTFS or Ext4 - PVR works,

but I want to connect an SSD

[WanWizard]

There is no reason why it wouldn't work, this is all basic linux OS stuff.

 

But again, without a proper log, we can't do or say much. So, unplug the disk, and issue the command

dmesg -c

which will clear the message buffer. Then plug the disk in, and do

dmesg

and upload ALL output of this command here.
 

 

[SwedishChef]

openpli 8.3-release h8

h8 login: root
Last login: Mon Apr 14 14:00:13 CEST 2025 on pts/0
root@h8:~# dmesg
PPP generic driver version 2.4.2
PPP BSD Compression module registered
PPP Deflate Compression module registered
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-platform: EHCI generic platform driver
ehci-platform f9890000.ehci: EHCI Host Controller
ehci-platform f9890000.ehci: new USB bus registered, assigned bus number 1
ehci-platform f9890000.ehci: irq 20, io mem 0xf9890000
ehci-platform f9890000.ehci: USB 2.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-platform: OHCI generic platform driver
ohci-platform f9880000.ohci: Generic Platform OHCI controller
ohci-platform f9880000.ohci: new USB bus registered, assigned bus number 2
ohci-platform f9880000.ohci: irq 21, io mem 0xf9880000
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usbserial
usbcore: registered new interface driver usbserial_generic
usbserial: USB Serial support registered for generic
usbcore: registered new interface driver usb_debug
usbserial: USB Serial support registered for debug
usbcore: registered new interface driver option
usbserial: USB Serial support registered for GSM modem (1-port)
mousedev: PS/2 mouse device common for all mice
usbcore: registered new interface driver xpad
i2c /dev entries driver
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR Sharp protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR XMP protocol handler initialized
usbcore: registered new interface driver uvcvideo
USB Video Class driver (1.1.1)
sp805-wdt f8a2c000.watchdog: registration successful
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ashmem: initialized
usbcore: registered new interface driver snd-usb-audio
Netfilter messages via NETLINK v0.30.
nfnl_acct: registering with nfnetlink.
ip_tables: (C) 2000-2006 Netfilter Core Team
arp_tables: (C) 2002 David S. Miller
NET: Registered protocol family 10
NET: Registered protocol family 17
Key type dns_resolver registered
Registering SWP/SWPB emulation handler
ubi0: default fastmap pool size: 85
ubi0: default fastmap WL pool size: 42
ubi0: attaching mtd9
usb 1-1: new high-speed USB device number 2 using ehci-platform
usb-storage 1-1:1.0: USB Mass Storage device detected
scsi host0: usb-storage 1-1:1.0
ubi0: scanning is finished
ubi0: attached mtd9 (name "rootfs", size 444 MiB)
ubi0: PEB size: 262144 bytes (256 KiB), LEB size: 253952 bytes
ubi0: min./max. I/O unit sizes: 4096/4096, sub-page size 4096
ubi0: VID header offset: 4096 (aligned 4096), data offset: 8192
ubi0: good PEBs: 1773, bad PEBs: 3, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 2/0, WL threshold: 128, image sequence number: 1750827591
ubi0: available PEBs: 0, total reserved PEBs: 1773, PEBs reserved for bad PEB handling: 37
ubi0: background thread "ubi_bgt0d" started, PID 825
ALSA device list:
  No soundcards found.
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 828
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery completed
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS (ubi0:0): LEB size: 253952 bytes (248 KiB), min./max. I/O unit sizes: 4096 bytes/4096 bytes
UBIFS (ubi0:0): FS size: 436797440 bytes (416 MiB, 1720 LEBs), journal size 9404416 bytes (8 MiB, 38 LEBs)
UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID AB85A3D8-F423-451B-98E3-7B41FAD8E240, small LPT model
VFS: Mounted root (ubifs filesystem) on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 280K
This architecture does not have kernel memory protection.
scsi 0:0:0:0: Direct-Access     Patriot  Burst            0117 PQ: 0 ANSI: 6
sd 0:0:0:0: [sda] Spinning up disk...
random: nonblocking pool is initialized
h8_1: loading out-of-tree module taints kernel.
hisi-sndcard hisi-sndcard: aiao-hifi <-> hisi-i2s mapping ok
.ready
sd 0:0:0:0: [sda] 468862128 512-byte logical blocks: (240 GB/224 GiB)
sd 0:0:0:0: [sda] Write Protect is off
sd 0:0:0:0: [sda] Mode Sense: 47 00 10 08
sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
 sda: sda1
sd 0:0:0:0: [sda] Attached SCSI disk
input: front panel as /devices/virtual/input/input0
input: dreambox advanced remote control (native) as /devices/virtual/input/input1
input: rc mouse emulation as /devices/virtual/input/input2
DVB: registering new adapter (dvb0)
platform dvb0.0: DVB: registering adapter 0 frontend 0 (DVB-S2)...
platform dvb0.0: DVB: registering adapter 0 frontend 1 (DVB-T/T2/C)...
udevd[1042]: starting version 3.2.8
udevd[1043]: starting eudev-3.2.8
JBD2: Clearing recovery information on journal
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 0c 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 201328640
Buffer I/O error on dev sda1, logical block 25165824, lost sync page write
JBD2: Error -5 detected when updating journal superblock for sda1-8.
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
hieth f9c30000.hieth eth0: Link is Up - 100Mbps/Full - flow control rx/tx
IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 0c 00 08 18 00 00 08 00
blk_update_request: critical target error, dev sda, sector 201328664
blk_update_request: critical target error, dev sda, sector 201328664
Aborting journal on device sda1-8.
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 0c 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 201328640
Buffer I/O error on dev sda1, logical block 25165824, lost sync page write
JBD2: Error -5 detected when updating journal superblock for sda1-8.
EXT4-fs (sda1): previous I/O error to superblock detected
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write
EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
EXT4-fs (sda1): Remounting filesystem read-only
EXT4-fs (sda1): previous I/O error to superblock detected
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x1 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x37 ASCQ=0x0
 sda: sda1
 sda: sda1
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write
EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 0c 00 08 50 00 00 08 00
blk_update_request: critical target error, dev sda, sector 201328720
blk_update_request: critical target error, dev sda, sector 201328720
Aborting journal on device sda1-8.
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 0c 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 201328640
Buffer I/O error on dev sda1, logical block 25165824, lost sync page write
JBD2: Error -5 detected when updating journal superblock for sda1-8.
EXT4-fs (sda1): previous I/O error to superblock detected
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write
EXT4-fs error (device sda1): ext4_journal_check_start:56: Detected aborted journal
EXT4-fs (sda1): Remounting filesystem read-only
EXT4-fs (sda1): previous I/O error to superblock detected
sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08
sd 0:0:0:0: [sda] tag#0 Sense Key : 0x5 [current]
sd 0:0:0:0: [sda] tag#0 ASC=0x24 ASCQ=0x0
sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x2a 2a 08 00 00 08 00 00 00 08 00
blk_update_request: critical target error, dev sda, sector 2048
Buffer I/O error on dev sda1, logical block 0, lost sync page write
root@h8:~#

[WanWizard]

Either the connection is bad, the controller is bad, or the disk is bad, but no way that works on any other OS, unless the problem is the specific USB port or USB controller it is connected to.

[SwedishChef]

I'm wondering about this myself, that's why I wrote on the OpenPLi forum, because I couldn't handle it myself. I don't know much about UNIX. There must be some bug in the OpenPLi driver.

 

The same STB, the same cabling. The same disk, the same USB port, just the firmware from OpenATV and everything works like a charm.

 

The disk saves, you can set the directories /hdd/movie and /hdd/timeshift on this SSD and everything works fine. But I don't want to use OpenATV because it's overloaded and the Zgemma H8.2H has only 512kB ROM and RAM, so I prefer the OpenPLi image, besides, for me it's friendly, minimalistic and pretty.  

 

Thank you for your interest and help.

[SwedishChef]

Eureka

I remembered that I still have an NVMe disk in the box on the RTL9210B this disk initialized. PVR returned I can write to this disk.

[WanWizard]

I'm wondering about this myself, that's why I wrote on the OpenPLi forum, because I couldn't handle it myself. I don't know much about UNIX. There must be some bug in the OpenPLi driver.

 

I've been telling you several times now: there is no such thing as "an openpli driver". This is all basic linux OS stuff, and the same for every linux device, from your washing machine to a server running Redhat Enterprise.

 

So it is impossible that you don't have these same problems on other linux devices, unless like I wrote the problem is device hardware related (and not disk hardware related). Which you can test by installing ATV on that H8.2H.

 

One other possibility is that the USB port doesn't supply the required 0.5A of power, other reports of your error messages seem to support that, and adding external power to the device fixed the problem.