NASLite Network Attached Storage

Ok all you NL gurus. I have a basic server set up with Disk-0 as my primary HD, and Disk-1, set as a mirror. It appears the mirror worked when I initially set it up, but hasn't updated since late April. I did set Disk-1 as RO a few days after installation because I didn't want users changing the data on Disk-1, but would that prevent the nightly mirror from running? If I have to set it back to RW, is there a way to make it "invisible" to the users when they browse the network to avoid having the mirrored data changed by someone?

One other question: when I look at the status of Disk-0 through the web interface, it shows "Not Clean". Any ideas on what to do about that.

Thanks for the help!

RO setting mounts the drive as RO so nothing can write to it including the mirror.

"Not clean" is a flag setup when the drive starts and is cleared when the drive in unmounted / NASLite stopped normally. It is used as a security flag. It DOES NOT indicate that your drive has problems.

NASLite at startup looks for the "Not clean" flag and if it finds it, it assumes that the poweroff was not correctly done and the drive(s) may be corrupt and starts a "check disk".

Regards.

I had this happen to me as well. Rebooting (tried several times) did not work. I changed the time the mirror is scheduled to happen and that fixed it.

Like Tony said, If the mirror is set to RO then nothing can write to it.

Wasn't it Peter Drucker who said that the only reason journalists called him a guru was because they couldn't spell charlatan?

Anyway, in relation to your query about preventing the mirror drive being changed, what I have done on my home network was to map Disk-0 as "Server" on the other computers that are using the network (my daughter's and my wife's) and they are content with that and in truth wouldn't know how to find Disk-1, nor even know that it's there. Of course this possibly wouldn't be sufficient if you had curious users on the network but for our needs it works rather well.

hence the need for some user level perms

User level permissions has been discussed in other threads and the reason they have not been implemented in NL. In a nut shell it has to do with the complications of getting the same permissions to work across all of the exports in a consistent manner. NASLite is really more of a SAN than a NAS. My advice is that if you feel such an compulsion to have file access controls is that you simply set up a server with a pair of NICs. The NL network is connected to one NIC with the network on the other and the server controlling the access to the shared volumes.

I for one do not want to see access controls on NL.

Mike