December 5, 201510 yr When I attempt to create a cache only share unraid pops a message saying the share has been deleted. Creating a non-cache only drive works fine. Unraid 6.q.6 pro key 2 1TB drives + 256G SSD for cache. I've setup two other servers and I'm never had this type of issue. Any ideas?
December 5, 201510 yr When I attempt to create a cache only share unraid pops a message saying the share has been deleted. Creating a non-cache only drive works fine. Unraid 6.q.6 pro key 2 1TB drives + 256G SSD for cache. I've setup two other servers and I'm never had this type of issue. Any ideas? I just tried it and it works fine for me. Maybe post your diagnostics
December 5, 201510 yr Dec 4 20:18:20 Tower logger: mount: warning: /mnt/cache seems to be mounted read-only. You going to have to stop the array, then restart it in maintenance mode and check the file system on the cache drive
December 5, 201510 yr Author The drive was originally formatted ntfs which was the issue. I took it out and plugged it into my pc and confirmed I could write to it. I then destroyed the primary partition and added it back to the Unraid server. Now everything works. A more descriptive error or warning when adding an ntfs cache drive would be nice. Thanks for the help.
December 5, 201510 yr The drive was originally formatted ntfs which was the issue. I took it out and plugged it into my pc and confirmed I could write to it. I then destroyed the primary partition and added it back to the Unraid server. Now everything works. A more descriptive error or warning when adding an ntfs cache drive would be nice. Thanks for the help. I don't think you can blame unRaid for that, as an NTFS drive operating as part of the managed disks (array / cache) is a completely unsupported configuration.
December 5, 201510 yr Author I wasn't blaming, just pointing out that a message that says the drive is mounted read only would be better than "share XXXXX is deleted" would help. Also, if ntfs isn't supported for the cache drive why did it allow it without notifying me. The drive was new to me and I wasn't even aware it was formatted ntfs. Raising clear errors make supporting a product easier for both the developer and user. Thanks again for the help. I wouldn't have seen the issue without it.
December 5, 201510 yr I wasn't blaming, just pointing out that a message that says the drive is mounted read only would be better than "share XXXXX is deleted" would help. Also, if ntfs isn't supported for the cache drive why did it allow it without notifying me. The drive was new to me and I wasn't even aware it was formatted ntfs. Raising clear errors make supporting a product easier for both the developer and user. Thanks again for the help. I wouldn't have seen the issue without it. You probably have the unassigned devices plugin installed, which adds NTFS support. Supposed to be for access to NTFS drives outside the array, but looks like it will also allow you to add it as a cache drive. Not necessarily an issue by itself, but it definitely is an unsupported configuration. And, in re-reading, you are correct that something a little more descriptive should have been present. My apologies.
Archived
This topic is now archived and is closed to further replies.