Lost samba access to my USB NAS

[cdysthe]

[SOLVED] Lost samba access to my NAS

Hi,

I have run the latest Merlin build 374_39_0em on my RT-N66U with good results for a few days. Then suddenly this morning I could not access my NAS through Samba. On the Network map I can see the NAS is connected, but it says that I have used 0 space and there's no other info on the drive. I remounted it, then checked it but no go. Nothing shows up. But I can enable FTP and access the files. What could be wrong and could it be related to the newest firmware update?

Update: I went back to 374_38_2em and the NAS works again, so this is firwmare related. I also tried a factory reset of 374_39_0em but the NAS was still not available.

I would like to add that the NAS is formatted ext3 and has no errors after having run a full fsck. No errors on the built in disk check either.

[SOLVED] I looked at the disk layout. It had an extended partition with a large logical ext3 formatted partition taking the whole disk. I got all the data off, erased the disk and formatted it with one large primary ext3 partition (using gparted) and now 39_0_em sees the disk correctly both over the network and if hooked up with USB.

 

[sinshiva]

did you try going back to 39-em after?

 

[cdysthe]

did you try going back to 39-em after?

You mean 38_2em? Yes I did and all is back to normal. The NAS data is showing up and I can access it again over Samba. I also tried to factory reset 39_0_em without any success as far as my NAS is concerned.

 

[mtrains]

There is some instability with the USB drives in 374.39. I once had the USB drive dismount unexpectedly on me in the middle of a file copy. Happened only once. I think it is related to the Asus USB Hub implementation. But do not have enough data to prove it. My router is AC68R.

 

[cdysthe]

There is some instability with the USB drives in 374.39. I once had the USB drive dismount unexpectedly on me in the middle of a file copy. Happened only once. I think it is related to the Asus USB Hub implementation. But do not have enough data to prove it. My router is AC68R.

What is really weird is that I could access the drive from 374_39 for two days and then all of a sudden I couldn't. I can check the disk through the router, It's detected correctly as a Seagate disk, but there's no information available and I can not access it through Samba remotely. I really like the the new DNS filtering in 39 so I hope this can be sorted out soon.

 

[roldogg]

Same problem

I used to be able to access my network storage device, which is hooked directly into one of the LAN Router ports, and all the computers on my network using my Samsung Galaxy phone and tablet and one of their file manager apps. After the upgrade of the firmware, I can't connect to anything, and if I scan the network, it comes back with nothing.

 

[cdysthe]

I used to be able to access my network storage device, which is hooked directly into one of the LAN Router ports, and all the computers on my network using my Samsung Galaxy phone and tablet and one of their file manager apps. After the upgrade of the firmware, I can't connect to anything, and if I scan the network, it comes back with nothing.

Same here, but my disk is now hooked into one of the USB ports on the router. I am now on 38_2_em and everything it working normally.

 

[cdysthe]

Another update: I tried to install the latest Asus firmware and I am seeing the same problem with the NAS: It's mounted and I can tranfer files for a while, but there's no information on the drive (see screenshot) and after a while I lose connection and can't access it anymore. So this is a problem introduced in the latest firmware both from Asus and now also Merlin. My NAS is an ext3 formatted 3TB Seagate. It is probably the introduction of the USB hub stuff that messed it up. I hope it can be fixed so I'm not stuck on outdated firmware and without the new DNS filtering.

 

[L&LD]

A NAS is not attached with a USB cable.

Network Attached Storage device, means LAN connection.

 

[cdysthe]

A NAS is not attached with a USB cable.

Network Attached Storage device, means LAN connection.

Sorry, I was a bit quick. It's attached with a network cable but it can also be connected to USB. It doesn't work either way.

 

[RMerlin]

If it doesn't work either as a USB disk or as a networked NAS, then I suspect the problem is at the NAS or the client level, since these are two totally different methods of sharing. One is the router acting as a SMB server, the other is the router merely acting as a plain network switch, with no processing whatsoever.

I would also make sure you don't have a network-level issue with your Master Browser ending up on a firewalled machine. Try forcing master browser functionality on the router (USB -> Servers Center -> Misc) then reboot every devices on your network (except for the router) to make sure they properly register with the new browser master.

While USB sharing issues might be related to the firmware, network sharing is unaffected by the firmware - it's all done through a switch.

 

[roldogg]

My drive is a Seagate as well. I've been using the Seagate Desktop software on all my computers for a couple of years and it's setup the drive into 3 partitions, X, which is a publicly shared drive by all users, Y, where each computer has its own backup when you access the Y drive, and Z, which is used as an external storage drive for each computer independently (accessing the Z drive from different computers will only show the files copied to the drive from each computer independently. It's not shared like the X drive). After upgrading to the latest Merlin firmware, the drive still shows the same amount of data being used before the upgrade, but when I pull up the X drive, it shows no data even though I know it's there. When I read the changes to the latest firmware on the Asus website, they say the problems with the Seattle Go flex drives has been fixed. I really don't want to go back to the Asus firmware, but I'm afraid I might have to.

Sent from my SM-P600 using Tapatalk

 

[RMerlin]

When I read the changes to the latest firmware on the Asus website, they say the problems with the Seattle Go flex drives has been fixed. I really don't want to go back to the Asus firmware, but I'm afraid I might have to.

Asus's 374_4561 fixes are included in 374.40.

 

[roldogg]

There was a conflict between the USB flash drive I had setup to use AICloud and the ftp access to my NAS. Once I removed the USB flash drive and uninstalled the AICloud software, all the files on my NAS appeared again.

Sent from my SAMSUNG-SM-G900A using Tapatalk