greetings -

 

i have installed unraid, for testing, per instructions, gotten a reg key, and succesfully logged in thru browser.  i can't start array because of 'too many attached devices'.

 

what is the meaning of 'attached' as in attached devices.  i've seen a reference to whether a dvd drive was attached in an answer about too many attached devices, so i guess attached means attached to the motherboard (?) rather than, as would be the least obtrusive definition, attached to unraid.  is this true?

 

in other words, to use or even just test unraid i have to account for all i/o devices in my system?  how unfortunate.

 

i have 2 ssd, 2 hdd, and a dvd drive.  i only want to test unraid with the 2 hdd and when not testing to boot from one of the, not unraid attached,  ssd.  this doesn't seem possible, as with only 2 devices assigned to unraid, i get too many attached devices error.

 

is it possible to leave all my devices attached and assign only a subset to unraid, so that i may boot between multiple systems ( in my case, WIN10, Ubuntu, and Unraid testing system) and not exceed attached device limit.  if this is not the case, then that means that once unraid is installed i must use all drives and so, therefore can't have multi-Os boots.  also, why is a dvd drive even in the unraid equation.

 

thanks

Hi there,

 

Below is directly from the purchasing page

 

What are “attached devices”?

 

They refer to the total number of storage devices physically attached to the system before you start the array.  This number is in addition to your USB flash device used to boot unRAID (e.g. 4 HDDs + 2 SSDs + unRAID boot device = 6 attached devices).

What is your use case for unraid? Booting multiple OS's from the same machine doesn't really fit with any of the normal use cases, and can be dangerous to your data as any writes to unraid's array devices outside of unraid's control will invalidate parity and keep you from rebuilding a bad array drive.

 

V6.2-beta trial allows up to 6 attached devices, up from 3 devices on V6.1.

V6.2-beta trial allows up to 6 attached devices, up from 3 devices on V6.1.

from 6.2 rc1 I believe all limits are removed from the trial version.

from 6.2 rc1 I believe all limits are removed from the trial version.

 

You're right, didn't remember that.

What is your use case for unraid? Booting multiple OS's from the same machine doesn't really fit with any of the normal use cases, and can be dangerous to your data as any writes to unraid's array devices outside of unraid's control will invalidate parity and keep you from rebuilding a bad array drive.

 

thanks  for your prompt reply.

 

Long story short - I have a 'use case' that isn't normal and I'm not intending to write to unraid's array devices when I boot from another OS.

 

Two questions, then -

 

1.  Under unraid can I exclude mb attached drives from it's control?  It seems I can.

2. For testing purposes how do I get 6.2 beta with the testing reg key I already have applied?

 

btw -  high handed of unraid to base its license on number of devices attached to mb, rather than number of devices assigned to unraid.  almost guarantees people can't use the lowest level license.  that's the bean counters, not the technicians, talking.

What is your use case for unraid? Booting multiple OS's from the same machine doesn't really fit with any of the normal use cases, and can be dangerous to your data as any writes to unraid's array devices outside of unraid's control will invalidate parity and keep you from rebuilding a bad array drive.

 

thanks  for your prompt reply.

 

Long story short - I have a 'use case' that isn't normal and I'm not intending to write to unraid's array devices when I boot from another OS.

 

Two questions, then -

 

1.  Under unraid can I exclude mb attached drives from it's control?  It seems I can.

2. For testing purposes how do I get 6.2 beta with the testing reg key I already have applied?

 

btw -  high handed of unraid to base its license on number of devices attached to mb, rather than number of devices assigned to unraid.  almost guarantees people can't use the lowest level license.  that's the bean counters, not the technicians, talking.

In LTs defense on that one unraid has significantly evolved from its basic NAS functions and now incorporates VMs all of which can can numerous drives passed through to them.  Conceivably you could run a couple VMs with controllers passed through and say 20 devices attached to those controllers.  IMO I don't think it's unreasonable to have LT insist on something more than the basic license for use cases such as that.

 

Sent from my LG-D852 using Tapatalk

 

 

btw -  high handed of unraid to base its license on number of devices attached to mb, rather than number of devices assigned to unraid.  almost guarantees people can't use the lowest level license.  that's the bean counters, not the technicians, talking.

Earlier versions only counted used devices - but the limits were significantly lower.

 

Also, since unRAID is designed primarily as a server OS having unused storage devices attached is not that common.

Thanks to all who replied. 

 

Because of 'attached devices' obtrusiveness and the write cache kludge of unraid, i have decided to use ubuntu zfs striping, with a nightly syncing sweep to another NAS, and for my special use case to run win10 vm in ubuntu's qemu/kvm.

 

regards

... the write cache kludge of unraid...

Not really a kludge, just a way to get faster writing to the server while still providing some of the other benefits of unRAID, which is real-time parity and independent disks. Any design has trade-offs and whether unRAIDs trade-offs suit your purposes depends on your use.

When I hear stripe, I cringe haha. I am ok with complete losing 2 disks. I am not ok with losing ALL DATA because of losing 2 disks.

When I hear stripe, I cringe haha. I am ok with complete losing 2 disks. I am not ok with losing ALL DATA because of losing 2 disks.

Me too.  Best feature of unRAID.  I can deal with slow writes.