Tiny Core Linux
Tiny Core Base => Raspberry Pi => Topic started by: Yleisajattelija on November 05, 2026, 03:03:46 AM
-
Working for VSRV-port mirror site with Rasberry3b/5. Setting rotating RAID1 disk box with ancient HW without LAN-port. Rasberry is missing eSata, and at least this Raid-Box USB is not working with hdparm. Without hdparm some problems may come. There is classical security problems with PHP, which can maybe avoided with smart partition scheme. In this case disk formatting and partition must be made by IDE-connector without raidbox. I suppose this is not problem until disk crash, and then IDE-connector can be used again.
For partition setup experiments disks must be formatted anyway, so there should be any difference.
There might be some nasty side-effects I can't guess, any hints?
-
I was told once that, for USB connected drives, you need sdparm instead of hdparm. I was drawn away to other issues before I ever tried that so I don't know if that will help.
-
I was told once that, for USB connected drives, you need sdparm instead of hdparm. I was drawn away to other issues before I ever tried that so I don't know if that will help.
Sdparm works with SCSI-disks, and sometimes works with USB-drives, too. I don't know what is exactly standard busybox command set (probably there is not any...), but this piCore busybox has just hdparm. Problem is more RAID function than USB, if different type disks are allowed, is impossible to make setup transparent for both disks.
Hdparm is typically used to set DMA-transfer parameters and sleep timing, and if those are set directly by IDE (this case sata) connector, there should not be problems. Of course, if application try to set those parameters and error returns, there is a problem.
I do not see any reason for Cherokee to set those parameters.
-
sdparm posted to piCore64 repo
-
I'm asking myself, "why you don't use SSD drives?".
Answer: I will in future, but I have spinning HD RAID-box already, and there is documentation problems with those SSD-disks. EXT4 is no good for SSD-drives, and there is unknown problems with "burning through flash bits". Already handled in mobile phone file systems, but those file systems are very badly documented.
-
sdparm posted to piCore64 repo
Thanks! Will be needed with SSD-disks anyway.
-
I feel cozy:
Ubuntu documentation:
"hdparm --dco-restore
Reset all drive settings, features, and accessible capacities back to factory defaults and full capabilities. This command will fail if DCO is frozen/locked, or if a -Np maximum size restriction has also been set. This is EXTREMELY DANGEROUS and will very likely cause massive loss of data. DO NOT USE THIS COMMAND."
While project was permafrost state, RAID box was a donor for son's playmachine, and one disc is now renewed by identical "new old stock" unit. Pedantic soul would check, that setup is similar for both disks. "Fdisc" does find both disks, and it is bit questionable to fix something is already working....