March 24, 201511 yr unRAID OS Version: 6.0-beta14b Description: hotswapping internal SATA drives that are unassigned causes errors to be reported. How to reproduce: power up machine and start array with a SATA drive unassigned. Once running hot swap the unassigned drive. Now load the Main tab and on the console you will see "/dev/XXX: No such file or directory" error on console (repeating if the GUI is set to autorefresh. restart the array and drive error will be gone, as will the drive from unassigned. if you hotswap the drive back in, no errors but it never shows in gui until array restarted Expected results: No errors on hotswapping of unassigned drives and have unassigned devices section refresh on page load to only show drives in the system Actual results: see below for full description Other information: I've noticed a defect with internal drives outside the protected array. Running newest beta of unraid 6. no plugins installed for tests. I noticed a couple issues.... 1. unassigned hot swap drives added after the array has started don't show up in MAIN as an unassigned drive until the array is stopped and started again 2. unassigned hot swap drives removed after the array has stared will cause a repeating "/dev/XXX: No such file or directory" error while on the main screen (I assume it repeats every time the page refreshes automatically) 3. unassigned internal drives seem to be unnecessarily spun up by the MAIN page. I can spin them down, confirm they are spun down, but when I hit the main page they spin up again and report temp. I have confirmed this with both the onboard SATA and an add on SATA controller and it is consistently. I have a drive I hotswap in and out of the machine that will never be part of the array, so this will be an issue for me. My guess is that this behaviour is caused by the unassigned drive section of the MAIN screen, since I don't see this behavior with external drives connected, and they don't show on the screen.
April 9, 201511 yr Author No suggestions? It sounds like all I need to do is have a way to tell unraid to ignore the drive and not put it in the GUI as an unassigned drive. It appears unraid only loads the unassigned drive info at array start, so if I hot swap it out one the array started I see errors when ever accessing the main screen. But if I stop and start array, the errors go away. That or if the unraid folks put in a check to see if drive existed prior to displaying in the gui, that would resolve the issue too. My current workaround is restarting the array when I have to pull the drive but that is a major inconvenience.
April 9, 201511 yr Hey, I recently posted a possible defect on another matter. And someone was kind enough to point me in the right direction so here's me passing it on There's a better sub-forum to post them in that gets regular mod reviews. Forum Here Guidelines For Posting You've already stated you've got no plugins running but for others reading this - Check Here
April 10, 201511 yr Author Thanks for the tip, I thought I had originally posted to the defect area and it got moved? perhaps I'm wrong. Regardless, I used the template and added to my original post. Hey, I recently posted a possible defect on another matter. And someone was kind enough to point me in the right direction so here's me passing it on There's a better sub-forum to post them in that gets regular mod reviews. Forum Here Guidelines For Posting You've already stated you've got no plugins running but for others reading this - Check Here
April 16, 201511 yr FWIW I have had the same problems. I did not file a report, mostly because hotswap is not an advertised feature, and the reasons why made sense to me (the diversity of hardware makes it difficult to support). Interestingly, it worked fine on one of my controllers (I forget which one), but had dire consequences when I tried with another. YMMV.
Archived
This topic is now archived and is closed to further replies.