kyis

I'm on 2025.03.20a, it seems unable to move files with filenames containing a "$". It throws an error : "Error: Invalid filename path"

Everything is working as intended on my end, but my setup probably wasn't accounted for: I have two WAN links/ public IPs, a fast link with a dynamic IP I'm unable to forward ports through (say 1.1.1.1), another slightly slower with a static IP I'm using as failover for the first link and to forward ports through (say 2.2.2.2), the plugin probably tested the default link to get my external IP and associate it (1.1.1.1) to my www.hash.unraid.com subdomain, except that's not the one I'm forwarding from. Is there any way I can manually override the external IP to set my inbound link (2.2.2.2 in my example) or more complex but probably more flexible, a list of IPs assigned in order to www./www1./www2. etc?

@dmacias worked like a charm, everything is cool and quiet. Thanks a lot!

@dmacias thanks for taking the time, I'm running 2016.10.24

Same issue as xoddoza on a C2750D4I, I cleared my settings and reinstalled the plugin. Previously working board.json (its presence/absence in the ipmi folder doesn't seem to change anything): { "ASRockRack": { "raw": "00 3a 01", "auto": "00 00 00 00 00 00 00 00", "full": "64 64 64 64 64 64 64 64", "fans": { "CPU_FAN1": "00", "FAN_POS2": "00", "REAR_FAN1": "00", "FAN_POS4": "00", "FRNT_FAN1": "00", "FRNT_FAN2": "00", "FAN_POS7": "00", "FAN_POS8": "00" } } } Edit: I found that the fan.cfg file doesn't have anything for the board key, from the code it looks like that would make the configuration fail but I've run out of time to look into where that file is generated and why everything is grayed in the ui. I'll keep looking later. FANCONTROL="disable" FANPOLL="3" FANIP="" IPMIBOARD=""

@wgstarks I would wait to be able to update unRAID as a whole. Updating dependencies here and there is asking for trouble. ^^

@wgstarks ok here is my version (under unRAID 6.3.2) and truncated columns list which includes SERIAL, I think this column is a requirement you may be stuck until you can update unRAID if it isn't supported by your version. If it has just been renamed maybe... root@BlackHole:~# lsblk -V lsblk from util-linux 2.28.2 root@BlackHole:~# lsblk -h ... Available columns (for --output): NAME device name KNAME internal kernel device name MAJ:MIN major:minor device number FSTYPE filesystem type MOUNTPOINT where the device is mounted LABEL filesystem LABEL UUID filesystem UUID PARTTYPE partition type UUID PARTLABEL partition LABEL PARTUUID partition UUID PARTFLAGS partition flags RA read-ahead of the device RO read-only device RM removable device HOTPLUG removable or hotplug device (usb, pcmcia, ...) MODEL device identifier SERIAL disk serial number SIZE size of the device STATE state of the device OWNER user name GROUP group name MODE device node permissions ALIGNMENT alignment offset MIN-IO minimum I/O size OPT-IO optimal I/O size PHY-SEC physical sector size LOG-SEC logical sector size ROTA rotational device SCHED I/O scheduler name RQ-SIZE request queue size TYPE device type DISC-ALN discard alignment offset DISC-GRAN discard granularity DISC-MAX discard max bytes DISC-ZERO discard zeroes data WSAME write same max bytes WWN unique storage identifier RAND adds randomness PKNAME internal parent kernel device name HCTL Host:Channel:Target:Lun for SCSI TRAN device transport type SUBSYSTEMS de-duplicated chain of subsystems REV device revision VENDOR device vendor ...

@wgstarks ok, typical output should be : NAME="sdf" TYPE="disk" LABEL="" SIZE="4000787030016" MOUNTPOINT="" FSTYPE="" SERIAL="WD-WCC4E1YTHK4R" NAME="sdf1" TYPE="part" LABEL="" SIZE="4000786980352" MOUNTPOINT="" FSTYPE="xfs" SERIAL="" NAME="sdd" TYPE="disk" LABEL="" SIZE="250059350016" MOUNTPOINT="" FSTYPE="" SERIAL="S2R6NX0HB36987T" NAME="sdd1" TYPE="part" LABEL="" SIZE="250059317248" MOUNTPOINT="" FSTYPE="btrfs" SERIAL="" NAME="md6" TYPE="md" LABEL="" SIZE="6001175072768" MOUNTPOINT="/mnt/disk6" FSTYPE="" SERIAL="" NAME="sdb" TYPE="disk" LABEL="" SIZE="6001175126016" MOUNTPOINT="" FSTYPE="" SERIAL="WD-WX11D76D3L8C" NAME="sdb1" TYPE="part" LABEL="" SIZE="6001175076352" MOUNTPOINT="" FSTYPE="xfs" SERIAL="" NAME="md4" TYPE="md" LABEL="" SIZE="4000786976768" MOUNTPOINT="/mnt/disk4" FSTYPE="" SERIAL="" NAME="sdk" TYPE="disk" LABEL="" SIZE="6001175126016" MOUNTPOINT="" FSTYPE="" SERIAL="WD-WX21DC5J246D" ... And lines where type is "disk" are used by php to populate the array your error says is null. Try running the command again but remove the "2>/dev/null" maybe it'll give you some useful error.

@wgstarks History of plg files (way better ^^) following what trurl said : https://github.com/gfjardim/unRAID-plugins/commits/master/plugins/preclear.disk.plg For the hell of it what does this command return on your system ?: lsblk -nbP -o name,type,label,size,mountpoint,fstype,serial 2>/dev/null @ mentions DO work! That's great, no more endless quoting. ^^

Preclear plugin archive on github : https://github.com/gfjardim/unRAID-plugins/tree/master/archive

Successfully cleared my drive with the modification.

That was the next step, I'm rerunning a clear before that to see if it was a fluck or if it consistently fails on just one write. Edit: Exact same result, 2MB not written or failed, can't tell. I won't upload the log, it's identical to the previous one. I wonder if it might be an "off by 1" kind of error somewhere in the math, 2MB is the value of the sb parameter of dd, it might be used somewhere else. Edit: Memtest done no errors... I'm stumped Edit: Finally caught what I was looking for, I edited the script so the -t option would run over 1TB and I monitored dd_output, I got this amongst the normal output: dd: warning: partial read (1126400 bytes); suggest iflag=fullblock Added the flag inside the function write_disk(), clearing and praying (already past the point where the message was showing up).

Hi, can you please check this out : It should have been posted here to begin with I guess. ^^ Edit: Is there any way to increase verbosity on dd ? Looking at the script real quick it looks like all errors should be logged already but it's quite a large script/voodoo magic spell, I wouldn't want to edit anything half-assedly and screw with my data.

Same, 2MB return failure on zeroing early on, doesn't show up in the log though, it showed an error real quick and some recommendation in it, couldn't tell what it was. Log attached. BLACKHOLE-preclear.disk-20170222-0516.zip

Glad I could help, and I learned how plugin installation works on the way.