• Content count

  • Joined

  • Last visited

  • Days Won


SSD last won the day on November 7

SSD had the most liked content!

Community Reputation

206 Very Good

1 Follower

About SSD

  • Rank
    unRAID Revolutionary


  • Gender
  • Location
  • Personal Text
    ASRock E3C224-4L/A+, SM C2SEE/B, Asus P5B VM DO/C
  1. Best 8TB Parity Drive?

    What do you mean won't be read by the "WD system"? Were you trying to remove the drive from the MyBook external and replace with the HGST? HGST drives should work just fine in an unRaid server.
  2. How to add existing data drive to new server

    UnRaid is very particular about how it partitions ahs formats array disks. So no, you would not be able to add your existing disk as an array disk. You could configure your array with no parity, then copy the data over from your existing disk to the array, then do a new config adding the parity and the 3TB drives to the config. Take a look at this thread, Technique will be similar. Review and reach out with any questions.
  3. These are optimized instructions. Nothing can be faster than copying data within the server without parity overhead. Copy would go fastest if you delay adding parity OR almost as fast if you use reconstruct write mode. Since you are taking far more drives out, you'll be able to mount and copy from all but one of the disks (one at a time) before having to shut down and add the final disk and copy it over. There are multiple ways. Midnight Commander (command line but not sure if screen or console is required), cp (using command line) inside "screen" / console, or Crusader docker - there is a video on how to configure it. Personally I use cp with -rpv options inside a "screen" session. (Screen it's installable via the nerdpack plugin). You could also copy using Windows over the network. This would be decidedly slower. If you have a Windows VM on the server, you could copy using that nearly as fast as copying via Linux on the server. Not sure about preclearing inside USB. You might have issues getting smart data, so you'd be unaware if the drive had issues. You could also have issues with the geometry of the drive changing and the disk not recognizing the preclear signature. But since you are rebuilding parity, this won't matter. Is there an another machine you could use for a day or 2 to do the preclear. It will not touch your other drives unless you try to add them to an array, preclear them, or write to them some other way. It's very easy to just preclear the disk you want and boot the machine back into Windows or whatever when you are done. Some controllers need to be flashed with IT mode firmware. I believe the perc would require this. Can't help as I have no experience with that card. I like the LSI SAS9201-8i as flashing is not needed. Good luck!
  4. Your request is similar to the post I made recently. Have a loo and if you have questions on how to adapt this to your requirement, let me know.
  5. CPU & Motherboard for new build

    We may be on the verge of greatness with the Ryzen / TR platform. Firmware updates are rolling out that show promise for resolving a lockup issue related to c-states. recently posted a video of getting it setup with passthrough. Certainly Intel is the low risk option, but a short wait before a major purchase might be in order.

    You are smart to incorporate drive cages to make swapping disks easier, but even more importantly, safer. Have to agree with @BRiT about using larger drives though. Simpler config and 8T drive prices have recently been very economic. But ultimately depends on your array growth rate, and certainly nothing wrong with using the 1T drives. It does reduce the amount of potential data loss should multiple drives fail simultaneously. And the cost of parity can be substantially less with a smaller parity drive. If you said you were hard wiring each drive I'd be more concerned with the higher drive count, because with each drive you add you increase the chance of a cabling issue (the greatest risk to unRaid servers), but with hot-swap style cages, after initial burn in, those risks are quite minimal. Enjoy your array!
  7. @bombz - You will need to do a new config to remove the old drives and add the new one. Don't delete the data from the 2 500G drives, and you'll have a backup just in case you have any issues with the external. I do recommend a preclear to test out any new drive, but technically you would not need to preclear it. When you did a new config, parity is rebuilt. What you could do is this. It's what I would do. You don't need the external. Preclear the new 4T drive and second parity disk (if you have). (Recommended but not mandatory) Shutdown server. Remove one of your 2 500G drives from the server, and add your 4T drive. Boot server. Do a new config but keep configuration. Add the 4T add as a data drive and omit the 2 500G drives from the array configuration. (I'd also omit parity, but that's up to you. Without parity you'll be able to copy faster). Change filesystem to xfs on the new 4T drive before starting array. Start the array. (Let parity build if you added parity.) Format the 4T drive. Use unassigned devices and mount the 500G drive. Copy all the data from the 500G drive to the 4T. After the copy, shutdown the server. Swap the 500G with the other one. Boot the server, start a array, use UD to mount the other 500G, and copy other 500G drive to the 4T. Shutdown the server again. Remove the second 500G. I think you said you wanted to add second parity drive. This would be the time. Otherwise just leave slot empty. Boot the server. Before starting the array, add your parity disk to the config (if didn't do before), and your second parity if you are adding it now. Start the array and parity(ies) will build if you added.
  8. @bombz - So it sounds like you are completely full in terms of drive slots. So you want to copy data from 2 500G drives to an external drives, and then add a 4T disk that you'll format as xfs. This sounds like a reasonable approach. It will require rebuilding parity to remove the 500G disks and incorporate the new 4T disk containing data. Swapping add-on controllers is seamless. UnRaid recognizes drives by serial number. So if you remove the old, attach the drives to the new, and boot, all the drives will be assigned to their proper slots as though nothing had changed. (Obviously connecting everything securely and not disturbing the drive cabling of other drives is critical to not causing drives to drop offline). Related to ports to avoid I am confused. The SuperMicro add on controllers that use the Marvell chipset are problematic, but motherboard ports that are provided from the Intel chipset or non-Marvell chipsets are fine to use. Your post made it sound like you were trying to avoid using regular motherboard ports but maybe I misunderstood. I do suggest planning for an empty slot as it is useful in some recovery scenarios. And comes in handy for preclears as well. It is also needed to convert from rfs to xfs.
  9. AMD Ryzen update

    Tom - I haven't kept up that well with the Ryzen / TR saga, but recall there were two issues - C states and the NPT. I thought there was a fix / work around for both, but then there a second C state / stability issue. Do you believe that this low power C states issue COULD be the "3rd one's the charm" final fix to make the platform stable? Or are there another symptoms (e.g., with pass through) that aren't consistent with this problem?
  10. You sure it is the drive and not something about how it it's mounted? Or a fan? Is it noisier when being accessed? When spinning? Any noise when spun down?
  11. Without the two parity disks, you'd have had to use the two disk 'as is'. Any recently added content added you either would have been lost. Since neither disk actually failed, the loss would have been only recently added. The key concept about parity is that it can be completely fubar and there would be no visible signs. Only a parity check would tell. Now unRaid does an excellent job of maintaining parity, but there are several ways it can get screwed up. And if one gets screwed up, so does the other. And it's normally not subtle when it happens. Compare with raid which stripes data. It has options in terms of how it reads the data (whichever it can do faster). It does integrity checks. Once any sort of out of sync condition is detected, the array is invalidated. So unlike unRaid, no way it can be corrupt if it's working. I'd check the disk to make sure the directory shows up. And I'd check a few files, including older and newer content. Checking md5s on then if I had them, or playing the media (Quickly skipping through). I'd also copy off any content that I was particularly concerned about - like the 2000 pictures you recently copied of your wife's cell phone that you'd be shot if got lost!
  12. First should have checked emulated disks looked good. No extra disks needed. We had a rebuild complete about a month ago, but content was garbage. Rebuilt over the disk that was kicked (that would have been virtually perfect). I know it's expeditious, but I really dislike the rebuild over the kicked disk concept. Could have done with 2 extra disks. Or could have rebuilt one at a time and done with one extra disk. Always good to have at least one disk in the wings. If you have backups, none of this would matter as your data is protected.
  13. Onboard SATA or 6GB/s LSI board?

    Getting back to your initial question about best controller for drives, thought I would try to address. First, if your motherboard or add-on controller use Marvel chipsets, disable that controller in BIOS for motherboard controller (if possible) / remove the HBA. Don't risk using them. Generally speaking, normal motherboard (chipset provided) sata ports are the best. Only situation I'd advise using something else first is if they are not fast enough for an SSD (old motherboard). They tend to be the fastest, least problematic ports. With add on controllers, there are a lot of variables. 1. Some (especially prior generation ones) don't support trim, which is important for SSDs. LSI SAS9201s have this issue for example. Work great for spinners, but use MB or newer controller for SSDs. 2. Sata spec / single port performance needs to be fast enough. Not a problem for spinners with sata2+. SSDs need sata 3. 3. Bandwidth constraint. This it's a tricky one as it involves the PCIe version number (1.x, 2.x, 3.x) of the HBA and slot (slowest rules), the usable (electronic) slot width (x1, x4, x8, x16), and the number of drives that will be in simultaneous use. Remember PCIe 2.0 at x4 would support 8 spinners almost exactly. 4. Other conflicts. As Johnnie mentioned, with shared DMI and resources. I would not know how to calculate, but if you are running close to maxing out, could come into play. Benchmarking might be only way to determine how these shared resources would impact performance. In your case, the new LSI controllers are excellent. Doubt you'd have any performance bottlenecks with spinners, but might have bandwidth constraints with several SSDs depending on the slot / drives in parallel use. But I'd still favor the motherboard slots.
  14. Before a rebuild, I always recommend looking at the simulated disk(s) to make sure everything looks ok. Although the two disks dropped offline, their data is likely intact (except for recently added files since they dropped offline). And if rebuilding onto different disks, these original disks would act as a decent backup to protect against a bad rebuild. Your chances of a problem are pretty low, but thought I'd mention for other readers and for the future. Rebuilding 2 disks leaves you unprotected during a whole dual operation, so you are dropping your pants completely when you didn't have to. Btw, perfectly good drives that drop offline are often caused by bad or lose cabling.
  15. Didn't mention easier, but the monoprice cables linked above support 4K video at 60 Hz. If looking extenders or other cables, confirm you are getting 4k capability if this is important to you now or within a reasonable timeframe.

Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.