NodNarb012

Members
  • Posts

    86
  • Joined

  • Last visited

Posts posted by NodNarb012

  1. 10 hours ago, SSD said:

     

    You bought a NESN with a white label drive inside? Anyone else see this? To date all NESN's have been REDS, and NEBB's, white labels.

     

    The REDs are helium filled and the label covers the entire drive front. It is decidedly more "white" than other drives. White label drives do not reference the manufacturer or any recognizable model number. They are "generic" drives and usually carry a large white sticker, although I suppose they could use any color and still be termed white label if they do not carry the manufacturer and drive model.

     

    Yes, I bought 6 NESN's and 2 of them are white label WD80EMAZ drives.  The other 4 are WD80EFAX Red drives.  Once the Reds pass a WD full drive scan and a preclear, the 2 white labels will be returned to Best Buy.

     

    Here's a chart that explains what the model numbers mean:

    4sg8kvhe1nuy.png

  2. I managed to pickup 2 of the NEBB drives yesterday for $129.99 each.  They were one of the doorbuster deals, so I think they went quickly.  I also picked up 2 of the NESN drives for $159.99 each.  I don't need all four drives, so now I have to figure out which ones to keep.  What's the deal with the 3.3v reset thing on the white labels?  Is this a problem with the shucked NESN (Reds?) drives, too?

  3. Background: I'm running 5.0.6 on a HP Microserver N54L with 8GB of memory, Hitachi 4TB NAS parity drive, and three WD 4TB Red data drives (formatted ReiserFS).  I went a little crazy around Black Friday and bought three more Hitachi 4TB NAS drives to replace my WD Reds.  After reading up on v6, I decided that I wanted to convert to XFS, so I setup the three new Hitachi drives in a spare HP Microserver N40L (4GB memory), loaded 6.1.8 with my second Plus license, and created a new array with the three drives all set as data drives, no parity.  Instead of copying the data from one server to another over the network, I shutdown my 5.0.6 server, pulled one of the data drives, added it to my 6.1.8 server as a fourth data drive, and started copying the data using the command-line at the console.  Once I have the data moved to the new XFS-formatted drives, I'm going to put the four Hitachi drives in the N54L and rebuild parity.  I'll keep the WD Red drives on hand as backups for a bit.

     

    Now, the weird thing that I noticed is in the Web GUI, the read count on the ReiserFS drive is double the write count on the XFS drive that I'm writing to.  I would expect numbers like that if unRAID was calculating parity, but I'm not running a parity drive yet.  Is this working as expected or is this a bug?

    tower-diagnostics-20160223-2046.zip

  4. I'm going to keep the v5 server with its disks until I complete the data transfer. The only disk that I plan to permanently move to the v6 server is my parity drive, which I'll do once I transfer all the data. I understand that I'll have to rebuild parity, but I'll have a copy of all of my data on my v5 server while it rebuilds on the v6 server.

  5. I'm still running 5.0.6 on my primary server and instead of upgrading it to v6, I opted to use my second unRAID license to setup a separate server running a clean install of 6.1.8. I have a couple of brand new drives in the second server formatted as XFS, but I have NOT setup a parity drive yet; I'll do that once I copy my files from my v5 server.

     

    Can I put one of my v5 data drives (ReiserFS) in my v6 server without it triggering a reformat? Will I be able to copy the data from the v5 drive to one of the v6 drives?

     

    I think I'll be able to do this, but I just want to be sure I'm not overlooking some small detail.

  6. I'm currently running unRAID 5.0.5 with six 2TB WD Green drives (1 parity, 5 data).  I have a 4TB WD Red drive that I'd like to swap in to replace the parity drive, but I also want to completely remove a drive from the array, leaving me with 1 parity drive and 4 data drives.

     

    Does anyone see a problem with me removing one data drive and replacing my parity drive at the same time?  I figure that removing the drive is going to force me to rebuild parity anyways.  I realize that my array will be unprotected during the rebuild.

     

    Steps I've already done:

    1. backed up all vital data from the entire array

    2. moved all data off the drive I want to remove from the array

    3. completed a parity check with zero errors

    4. precleared my new 4TB WD Red drive

     

    My next steps:

    1. backup my config (I also took a screenshot of my drive assignments and disabled auto start of the array)

    2. stop the array

    3. un-assign the one data drive and my parity drive

    4. shutdown the server

    5. physically remove the data drive and old parity drive, and add new parity drive

    6. power up the server

    7. reset the array config (can someone help me with the steps for doing this on v5? Do I still use the initconfig command?)

    8. assign new parity drive (and reassign remaining data drives)

    9. start the array and rebuild parity

     

    Am I missing any steps?

     

    EDIT: I found instructions on the Wiki for removing a drive

    http://lime-technology.com/wiki/index.php/FAQ#How_do_I_remove_a_hard_disk_that_I_do_not_plan_on_replacing.3F

  7. Since I didn't get a chance to test and report my findings for the new "reconstruct-writes" option ("mdcmd set md_write_method 1") under 5.0.3, I figured I should post it here now that I'm running 5.0.5.

     

    I have my Plus license maxed out with six WD 2TB Green drives (WD20EARS) connected to the onboard SATA ports on my MSI H55M-ED55 motherboard paired with an Intel Core i3-550 processor and 8GB of RAM.

     

    Testing with a 15GB MKV file I saw my writes jump from about 20-22 MB/sec to 40-45 MB/sec according to the Windows 7 Pro file copy progress window.

     

    Needless to say, I love the 2x speed increase from this option!

  8. I'm going to replace my last 2TB WD Green with this. Believe it or not, used working 2TB WD Green drives still go for $60-70 on eBay so it actually should only cost me $125 after selling the green and PayPal/eBay fees.

     

    Wow, I never would have guessed that a used 2TB WD Green would still sell for that much. Thanks for the info; I'll have some to get rid of once my 4TB Reds arrive.