August 17, 201015 yr I no longer seem to be able to access any of my shares. My Network Places sees them, but tells me that they are not accessible. The monitor I have attached to my unRaid box disgorges [pre]smbd: no process killed[/pre][pre]exportfs: Warning: /mnt/user/[user share] does not support NFS export[/pre] for each and every share. If I try to Map Network Drives using one of the shares, I get the response "The network path \\Tower\[user share] could not be found." I should also point out that I am unable to change any of the share settings. They just revert to their original selection within the drop down menu after selecting "Done." To further muddy the waters, I had to replace a drive and do a parity rebuild - which took a day - and when done, and all was green with no errors listed, I did a clean shut-down. On rebooting, the new drive showed up as blue and the system only gave me the option of doing yet another parity rebuild. I am clearly out of my depth here and could benefit from some help. Thanks in advance for any you might choose to throw my way.
August 17, 201015 yr I no longer seem to be able to access any of my shares. My Network Places sees them, but tells me that they are not accessible. The monitor I have attached to my unRaid box disgorges [pre]smbd: no process killed[/pre][pre]exportfs: Warning: /mnt/user/[user share] does not support NFS export[/pre] for each and every share. If I try to Map Network Drives using one of the shares, I get the response "The network path \\Tower\[user share] could not be found." I should also point out that I am unable to change any of the share settings. They just revert to their original selection within the drop down menu after selecting "Done." To further muddy the waters, I had to replace a drive and do a parity rebuild - which took a day - and when done, and all was green with no errors listed, I did a clean shut-down. On rebooting, the new drive showed up as blue and the system only gave me the option of doing yet another parity rebuild. I am clearly out of my depth here and could benefit from some help. Thanks in advance for any you might choose to throw my way. Step 1. Post a system log. Instructions under "troubleshooting" in the wiki. Joe L.
August 17, 201015 yr Author I'll do that. [pre]cp /var/log/syslog /boot [/pre] gives me [pre]cannot create regular file /boot/syslog': Read-only file system[/pre] [pre]cp /var/log/syslog /mnt/disk1/syslog.txt[/pre] assumes that I have access to Disk1, which I don't. Screen captures from the telnet out screen:
August 17, 201015 yr If /boot as been mounted as read-only then its file-system is corrupted. You need to move the flash drive to your PC and run "scandisk" or "chkdisk" on it. Once repaired, you can reboot your unRAID server and it will mount as read/write. Only then will you be able to perform a parity check and save the results. Until then, your array will continue to do a parity check every time you boot. Once it is writable, you can then post a syslog. Joe L.
August 17, 201015 yr Author That seems to have done the trick. I now have access to my shares again. Thanks for that. Off to bed now.
Archived
This topic is now archived and is closed to further replies.