ksignorini

Members
  • Posts

    300
  • Joined

  • Last visited

Everything posted by ksignorini

  1. WTH was wrong with my eyes the first few times I looked? Yes, I see the link and yes, you are correct. No VT-d on this processor. I guess that answers it. Thanks!
  2. The CPU certainly does. But does the motherboard? (I did install a separate GPU as a test but still couldn't find any way to get it to not show Disabled for IOMMU. Thoughts?)
  3. The drive I'm using is really too small to be a cache drive, I think. That, and it's only 5400 rpm, I think as well. I want the app drive strictly to hold settings for my apps, e.g. my MineOS installed Minecraft server, so that it doesn't lose settings between boots. I didn't want to use a 120gb cache drive as it isn't enough for my daily transfer right now while I'm getting everything setup (multiple Mac Time Machines, some other backups, media files, etc.) which are pushing well past 120gb per day, double or so, really. Wouldn't I want a large SSD for cache? I've read comments in lots of threads about using Unassigned Devices to mount a separate drive from the array to use as appdata, but none that I can find telling me how to do it. Is this not a good way to use this little spare drive?
  4. I'm using unRAID version 6.2.4. I've mounted a new 120 GB drive (okay, it's old, actually) as /mnt/disks/Applications using the "Unassigned Devices" plugin. I've turned on sharing of the drive and adjusted its share permissions in its Settings. I now want to use that disk as my "appdata" share so I don't lose data on a reboot. This is not a cache disk. How do I do this? (BTW: I've seen lots of examples of how to use a cache disk for this but I don't have a cache disk. Mine is simply an Unassigned Devices disk.) Thanks so much!
  5. I'm seeing the same behaviour. But here's what's weird: On 4 of my 5 networked Macs, my SMB server name is in mixed cased. On 1 of the 5, it's ALL CAPS! Bizarre.
  6. I have created an SMB user share for each of my users. When I set them to Export "Yes", each user can see all of the shares when they access the server on the network (I'm using a Mac) but can only access their own share. When I set them to Export "Yes (hidden)" none of them are visible but I can connect to them using the Go to Server menu in Finder. Security is set to "Private" in each case, with only "Read/Write" granted to the user who should have access to the share. Everyone else is set to "No access". Is there any way to export the shares such that they are only hidden to other users and not the user that has permission to see the share? This is so that when they visit the server in Finder, they only see shares that are accessible to them. Thanks.
  7. Any further movement on this? I'm just setting up my Time Machine shares and chose to only allow the share to exist on one "Included disk(s)" only. I also chose the Split level as "Manual: do not automatically split directories" as an added safety measure. I set "Use cache disk" to "No". Any thoughts?
  8. This is an old thread, but in case someone is looking for the answer, I think I may have stumbled upon it. From the Guide: Fill-up: The fill-up allocation method simply attempts to fill each disk in order from the lowest numbered disk to the highest numbered disk. The fill-up allocation method must be used in conjunction with the minimum free space setting. Otherwise, unRAID will begin to give disk full errors and not allow any more transfers once the first disk gets close to being full.
  9. And a further question... I haven't installed my discrete GPU card yet--right now I'm only using the integrated graphics. Could this be why it's disabled? Think it will change if I install the graphics card? Thanks again.
  10. I have the MSI Z77A-45G ("Military Class III") motherboard. This is not the "Gaming" version. It's the "MS-7752" version. When I look at the unRAID info, I see that HVM is Enabled and IOMMU is Disabled. My understanding is that Disabled does not necessarily mean unavailable--in fact, it could mean available but turned off. But for the life of me, I can't find a setting for IOMMU or VT-d or anything like that in the firmware. I'm running an Intel® Celeron® CPU G1610 @ 2.60GHz. Can anyone tell me if IOMMU is available on this mobo? Thanks!
  11. Yeah, I never considered having data on the disks before building the array. In my case, I'm building a new array with clean disks. As long as anything I write gets protected as I write it (i.e. parity data built in real time) then I'm good. Thanks again. (Phones are not the best way to read forum posts.)
  12. I just reread. I understand. Thanks for your help!
  13. Then how is it "unprotected" during the initial sync?
  14. But will that initial data I wrote during the sync get parity data written for it afterwards?
  15. During the initial parity sync I understand that my data is not protected if I write to the array. However, if the initial sync finishes, will it then sync parity for the data I wrote while it was initially syncing? That is to say, will it get me caught up and make my data (that was written during the initial sync) safe? There is no answer to this in the manual or on the website; simply that it is unsafe during the initial sync. Thanks!