mikedpitt420

I use a little KVM, and I can verify that it will pass my USB to SATA adapter through to do a preclear through the unassigned devices plugin and the preclear plugin / script. It's USB 3.0 device, so it actually goes about as quick as I normally allocate for a drive to be done.

I'm having an issue trying to empty one disk to another disk. I have a disk1 which has only a few things on it. The mover has been run, so they aren't symlinks. I am trying to empty disk1 so I cna reformat it to xfs. There are currently only a few tv shows on it. When I try to highlight the media share (where all the files are on disk1) and use another disk with plenty of room in it, I get an error saying the process was interrupted, see log files. What am I doing wrong? syslog.txt

Just to document this for anyone in the future. Case migration and rearranging all of my SATA signal cables caused absolutely no issue whatsoever. Some drives were changed from being plugged into a controller card to the motherboard directly, and vive versa. The 4 port PCI SATA controller card I utilize, the Adaptec 1430SA, as well as the Iceydock 3-in-2 RAID backplane cages do report the correct drive serial #s to unRAID so they are identified. After swapping chassis / case, PSU, and completely changing almost every SATA signal connection, unRAID booted as normally expected. All dockers and VMs worked as they did before, even with an out of the array drive being managed by the Unassigned Devices Plugin. The only noticeable change was the sdX designation, which of course can change from boot to boot adding or subtracting drives. I've had a good laugh poking fun at some of my older "hardware RAID die hards" and "FreeNAS die hards" (not to down talk either of them, I just like unRAID a lot more for several of my own personal reasons) asking if their Media NAS OS of choice could tolerate the same thing With dual parity coming in 6.2, and the addition of Turbo Write, their arguments for any type of superiority are getting smaller and smaller Thanks again for all the help

Just as a response to anyone who may be wondering for the future, this plugin does indeed detect a drive swapped to another SATA port by serial number, and rearranging my SATA signal connections caused absolutely no issue with this plugin whatsoever. My system booted totally normally as if nothing was ever changed, albeit the sdX designation changed as with any boot that drives are added or subtracted. But absolutely no issues with case / chassis and SATA signal cable migration at all. The VM I had using this drive showed no change at all and everything went exactly as it should.

Thank you very much. I have posted in the Unassigned Devices plugin page to ask if this also will basically just auto detect via serial #. As it looks now from the MAIN page, all the serial #s are what I would expect to see from each manufacturer so I think they'll be fine. I failed to mention I am already using two of these same model iceydock 3-in-2 cages in my current setup, I just ordered 4 more as that's what this new chassis allows. I planned on doing a copy of /boot/config with the array stopped, and taking a screenshot of MAIN just in case I need it down the line. Is there any reason to copy the entire contents of the USB? Thanks again very much for taking the time to respond.

I am migrating my unRAID server to a new chassis, with SATA backplanes as per this thread: http://lime-technology.com/forum/index.php?topic=50806.new;topicseen#new and basically will be rearranging my SATA connections. I currently have the Unassigned Devices Plugin managing one out of the array drive which I use for storage for MythTV KVM. The ISO for this VM is stored on this HDD, the VM itself runs from my cache drive, and MythTV stores it's recordings in a share /mnt/disks/mythtv . My question is, during the process of changing around SATA connections, will this affect the drive being managed by Unassigned Devices in any way or does it like unRAID, identify devices by serial# and basically "just work" if this drive is plugged into another SATA port?

My unRAID server has outgrown the chassis it's currently occupying, and my PSU I don't think is capable of supporting a 13th drive. So I've purchased an Antec Twelve Hundred full tower with 12 front facing 5.25" drives. They are from top to bottom. I've also purchased 6 iceydock 3-in-2 SATA Backplane cages, so there will be a total of 18 front facing drives, and room for two internally mounted SSD's for a cache pool. In the process of moving all of my drives into this new case, it's going to require that I change around some of the SATA ports. What is the best process in this case? Do I just let unraid boot and think something is horribly wrong and then reassign the drives ? Would it be better to start in maintenance mode? Also, I have the Unassigned Devices Plugin managing a single out of the array drive for MythTV recordings solely, how do I reassign this without disturbing the VMs etc. Maybe I am making more of a deal out of this than I should, but I just want to make sure I don't do this incorrectly. The only real change is rearranging several of the SATA signal ports. Should I just stop the array and take a screenshot of the disk #s, then start in maintenance mode and reassign the drives? Thanks very much in advance

Doesn't work with http either from outside my LAN Also, when I load the madsonic UI from within my LAN, it defaults to using https. I can connect to my VPN and use the local LAN IP, but I'd rather to be able to not drain my phone battery with an always on VPN. When I load the UI of this docker from my LAN, it loads in https. I did not specify any extra flags or anything. But is there something I can try to see if this docker, with all the proper ports forwarded, will allow remote access? I've tried my actual IP, my DDNS address, and neither work. I can access my VPN via my DDNS address, so I know that DDNS is working. EDIT: I am now just getting a 404 not found, when using my DDNS address:4050. I can use my DDNS address to access plex via a forwarded port in this same fashion. I can accept the Self Signed Cert on my phone and connect to Plex using this certificate, but this docker will not allow remote connection no matter what I try. NMAP from another place shows ports 4050 and 4040 as both closed. They are definitely both properly forwarded to be able to be reaching this unRAID machine and this docker. I cannot reach it from outside my LAN with either http, or https.

Well unfortunately that's a deal breaker for me I'm not a huge fan of forwarding ports through my router in the 1st place, and having to leave the VPN connected all the time to do this would drain too much battery I think. So there's no way of generating a self signed certificate or something like that so at least there is SSL encryption? Do the other Madsonic (or similar) dockers also have this same issue or are there other ones that will work with https? Is there a way to specify that I do in fact want to use https? I thought I read that it was a definable environment variable somewhere, is that in fact the case?

Firstly, thanks very much for this docker. It plays everything just great and I love the interface. Although no matter what I do I can't seem to reach this from outside my LAN. I've forwarded all the ports correctly. I am able to VPN home using my noip DDNS address, and connect to plex this way as well so I know the port forwarding and DDNS are working. Is there something I'm missing? I have ports 4040 and 4050 forwarded to the unraid machine, but in Madsonic I keep getting : Status: Could not connect to https://mikedpitt420.ddns.net. (HttpHostConnectException) When I try to enter my custom URL. What am I missing?

I am rebuilding it on the same disk now, because I suppose the question would be, why wouldn't I? I have another larger, already pre-cleared disk just waiting to drop into my array so I'm going to give it a shot and if it fails then I'll rebuild to the new one. I did do a long SMART test and it's passed, no reallocated sectors, although it's "old age" and "pre-fail" are almost always present in consumer level drive SMART tests, I hope it will be alright. I believe in this case I simply need a larger PSU

I added my 12th drive to my unraid array a few days ago. As it began to pre-clear another fairly newer drive, showed a red ball, failing, contents emulated. When I clicked on the drive itself, it was being reported as a size of 600 Pedabytes or some crazy high number. I suspected it may be a failing of the PSU to keep all the drives powered, so I allowed it to finish the pre-clear, stopped the array, powered down the machine, checked all my SATA and power connections, removed the new pre-cleared drive, and powered back up the machine. I got an email saying : Event: unRAID array errors Subject: Notice [TOWER] - array turned good Description: Array has 0 disks with read errors Importance: normal But I still have a red X next to the drive, even though now when I click into the drive, the size is reported properly and the SMART status reports as "passed". I think the drive is fine, but unraid refuses to see this drive as such. How should I proceed? I have another larger, already pre-cleared drive, but I don't think the problem is the drive, as much as the PSU wasn't giving sufficient power to the array in general.

An unRAID user friend of mine using unRAID 6.1.9 and the newest version of this plugin reported something to me and I was curious if it was possibly a bug? Being a new unRAID user, he had already tried to create his array without preclearing drives. I advised him to install the script and this plugin, and do the pre-clear. Unbeknownst to me, he had tried to perform a pre-clear on a drive already in an array. After several hours of being stuck at "Starting" from the status screen he checked the log to see the command invoked, and the response from unRAID saying it would not perform the pre-clear as the drive was already in the array. Is there a reason that the plugin itself doesn't try to stop or warn you when trying to pre-clear a currently in the array drive? I definitely appreciate that it stops it from happening as you'd lose all your data, but should there not be a warning letting a user know this is not a preferred method or that the command was not completed instead of it just sticking endlessly at "started" ?

I can definitely configure the new MAC the new KVM takes on my router end with DCHP. I honestly (obviously) didn't know the answer It is working great. I've been able to assign it a static LAN IP based on the MAC in the KVM settings. Thanks for setting me straight. Apologies for such a n00b question

I understand this. My mythbuntu instance uses br0 as it's network interface. If I wanted to create a 2nd VM, would I not need a br1 interface with it's own MAC and IP address? Excuse me if I'm missing something simple.

I would also love to see support for multiple virtual bridge adapters added to the GUI. I use the one I can create in the GUI for a Mythbuntu KVM which has been running very smoothly. I'd love to see the ability to create several. I'd like a small footprint ubuntu VM I could spin up every once in a while that has it's own IP address on my LAN. Is this possible through the GUI now or does it still require editing xml files?

Thank you very much sir for fixing the drive spin up issue. unRAID now has a warm spare option you rock!

Is it possible and either advantageous or negative to use par2 multicore inside of a docker container? Will it indeed use multiple cores and speed up the par process?

That's all I needed thanks very much sir. And in no way am I trying to downgrade any pro-bono or otherwise work you're doing. I posted this a while back, waited quite some time, and got no response. Another person also posted with this issue, and got the same. All I was looking for was acknowledging that it was in fact an issue that will be looked at in whatever amount of time you see fit. Thanks again, very much.

So I guess this plugin will just keep spinning up every drive it manages that isn't mounted ? Sorry, but I've posted more than once now and just keep getting ignored every time. Either this is indeed a bug or it's intended behavior and does in fact spin up every drive it manages for some reason. It would be great to even know what that reason is, so I can possibly find some other way of keeping a warm spare.

If that was corrected then unRAID would finally indeed have a viable "warm spare" option. I don't know how many users would like this as I would. But anyone with a remote system they can't get to ASAP I'm sure would appreciate being able to initiate a drive rebuild immediately instead of having to wait for a drive to pre-clear. Or having to physically install an already pre-cleared drive. If there is in fact some reason that this plugin needs to spin up drives and this is expected behavior, then would it be possible to designate one (or more) drives as a "warm spare" ? A drive that would remain undisturbed and not spun up until this status was removed or something along those lines?

The "MAIN" page is the MAIN tab in unRAID's UI that shows all of your drives in a list. When the page is loaded in a browser window, all drive info except under the Unassigned Devices section comes up immediately. A small spinning icon appears under the unassigned devices tab while it proceeds to spin up all devices that are not currently mounted or in use by something else. Then when the drive statistics for the unassigned devices do appear, all drives are green and spun up with temperatures reported. So, if you have a formatted, pre-cleared, and unused device, every time the "MAIN" tab in unraid's UI is loaded, any drive under the unassigned devices section spins up. I tried to keep a warm spare this way, and found I could not as it spun up constantly instead of staying spun down and pre-cleared until it needed assigned to the array. It is the same issue as described here: http://lime-technology.com/forum/index.php?topic=38635.msg426749;topicseen#msg426749 and here: http://lime-technology.com/forum/index.php?topic=38635.msg416013;topicseen#msg416013 The drives being managed by the Unassigned Devices plugin do in fact spindown after whatever the set time is. However, they spin up again every time the MAIN tab is pressed and the drives are listed. Unlike the array devices, which remain spun down (if not in use) and do not report temperature.

I have the same issue as HTPC newbie mentioned several pages back which still hasn't gone away. Every time I load the MAIN page, the Unassigned devices plugin spins up all the drives it is handling. Would love to see a fix to this as I tried to keep a warm spare and was unable to as it spun up every time I loaded stats.

So it is in fact the case with this new version that it has PermitRootLogin set to no? I would be able to just change it in the sshd config file and it would revert back again right?

Bump. I think it sure would be awesome to see this incorporated into unRAID as a plugin or built into the WubUI. Even a script that could perform this would be great. Is there a way to temporarily disable spindown and re-enable it from the CLIU making a script for this relatively easy? Due to the difference in SMART report information from manufacturer to manufacturer, I imagine parsing these results in a meaningful way would possibly prove difficult. But even just having the results emailed to you monthly or in a log file would indeed be a great and welcome addition to most I'm sure. Who has a NAS that doesn't want as much possible information about their drive health as possible?