• Posts

  • Joined

  • Last visited

DougCube's Achievements


Newbie (1/14)



  1. While the server is up (for days), suddenly the cache drive disappears from the UI. But in the command line, the mount is still accessible, accessing files that I know are on the cache drive via SMB share still works, and running the Mover works fine. Both reads and writes to it seem to work fine. The drive does not appear in the Unassigned Devices section. I did not find anything relevant in the syslogs. I've seen this happen twice now. Rebooting the server fixes it but I'd like to prevent it from happening again. I suspect it may be happening when I update the Unassigned Devices plugin, but I can't be sure. Anyone else see this issue before? Any ideas what's going on here, or how to fix it?
  2. Sounds like something went wrong with the preclear. Clicking the X should have no impact. Once the preclear is done, even before the post-read, there would be a signature written to the drive that Unraid picks up on when you later add it to the array so that it doesn't have to clear it again. I've never heard of this happening.
  3. I am somewhat familiar with the Notify command, but how do I trigger one once Mover is done? Essentially, I'm looking for a way to have a script detect if the Mover is finished running. Or even better, have it trigger automatically each time. Speaking of which, wouldn't it have made sense for this feature to be built-in to Unraid?
  4. Oh, good to know. I struck-out the incorrect info from my reply. Thanks. I might actually use this 'feature' going forward then. I just have a slight preference to group up drives of the same capacity and manufacturer.
  5. The way the OP is worded makes me want to clarify that you can't have gaps in your array slot assignments. And yes, what you describe is considered "reordering" from the UnraidOS point of view (especially w.r.t. the parity2 calculation). And like others have said, the physical configuration doesn't matter at all -- you can change where a drive is physically mounted or which SATA/SAS cables/ports to use between boots and the OS will easily cope with it. (Although I wouldn't switch an array drive from being internally mounted to being in an external USB enclosure.) I used to be overly concerned with the ordering of the drives, but I eventually found that it's best to live with leaving the order alone. Although... I have requested a feature to be able to assign nicknames to the drives to make it easier to manage. But if you do choose to reorder, keep in mind that the 'included/excluded' drive selections in the shares do not automatically update to track the change -- you'll have to update those manually.
  6. There is no limit on number of cache pools. Personally, I would go for the Pro license for future expandability, but I kept adding drives every few days until I hit 18 devices before my first trial key even expired. Currently, there can only be one 'Array' pool. Which conventional wisdom suggests should be all your HDDs together. In your case, the four large drives would be the 'Array' and you can use two of the SSDs to make a single btrfs RAID1 cache pool -- making it so you have redundancy as soon as the data writes to your cache. You can use remaining drives to make more cache pools, or be dedicated for VMs. And if you have even more SSDs to spare you could put them on the data array (a bit of a waste putting SSDs on the array IMO). Four HDDs is really just a start since you'll probably want to have one parity drive, which takes up nearly 25% of it. This sort of RAID5-ish setup is better suited for having more drives.
  7. There seems to be a bug or oversight where hot-plugged drives do not give a preclear icon/option in the MAIN tab but it is still possible to run it from the TOOLS tab. (I tried obvious things like refreshing the page.) Please fix. Regarding the issue of this plugin disappearing after a reboot... After I updated to latest version to fix this very issue, I still needed to reinstall the plugin after a reboot -- at least twice more. (I should send you a diagnostics file again.)
  8. To be clear, if I have a trial key that had expired 15 days ago, does getting a 15-day extension make any difference?
  9. Does the 15-day extension start when the 30-day trial ends OR when you start the 15-day trial? (There's a subtle difference between the two.)
  10. This question has been asked here many times. It can be done on a separate machine.
  11. I was wrong earlier. But I meant not including parity, pool, boot, or unassigned. It is 28 right?
  12. Other than the obvious (not being able to start the array), what features are blocked out when the trial key expires? I'm thinking of having a second Unraid machine that is dedicated to only running preclears, and prefer not to have to purchase another license for it. How about VMs? Does that feature work with expired trial key? I'm guessing dockers wouldn't work because they always need the array? Or can dockers be run from an unassigned device? And could you still do a disk share (SMB) of an unassigned device? I searched around and was unable to figure this stuff out -- or at least not explicitly spelled out anywhere.
  13. Currently, if a share has "Included Disk(s)" or "Excluded Disk(s)" and you reorder the Disk slots, the selection for the shares are not updated accordingly. I sighted this in 6.9.0-beta30 but it's likely always been this way. What would be nice is if it did automatically update it for you. Even better is having a "reordering wizard", a "replace parity drive wizard", etc..
  14. In "Array Devices" section the disk names are currently quite verbose "(<model number>_<serial number> - <size> (sb<letter>)". This is for the most part fine, but I would prefer to omit <size> since there is already a column showing it. The ability to rearrange and hide columns here would be nice too. I would also prefer to omit the <model number>. But even better might be to allow specifying your own identifier/nickname. And on top of that to give some formatting string, like "%nickname_%model_%serial (%sb)" -- you know, like printf().