mattbr

Hey, I'm trying to figure out how to make RSync work over an Unassigned Devices mounted SMB share. I'm trying to sync around 200k files, over several thousand folders, and it's simply refusing to have a friendly discussion about special characters. I'm -avsP'ing everything, because I'm not quite that stupid, but there's still a whole bunch of files that won't copy. I've tried DirSyncPro as well, to no avail, so my current assumption is that it's something that has to do with Unassigned Devices... Any way around this without having to go at it manually / rename the offending files and folders ?

Yeah, figured this wasn't the one to cut my dockerisation newbie teeth on... looks like it's VM time, folks ! (and thanks for taking the time to look into it, @Squid)

Hey guys, would anyone with the knowledge on how to do this be willing to take the time to make an UnRaid template for this PFSense log visualiser ?

For those with adoption problems, this seems to have done the trick. It'd been mentioned here, but without a walkthrough. For some reason, the GUI approach didn't work for me. TL;DR: ssh into the AP. then mca-cli Now issue the set-inform command with the IP address of your Unifi controller [in our case, the IP of your UnRaid box. Don't forget to change to the correct port if you're not allocating 8080 to the controller]. set-inform http://192.168.3.2:8080/inform

Figured - and I'd assume assigning the data drives randomly won't change a thing since parity is going to be rebuilt. (in case someone else runs into something like this: remember to turn Docker off when you restart the array, in case one of the apps start hitting one of the drives. Looks like it happened here, so my (possible) pain is your gain)

There's a new config step before that, right ? So new config - check which don't have a FS - new config - assign the drives without a fs to parity - start.

Oookay... so, it looks like something happened, either from me hitting the power button, or from the usb drive going down. Super.dat won't fly, and one of the drives shows as having no filesystem (I'd assume that was the parity drive, but I was running dual parity, so...). Is there a human-readable version of the previous drive assignments somewhere ?

Great, thanks a lot for the help !!!

Well, wouldn't mount this time... but booted fine from a freshly flashed key. So I guess that's that... I'm a moron who didn't do a screenshot of my drive configuration, is that stored somewhere, or should I risk booting things up with the old super.dat ?

Hi guys, my unraid box went down yesterday. Started looking into it this morning, and I'm a bit stumped. My feeling is it could either be an LSI controller or a cable gone bad (there's a bunch of drives missing from the LSi bios page), but the kernel panic message itself seems to point more towards a system thumbdrive issue, (it happens right after there's an attempted mount on it) even though it mounts and copies fine on an other machine. Anybody got ideas ? X10SDV kernel panic.mp4

Also, there's this cute little kink with the SM BMC where you need to physically unplug the device to make it reset and actually apply the cooling profile... lowering the thresholds fixed the rest of it, thanks a lot for the hint !!! (while I'm at it - I'd also corrected the temp thresholds for the M.2, since they're significantly higher than what you'd have for those spinny 60's things we still have to live with for the time being... not sure it had any effect other than no more blinky gifs, which is something)

And useful to stop the SM boards from the annoying cycling thing, too I'd tried the raw commands, they seemed to go through but don't seem to have any effect. Thanks for the pointer - forgot to mention I'd already set the IPMI to optimal. Best I can see is an error during boot with ipmifan saying the motherboard isn't supported yet...

Hey, I'm having this weird annoying issue with a Supermicro X10 xeon-d board, which had the SM "cycling" thing going at default... Switched a few things around in the IPMI settings, and the board will now boot with fans at a reasonable speed, which'll ramp up to full-on after a minute or so, so I'd suspect only once Unraid loads... I mean, it's not throwing errors or anything, it's mostly that it probably makes the box noiser than it could or should be... (I've tried putting the upper thresholds to proper variants of the manufacturer's max speeds, didn't change a thing, and also tried adding the Dynamix temp/autofan plugins on top, no luck with that, can't detect the PWM controller or any other temp sensor than the CPU's coretemp) Any clue as to what I'm doing wrong ? Section 607_FAN1 ## this is the silent wings case fan ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 1600.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 1700.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 1800.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN2 ## this is a noctua 92mm ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 741_FAN3 ## this is a noctua F12 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 808_FAN4 EndSection Section 875_FANA ## this is a noctua 92mm ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection