lost all share access

***SOLVED***

In case anyone else runs into this problem, SSH into your NAS. Run the following commands.

/etc/init.d/samba stop
/etc/init.d/samba start

That command works for restarting samba on legacy NAS units.

However you can restart it from Frontview by toggling off and on the service.

However the fact you ran into this issue suggests that more issues could be at play.

Could you check your OS partition is not full by running

# df -h
# df -i

If there is plenty of free space on the 4GB OS partition could you send me your logs?: http://readynas.com/kb/faq/misc/how_do_i_send_all_logs

Thanks for your reply mdgm.

3.2GB available on the OS partition.

Logs sent.

Note, after I restarted Samba, I was then prompted to login when attempting to access shares via Windows Explorer. It didn't do that until I restarted Samba. I'm guessing this might have something to do with the fact Samba was updated in 4.2.26 to address security concerns.

From your diagnostics.log:

Disks
-------------------------------
* Disk 0 (model Seagate ST31000340NS) has 1094 reallocated sectors.  Reallocated sectors might be acceptable, but they are often the first warning sign that a disk is starting to fail.
* Disk 0 (model Seagate ST31000340NS) has 115 ATA errors.  ATA errors are logged when the disk fails to complete an internal command.  This can be a sign that the disk is starting to fail.
* Disk 1 (model Seagate ST31000340NS) has 45 reallocated sectors.  Reallocated sectors might be acceptable, but they are often the first warning sign that a disk is starting to fail.
* Disk 1 (model Seagate ST31000340NS) has 48 ATA errors.  ATA errors are logged when the disk fails to complete an internal command.  This can be a sign that the disk is starting to fail.
* Disk 4 (model Seagate ST31000340NS) has 12 ATA errors.  ATA errors are logged when the disk fails to complete an internal command.  This can be a sign that the disk is starting to fail.

So Disk 0 is bad, Disk 1 and disk 4 maybe as well. disk_smart.log has more details

(Or disk 1,2 and 5 if you count from 1-6).

Looking at status-old.log I see lots of warnings about the bad disk.

Also I see you do RAID scrubbing? How often do you do that? Note that with failing disks, the stress of a resync can finish disks off.

I see you are using X-RAID2 dual-redundancy (like RAID-6).

I am convinced that the weird behaviour of your system with samba not starting is probably related to your problem disk(s).

We generally recommend replacing disks once either the reallocated sector count or ATA error count reaches 50.

Other counts such as a non-zero Current Pending Sector count also can indicate a problem.

Do you have a backup?

Thanks for reviewing the logs. I'm replacing the disk tonight. Which actually turned into another problem. I hot swapped disk 1. It displayed "disk 1 passed" and just got stuck there. The NAS eventually shut itself down after 30 mins passed from the moment I removed the failed disk. Now I'm not sure what to do. Should I boot it back up with the new disk 1 inserted? Or should I remove it, boot, then insert it again? Or something else?

We might be okay. I removed the new disk. Booted. Then inserted the new disk and now it's resyncing.