IAmNotAUser

I followed this guide exactly, and the new data disk is currently rebuilding, but is showing as accessible on the array page and the data from the disk is currently accessible. Thanks so much both of you! Is there a way of marking this as solved or anything?

I just hit this issue too - is there any chance of getting support in the popup before clearing to add custom flags for the script? Is it better a select box or a text box? A dropdown of all the different modules from the linked webpage may be one way to do it, however a free-form field to add an custom flags to the pre-clear script might be another (with a suitable warning) as a dropdown with all of the modules may be too overwhelming and looking through the list it doesn't actually reveal which option is the correct one in most cases. Additionally, a free-form field allows for any flags to be given manually to the script - saving the pop-up from becoming too unwieldy with lots of options that probably remain at "default".

Fortunately, I was just in the process of posting as the rebuild finished overnight (and, as you say, the drive is still showing as unmountable). 1. Attached is the diagnostics file taken after the second rebuild has completed. 4. I have now powered down, ejected the drive tray and restarted - after starting the array I have "Disk 4 - Not installed - Unmountable" showing on the array page and the data from the missing disk is not available in the array. So the emulated disk is unmountable too. 5. I'll start the parity rebuild using the old disk today and try again. Regarding a new config; before I start, is there anything I need to keep in mind? i.e. assigning physical disks to the same slot in unRAID etc? After the parity rebuild is complete, then I: [*]Power down [*]Eject old disk [*]Power on [*]Start array missing disk [*]Check emulated disk and ensure data is avaiable on the array [*]Stop array [*]Power down [*]Insert new disk [*]Power on [*]Start array and perform data rebuild [*]Pray disk is mountable Correct? Anything else I need to do or anything I need to do different? EDIT: Hmm, interesting. I disabled the mover script yesterday during the rebuild to ensure there wouldn't be an issue - but last night's files are on the array and nothing on the cache disk. The web interface shows the mover is disabled and you can see it in the attached syslog being commented out at Feb 26 19:41:33. EDIT 2: Have created a new config and assigned the data disks as they were before. Started the array, checked all files from the replaced disk were present and that files moved onto the array since I started were also present. Stopped the array and assigned parity. Now started a parity sync. titanium-diagnostics-20160227-0902.zip

I never saw an emulated disk (a consequence of going straight from one disk to the other, I guess) so I don't know whether that was unmountable. But the mover ran after the rebuild would have finished - which is why I think the parity drive may be out of sync and may cause an issue as this replacement is rebuilt. I guess it depends how this emulation works and whether it'll remain in place until after the disk successfully mounts. All files that were moved off the cache yesterday are playable - so they haven't been written to a null drive or anything. I've disabled the mover script now, and I'm waiting the remaining 6 hours of the rebuild to finish and will see how it goes. If it doesn't work, then I'll try John_M's method triggering a data rebuild first, and move onto johnnie.black's full parity rebuild from the old drive after. Thanks both EDIT: I've just spun up the old drive and checked its contents. The files on there are definitely not available on the current array shares - so I think it looks like emulation isn't currently in place? Will see what happens at the end of this rebuild and see if anything emulates after I power down and remove this drive, but I don't have high hopes atm.

I'm just trying to make sure we're both clear what the other side is talking about so you can reassure/belittle me appropriately and I can take the right steps to ensuring the data on all my drives is actually correct, and that parity is also correct at the end of all of this. So I had the disk connected through a USB3 external docking station (shown here) and I use X-Case 5-in-3 hotswap caddies in my Unraid server (look similar to those shown here). After the pre-clear was completed, I powered off the docking station and removed the disk from the loader. I then stopped the array and ejected the tray containing the 1TB data disk, swapped the disk and reinserted the tray. Then I refreshed the array devices, assigned the drive and restarted the array (triggering the data rebuild). So, for next time: I absolutely have to power down after the "stop the array" stage. In the current predicament at hand, my question is: do I need to stop this data rebuild, change the disks back, rebuild parity and then go through the upgrade process again? Or will the fact that it's currently rebuilding off of a parity disk that has been modified since I swapped the disk not be important going forward?

Hi John, Thanks for the reply. I think the bit you've missed is that the swap has been a data drive, not the parity drive. This is a data rebuild that is occurring, not a parity rebuild. The data on the new drive is being written to the replacement using the current parity disk state, which is why I think there may be an issue. I don't know which of your questions are still relevant in light of that, but: - The new data disk is showing as unmountable. - I did not power down the system between swapping the drives, no. However I did stop and start the array between the change. - The new disk had already been detected by the OS as sda, during the pre-clear. This appeared in the disk selection after a refresh.

Ok, so I just want to get some advice on whether I need to tear down my setup and restart, or not. I had an array that was getting low on space, so I purchased a 3TB disk to replace a 1TB currently included in the array. I ran 3 cycles of pre-clear with no issues and ran a parity check to make sure everything was in order. Once everything was completed, I stopped the array and took out the hotswap tray with the 1TB and replaced it with the pre-cleared 3TB. I refreshed the Array Devices on the web interface, replaced the 1TB with the 3TB in the dropdown and proceeded to start the array, complete with the data rebuild that it asked for. The time estimate was 7 hours, which was due to complete before my mover script triggers - so I (potentially) stupidly left it on. When I've come home today and checked on the rebuild, the disk is showing as unmountable in the GUI with 7 million writes to the disk. The cache drive is empty, but I can see last night's files on the shares. I stopped the array but the disk still shows as unmountable; in restarting the array again I've kicked off a new data rebuild. I still have the 1TB disk with all the data on, so I don't think I'm in a horrific position - but I can't help but feel this rebuild could be corrupted due to the fact that parity data has been written overnight while this new disk was showing as unmountable and since I have now kicked off a new data rebuild using the latest parity drive. Can anyone offer any thoughts on this? Or is it going to be a case of spending my weekend going back to the old drive, creating a new config, rebuilding parity and then reswapping the disk to see if it builds correctly this time? I'm happy to provide diagnostics info if anyone think it would help - but the only thing I think that would show is a potential reason for the rebuild not working, and I'm rebuilding again now anyways. Although if it fails after this run then I'll definitely be looking into it. I just don't want to risk subtly corrupting something that I may later need to rely on if/when a disk fails. Thanks

I just hit this issue too - is there any chance of getting support in the popup before clearing to add custom flags for the script?

Ok, here's an updated build using a micro-ATX board which should fit in my Antec 902 and give enough clearance to be comfortable with the X-Case caddies: PCPartPicker part list / Price breakdown by merchant / Benchmarks CPU: Intel Pentium G3420 3.2GHz Dual-Core Processor (£44.70 @ Ebuyer) Motherboard: ASRock H87M Pro4 Micro ATX LGA1150 Motherboard (£57.11 @ Amazon UK) Memory: Kingston 4GB (1 x 4GB) DDR3-1600 Memory (£27.32 @ Amazon UK) Total: £129.13 (Prices include shipping, taxes, and discounts when available.) (Generated by PCPartPicker 2014-05-28 16:03 BST+0100) Thinking I'm going to start out with the stock Intel cooler that comes with the CPU and reuse the OCZ StealthXStream 400w Silent PSU I already have. Will monitor power usage/noise and decide from there if either of those warrant an upgrade. Huge advantages of the H87M Pro is the integrated Intel NIC and second PCI-E slot. Can't see any obvious downsides with the build as it stands right now! The immediate thing that stands out is the Realtek RTL8111E NIC. While having a Realtek in my first board didn't affect me at the time I built it, it was the issues during the beta that has really turned me off it. I don't mind paying the slight premium to guarantee the Intel NIC and full support in unRAID.

Considering the number of spare drives I currently have as I've upgraded this gradually over the last 3 years - I think going to "max" capacity of the Antec is probably best way forward. I have just realised that to support that number of drives though I'm probably going to need a second SAS card, unless the board comes with 7x SATA ports. Either way, I don't think I'm going to get it on a mini-ATX. Back to the drawing board, and getting the tape measure out, I guess...

As a first update, some low-power HTPC recommendations I've seen recommend the following parts that could work for me: Intel Pentium G3420 - 3.20GHz Dual core - Socket 1150 - 3MB Cache Asus H81I-Plus - Socket 1150 - 2 x DIMM, Max. 16GB, DDR3 1600/1333/1066 MHz Non-ECC, Un-buffered Memory, Dual Channel Memory Architecture - VGA (1920x1200 @ 60Hz) / DVI with max. resolution 1920 x 1200 @ 60 Hz / HDMI with max. resolution 4096 x 2160 @ 24 Hz / 2560 x 1600 @ 60 Hz - 1 x PCIe x16 (x16 mode, yellow) - 1 x Gigabit LAN (Realtek RTL8111G) - 2 x USB 3.0 Back I/O Anyone see anything that causes an objection? I can see the Gigabit NIC is a Realtek RTL8111G - is that known to cause problems with unRAID? I'll probably put a single 4GB RAM module in, and then need to hunt for a decent low-power PSU.

Hi guys and gals, I've been running unRAID for a few years now and it's getting time where I feel I've outgrown my current build and looking to go bigger, better and badder. My current specs are as follows: Case: Fractal Designs R3 Case Motherboard: abit IP35 Pro XE CPU: Intel Core2Duo E7500 @ 2.93GHz CPU Fan: Zalman CNPS9700 Heatsink HDD1:JD Firefly PSU: OCZ StealthXStream 400w Silent RAM: 2x 2GB Non-ECC DDR2 GPU: Zotac Fanless GeForce GT220 1GB OS:unRAID Professional Other: Supermicro AOC-SASLP-MV8, 8-Port SAS/SATA Card - 2 spare on cable, SAS port free Intel PRO/1000 82541PI Gigabit Ethernet Card PCI Additionally, I have 6 HDDs in the array and 1 cache drive. The R3 is a really nice case; however I feel I'm at the maximum capacity due to the rotated lower drive bays. Not sure how much work it would be to get one of these X-Case 5-in-3 caddies in. Now, I already have the Antec 902 as this is the chassis that my current main PC is housed in. From my research, I think that I can manage to get three of the X-Case caddies in the front of the case and go from 7 mounted drives up to a potential 15! While I'm splashing the cash on the caddies and new drives, I figured I should probably replace the rest of the aging system (it was the build before, the build before from my current daily driver PC). My current biggest issues with it are twofold: - Requires a monitor to be plugged into the graphics card to boot. The motherboard does not have any integrated graphics and without the monitor plugged into the GPU the system simply refuses to POST. - It required an Intel PCI NIC card to get around the Realtek driver issues Tom had during the v5 betas. It never did get working for me again. So with all this in mind, I'm looking to buy a new Mobo, CPU and RAM. I'm in the UK and probably have about £200-250 to spend, but that is flexible to ensure a good system. My requirements pretty much are: - Should be as low-power as possible (I have a separate ESXi server for all the stuff that unRAID plugins usually provide). Maybe an Intel i3, but I'm not sure about the expenses compared against lower in the range - are the latest Haswell Pentium/Celerons really worth looking at? - Mini or Micro ATX board, as the reviews of the caddies suggest they come deep into the chassis of the Antec 1200 I saw them installed in - I don't want to risk there not being enough clearance - Integrated graphics support - Have a PCI-E 4x slot for the Supermicro AOC-SASLP-MV8 - Intel gigabit NIC, if possible to make sure that any potential driver issues are kept to a minimum in the future. - USB3 back I/O support - feel this is pretty much going to be a standard thing nowdays but still a requirement Does anyone have any good ideas?

It's going correctly between the first 2 drives, and refusing to add any to the second 2. How does changing split level change which disks are included? My understanding of how split level works should not influence which drive the data ends on, merely that all data from within a folder from that and below should not be spread across multiple drives. As an example though, my set up is similar to what is described on the FAQ as a split level of 2, which is what this share is set to. /Media/TV/ /Media/Movies/ /Media/Music

Ok, a bit of background to begin with in case this affects a step that I've missed. I originally installed unRAID 4.7 after first building my server with the intention of trying unRAID, but quickly discovered that I could not transfer the disks of data I already had onto the machine as 4.7 wasn't recognising my USB3 Icy Box caddy to mount the disks. So I upgraded straight to 5.0-beta6a and found that my USB3 PCIe card was recognised and worked. I added a few shares, including one called Media, and proceeded to move all my data onto the array. Once the transfer was complete, I added the drives originally containing the data into the server and added them to the array. If I click on the Shares page, the total available shows as the correct value I would expect, however when the mover script moves any new data off of the cache disk onto the array it only seems to move the data onto the disks first added, never the 3rd or 4th disks that were added later. The share is set up to be high-water, and it does seem to be conforming to this, but only with disks 1 and 2. When it reaches a threshold, the data is put onto the 2nd drive instead of the 1st and vice versa. My other shares are also set the same way and this is also happening to them. So, the question I'm asking is: did anything change in unRAID 5.0 that I didn't do when I added the new drives / is there a new required step from the 4.x days seeing the guide I followed was based on that? Any help you could offer would be greatly appreciated, I don't want to use up all the space on the first 2 disks before it starts using disks 3 and 4. I'm not even sure where to look to debug this, even if I am fairly knowledgeable in Linux. I've browsed the logs, and the /boot/config/shares folders, which show the same as the Shares webpage, no included drives nor excluded ones. Image showing the installed drives, note the low writes and space usage on disks 3 and 4: http://i53.tinypic.com/icv9kg.png Image showing how this share is set up, showing no excluded drives: http://i55.tinypic.com/ezk2hd.png Also, is it a intended feature that the mover script does not run on crontab after it has been run manually? I seem to be having that, and it's annoying when I copy something I'd like instantly copied into the parity array and forget to then press apply afterwards to revert it back to automatic. Thanks for your help