unable to get Samba to work for USB drive

[webintrigue]

I have attached a new 3GB Seagate USB 3.0 drive to the router and followed the steps exactly as stated in the wiki here: http://wiki.securifi.com/index.php?title=Network_storage_-_Almond%2B_2014

After having double and triple checked the settings (like only 2) I enabled the SAMBA server and clicked Save.

Now trying to map the drive doesn't work. I keep getting a constant error of the folder you entered does not appear to be valid error.
Mapping the drive I tried two ways:
1) \\ALMONDPLUS\share
2) \\10.10.10.245\share

Both fail, I even tried leaving off the \share part just in case, still no go.

I have switched the two USB ports, nothing.
I can connect the USB drive directly to my Windows 7 and I can see it just fine. For the fun of it, I even reformatted it just in case. Still no go.

The system log is filling with this report:
Feb 26 11:26:40 AlmondPlus user.notice usb-modeswitch: 2-2:1.0: Manufacturer=Seagate Product=Backup+_Desk Serial=NA7E3XYM
Feb 26 11:26:41 AlmondPlus kern.warn kernel: .Recover in TIM update
Feb 26 11:26:41 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:42 AlmondPlus kern.warn kernel: ..Recover in TIM update
Feb 26 11:26:43 AlmondPlus kern.warn kernel: .ready
Feb 26 11:26:43 AlmondPlus kern.notice kernel: sd 6:0:0:0: [sdc] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 26 11:26:43 AlmondPlus kern.notice kernel: sd 6:0:0:0: [sdc] Write Protect is off
Feb 26 11:26:43 AlmondPlus kern.debug kernel: sd 6:0:0:0: [sdc] Mode Sense: 4f 00 00 00
Feb 26 11:26:43 AlmondPlus kern.err kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 26 11:26:43 AlmondPlus kern.notice kernel: sd 6:0:0:0: [sdc] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 26 11:26:43 AlmondPlus kern.err kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 26 11:26:43 AlmondPlus kern.info kernel:  sdc: sdc1
Feb 26 11:26:43 AlmondPlus kern.notice kernel: sd 6:0:0:0: [sdc] 732566645 4096-byte logical blocks: (3.00 TB/2.72 TiB)
Feb 26 11:26:43 AlmondPlus kern.err kernel: sd 6:0:0:0: [sdc] Assuming drive cache: write through
Feb 26 11:26:43 AlmondPlus kern.notice kernel: sd 6:0:0:0: [sdc] Attached SCSI disk
Feb 26 11:26:43 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:44 AlmondPlus kern.notice kernel: ufsd: default nls iso8859-1
Feb 26 11:26:44 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:45 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:46 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:46 AlmondPlus kern.warn kernel: ufsd: sdc1 without journal
Feb 26 11:26:46 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:46 AlmondPlus daemon.notice proftpd[13326]: localhost - ProFTPD killed (signal 15)
Feb 26 11:26:46 AlmondPlus daemon.notice proftpd[13326]: localhost - ProFTPD 1.3.3 standalone mode SHUTDOWN
Feb 26 11:26:48 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:49 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:49 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:49 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:49 AlmondPlus daemon.notice proftpd[13494]: localhost - ProFTPD 1.3.3 (stable) (built Tue Aug 26 2014 15:59:38 IST) standalone mode STARTUP
Feb 26 11:26:50 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:50 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:51 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:51 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:51 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:52 AlmondPlus kern.warn kernel: Recover in TIM update
Feb 26 11:26:52 AlmondPlus user.info sysinit: ..................................................send MTORR^M
Feb 26 11:26:52 AlmondPlus kern.warn kernel: Recover in TIM update

and it just keeps going.

I understand SAMBA may be buggy, but this is really annoying. Anyone else having this issue and been able to resolve it? Even enabling the FTP and it still fails using a FTP client (Filezilla).

[Richel]

This worked for me:

http://forum.securifi.com/index.php/topic,2267.msg11823.html#msg11823

[webintrigue]

That worked, after applying a new label and directing it to that label, resolved the issue, thanks for your help Richel.

[jamenlang]

I also had problems with Samba my drive name had a space in it, after i removed it i was able to browse the contents. It might be unrelated to your issue but this worked for me.