Firstly, Let me say this forum has help me so much, Keep up with all great support.

 

So on to my issue.  I had an issues with some drives which I replaced with larger one, I even upgraded my parity drive. After all the rebuild and re-syncs where completed I notice I was unable to smb or afp into the shares. The share folders were not visible within unraid either, but when I explore the disks the folders are there and shares are listed in the config folder of the flash drive. I even did an upgrade from 6.1.5 to 6.3.5, remove the VMs and Dockers but still no luck on getting the shares to appear. I can see the disk but not the shares, Hope the screenshots help.

 

Appreciate any help with this

I had the same issue a couple of days ago. Are you using uBlock Origin by any chance?

 

Something under share was apparently blocked. Whitelist your unraid server, and it is fixed 

 

Didnt get if you could see the share in windows? If not, your problem is probably something else

I did see someone who suggested that. It didn't show up on any browsers with no extensions.

Please post your diagnostics: Tools -> Diagnostics

Here you go. The Diagnostic

avalon-diagnostics-20180111-1702.zip

Filesystem corruption on disk1 (md1), run xfs_repair:

 

http://lime-technology.com/wiki/index.php/Check_Disk_Filesystems#Drives_formatted_with_XFS

 

P.S. lots of ATA errors on ATA8, just a few from the log:

 

Jan 11 05:33:01 Avalon kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 11 05:33:01 Avalon kernel: ata8.00: irq_stat 0x40000001
Jan 11 05:33:01 Avalon kernel: ata8.00: failed command: READ DMA
Jan 11 05:33:01 Avalon kernel: ata8.00: cmd c8/00:04:84:70:7b/00:00:00:00:00/e0 tag 16 dma 2048 in
Jan 11 05:33:01 Avalon kernel:         res 51/04:04:84:70:7b/00:00:00:00:00/e0 Emask 0x1 (device error)
Jan 11 05:33:01 Avalon kernel: ata8.00: status: { DRDY ERR }
Jan 11 05:33:01 Avalon kernel: ata8.00: error: { ABRT }
Jan 11 05:33:01 Avalon kernel: ata8.00: configured for UDMA/133 (device error ignored)
Jan 11 05:33:01 Avalon kernel: ata8: EH complete
Jan 11 05:33:01 Avalon kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 11 05:33:01 Avalon kernel: ata8.00: irq_stat 0x40000001
Jan 11 05:33:01 Avalon kernel: ata8.00: failed command: READ DMA
Jan 11 05:33:01 Avalon kernel: ata8.00: cmd c8/00:04:84:70:7b/00:00:00:00:00/e0 tag 19 dma 2048 in
Jan 11 05:33:01 Avalon kernel:         res 51/04:04:84:70:7b/00:00:00:00:00/e0 Emask 0x1 (device error)
Jan 11 05:33:01 Avalon kernel: ata8.00: status: { DRDY ERR }
Jan 11 05:33:01 Avalon kernel: ata8.00: error: { ABRT }
Jan 11 05:33:01 Avalon kernel: ata8.00: configured for UDMA/133 (device error ignored)
Jan 11 05:33:01 Avalon kernel: ata8: EH complete
Jan 11 05:33:01 Avalon kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Jan 11 05:33:01 Avalon kernel: ata8.00: irq_stat 0x40000001
Jan 11 05:33:01 Avalon kernel: ata8.00: failed command: READ DMA
Jan 11 05:33:01 Avalon kernel: ata8.00: cmd c8/00:04:84:70:7b/00:00:00:00:00/e0 tag 4 dma 2048 in
Jan 11 05:33:01 Avalon kernel:         res 51/04:04:84:70:7b/00:00:00:00:00/e0 Emask 0x1 (device error)
Jan 11 05:33:01 Avalon kernel: ata8.00: status: { DRDY ERR }
Jan 11 05:33:01 Avalon kernel: ata8.00: error: { ABRT }
Jan 11 05:33:01 Avalon kernel: ata8.00: configured for UDMA/133 (device error ignored)

ATA8 is this, check cables:

Jan 11 05:32:49 Avalon kernel: ata8.00: ATA-8: ST3000VN000,             W7306HMD, SC60, max UDMA/133

 

thanks, I will run a Filestem check for disk 1 right away

 

The ata8.00: ATA-8: ST3000VN000 is an unassigned device not apart of the raid I will remove it from the system when I get in from work

It is all good now. 

 

Nothing changed after I ran the filesystem check but I did a full reboot and my shares popped up again. Thanks for the great help. Love this community.