daggah

Members
  • Posts

    26
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

daggah's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Is there a 4.0.3 docker coming? It fixes a critical bug that wipes out entire movie libraries (ask me how I know...) Is there any contact info for the Emby guys? I've spent the last week with my entire server offline so I could restore the deleted movie library off my unRAID drives. It's been a huge PITA and I still haven't completed the restore (to see what I'm missing after all is said and done.) I think I deserve at least a year of free Premiere access for this shit.
  2. I suppose I'll probably just let it go. For what it's worth, my array up until now had drives that would never have gotten coverage because I bought most of them in Korea anyway. (I was stationed over there at the time, at a base that had known issues with mail theft on many packages, especially ones with Amazon or Newegg logos on the boxes.)
  3. It had to have been the drives I ordered from Amazon. My order says "sold by Global Silicon Electronics." The other two came directly from Newegg. Weird thing is, I thought I was ordering directly from Amazon too.
  4. That's a good catch, garycase. I wonder if there are other concerns I should have now based on this. The "My Book for Mac" harvested drives passed their preclears just fine and I now have my array built after swapping drives; just waiting on the parity check. I'm not really sure if I should take any action at this stage, other than the concern that this will possibly screw me if I need warranty coverage.
  5. Yeah, I figured that out. I was basing my estimate off the physical sector size, not the logical sector size.
  6. I don't really have any way of knowing, unfortunately. Both of my invoices just say "WD60EFRX" but don't break down the model any further than that. Anecdotal, but one Redditor said that, out of an order of eight 6TB Reds, 5 or 6 were the slightly larger model and then the rest were 68MYMN1 models. Also...is it possible/realistic to see parity sync speeds of 165-170 MB/sec? Should I be worried? I know I'd be worried if it were going too slow, but I thought 30-50MB/sec was more normal.
  7. Update: I completed the transfer from my previous disk 3 over to the drive I intended to be the parity, then did a New Config. I confirmed that unRAID will accept my newly assigned parity drive. But unRAID also decided that the new disk 3, despite having been formatted XFS prior to the file transfer, was "unrecognizable" and forced me to do a format. I have once again disabled my parity and began another transfer of my last disk5 from my old array onto the new disk 3, after which I will re-add parity and cache to the array and let it do its parity sync. Apparently one tip that I was given on Reddit is that, the next time I'm building an array, I should shave off about a GB or so off of the partition size for each disk, so that if I run into a slight mismatch like this, I have some breathing room. By my estimate, I believe the difference in disk size was about 250 MB or so.
  8. I have the unassigned devices plugin, so I have access to unassigned disks. I'm copying disk3 over now, then I'll do a new config and set it to a parity drive.
  9. The (intended) parity drive is empty, the other disks are not. I just finished transferring all of my data over to them. Is it possible to copy disk3's contents over to the empty drive and then swap the empty drive and disk3?
  10. What's the best procedure for getting unRAID to drop one of the other disks from the array? Do I use the "New Config" tool and re-arrange the last disk with the disk I was trying to use as parity?
  11. So are you saying that there are different types of WD Red 6TB drives out there, and one happens to be ever so slightly smaller? WTF Western Digital?
  12. No, I purchased all 4 drives as bare OEM drives. 2 from Amazon, 2 from Newegg. All drives passed their preclears with no issues.
  13. Adding diagnostic info to post. dg_fileserver-diagnostics-20160327-1645.zip
  14. On the drive I'm trying to use as my parity, and on the first assigned disk: READ_NATIVE_MAX_ADDRESS_EXT failed: Input/Output error On disks 2 and 3: HPA disabled
  15. I just finished migrating all my data disk by disk from my old array, which was a setup of 6 2TB drives. I'm now using 4 6TB drives. I first created a 3-disk array with no parity and copied all data over from my old disks one-by-one, using PuTTy and the cp command from a terminal. (Disks 1 and 2 were copied to new disk 1, 3 and 4 to new disk 2, 5 to new disk 3, etc.) Then I stopped the array and tried to assign the last 6TB drive as parity. I keep getting a "drive in parity slot not biggest" message in the unRAID interface and it won't let me start the array. Help? All disks are WD 6 TB Reds using the XFS file system. I am on a consumer ASRock motherboard.