Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Inaccessable Shares/Transport Endpoint Proplem

Featured Replies

Hello All,

 

Well everything was going swimmingly until this morning when I got an error in SAB that one of my downloads was aborted because it could not make the final folder... I navigated to my network unsing windows explorer and could see TOWER in my network and could see all my Share Folders but when I tried to go into \\Tower\Movies or \\Tower\TV Series I got a network error stating "Windows cannot access \\Tower\TV Series" I tried to diagnose the problem but all it suggested was that I check the spelling...unfruitful. Tried to navigate to my shares from a Windows 7 termianl, Vista laptop and XP tower but still got the same "Windows cannot access \\Tower\Movies" error :-\

 

I then went into the WEBGUI just to make sure everything was okay. I can get into my simplefeatrues page and unmenu (which is good) but still couldn't get into the shared folders (not so good) When I checked the log it kept repeating the message:

 

tail -n 40 -f /var/log/syslog
Aug 27 06:25:36 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Storage Transport endpoint is not connected
Aug 27 06:25:36 Tower emhttp: get_filesystem_status: statfs: /mnt/user/TV Series Transport endpoint is not connected
Aug 27 06:25:36 Tower emhttp: get_filesystem_status: statfs: /mnt/user/appdata Transport endpoint is not connected
Aug 27 06:25:36 Tower emhttp: get_filesystem_status: statfs: /mnt/user/apps Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Anime Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Anime Movies Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Apps Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Audiobooks Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Backup Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Movies Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures Transport endpoint is not connected
Aug 27 06:25:39 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Storage Transport endpoint is not connected

 

Currently I'm at a loss of what to do...I shut down the tower before I left for work this morning and am just wondering if anybody could help me figure this out!!! Thanks for reading!!  :D

 

Currently Running: 5.0-rc12a

Simple Features, Unmenu, SAB, Sickbeard, Sickbeard Anime, & Couchpotato

Well, to completely diagnose, the gurus will require a full syslog and system configuration and etc.  BUT, this error is pretty well-known, though the actual cause is beyond me.  As I understand it, the transport endpoint happens when an out-of-memory condition or some other nastiness occurs, and the process that essentially creates the user shares is terminated.  As such, anything under /mnt/user/blah is no more.

 

RC16c was supposed to fix this problem, and it was supposed to be only happening to people running plex with large file libraries that ate up all the memory, but I don't run plex, and it happened to me right after I updated to RC16c so there you go.  Tom put a procedure in place to capture a file that would allow him to further diagnose the issue, but I haven't heard back from him, and he appears to be busy with bigger and better things.

 

The thread I started with my issue, which was in the interest of full disclosure not limited to the endpoint error, is located here: http://lime-technology.com/forum/index.php?topic=28382.msg257252#msg257252  But as you can see it was quickly drowned out.  I posted again under General Support for RCs and sent a PM, but nothing heard, so I have assumed the issue is worked or fixed or just something to live with. 

 

Bottom line, I rebooted and parity checked.  On reboot, everything looked fine, but as soon as I tried to write to the cache drive, it threw a fit.  I had to bring the array down and fsck the cache, which instructed a rebuild-tree.  This took a little time, but completed satisfactorily, I then rebooted the server again and everything came up fine.  So, depending on how things look and function on reboot will determine your next step.

 

Hope this helps, and good luck!

 

Pengrus

  • Author

Hi Guys, Thanks for the suggestions.

 

I have upgraded to 5.0-rc16c as per your suggestion and unraid loads and I can bring up Simple Features, but the problem comes in when I start the array...It will start to load in the plugins and seems to be hanging up when trying to install CP. I have tried rebooting the server several times and and everytime I try to start the array I get hung up...HELP! I don't know what to do!! :'(

 

I have attached the syslog and have a screenshot of the console when i start the array and hangs up.

 

photo.jpg

syslog-2013-09-01.zip

There's something wrong....your screenshot says Linux 3.96p but the syslog says Linux version 3.4.36-unRAID. And lower down in the syslog: 

System Management Utility version 5.0-rc12a

 

We need to focus on why there is this discrepancy.

  • Author

Sorry looks like I inadvertantly attached the syslog from this morning before the upgrade. I have attached what should be the latest syslog. I am sure that I have the 5.0-rc16c since that is what is being displayed on both unmenu and simplefeatures.

syslog-2013-09-012.zip

To me the syslog looks like something is getting in the way of your server finishing the boot process. Try Safe-Boot instead and see if there's any improvement. You won't have your plugins loading but you will see if you can get the array started and provide a more complete log.

 

 

  • Author

Okay I've rebooted unraid but dan't find and option for a safe boot. I can see start unraid OS normally, unraid with 4GB RAM limited and memtest...sorry but is there a specific command that I launch to initiate safe-boot?

There's a file you need to copy over from the distribution download to your USB key, it's SYSLINUX.CFG. It may not have been spelled out in the upgrade instructions. It's really just a text file used in the initial boot process with the Safe Boot option added. You probably have an older file on your USB key that doesn't have the Safe Boot option.

  • Author

Found the syslinux.cfg file and added it to my USB and rebooted in safe mode. The array is up and preforming a parity check but at least the array is back up. I have included the syslog when rebooted under safe-boot...just still don't know why 5.0-rc16c doesn't want to play nice with starting the array/plugins under normal boot conditions... ???

syslog-2013-09-013.zip

It is probably worth pointing out that the 5.0 final release is now out.  It might be worth moving your system to that so that you are on the same release that the majority of people will be using.

 

The 5.0 final release also includes the option to install the new experimental GUI (on the Utils tab) that is expected to supersede SimpleFeatures.

Thanks for the syslog; it's good to see you've got the basic urRAID back and your drives/data appears to be OK. From what I can see from your earlier log you run just about all the SimpleFeatures plugins plus Sabnzbd, SickBeard and CouchPotato.

 

Earlier your system failed at the CouchPotato V2 point. Searching the forums, I came up with one article: http://lime-technology.com/forum/index.php?topic=23140.0 (marked as SOLVED) which indicated their version of python-2.6.6-i486-1.txz was corrupt and manually installing it solved their problem. It was pointed out the USB stick might be a problem.

 

In another case, running out of memory was pointed to as a possible cause.

 

It seems like you'd first want to verify the state of the USB stick you're using by doing a CHKDSK on it in Windows. If you're on a Mac you might have to do some research on what tool to use.

 

Then you should troubleshoot plugins probably starting with CP. I know there's a way to disable plugins within webGUI (at least not start them). Another method is to move that particular plugin out of the plugin folder temporarily, or something like that.

 

I'd also review the state of all your other SF plugins as to current compatibility with rc16c or 5.0 final. I'm using Influencer's plugins and they're working very well!!

I don't use CP or SF so I can't help you with them very much.

 

I agree with Itimpl, now that you've got unRAID working and you're parity/disks/data looks to be in good shape, you should move to V5.0. All the best!

 

BTW, Happy Labor Day!

  • Author

Upgraded to 5.0 i386. Successful upgrade so that's good but when I started the array under normal circumstances it hung up again at the very beginning when attempting to install CP.  :-[

 

Just rebooted to 5.0 i386 safe-boot and started the parity check and all is looking good so far.

 

Then you should troubleshoot plugins probably starting with CP. I know there's a way to disable plugins within webGUI (at least not start them). Another method is to move that particular plugin out of the plugin folder temporarily, or something like that.

 

I'd also review the state of all your other SF plugins as to current compatibility with rc16c or 5.0 final. I'm using Influencer's plugins and they're working very well!!

I don't use CP or SF so I can't help you with them very muc

 

I am also using Influencer's plugins and I agree they were working well under 5.0-rc12a so that's why I don't know why they don't want to play nice under 5 i386?

 

Is there a way to disable the plugins within the webGUI under regular boot so that I can start the array/mount disks and install them again manually via the console?

 

*EDIT-I really like the new webGUI!! 9/2/13 10:25AM

So far so good! If you haven't review the status of SimpleFeatures plugins under the new webGUI, you should. From what I could tell you're running almost all of them. Development on those plugins is sort of on hold. The new webGUI is not SimpleFeatures' core.

 

It probably would be better to start a thread in Influencer's Plugin thread about your CouchPotato issue.

 

You could also test  SAB plus SIC minus COUCH and see if you get those two going.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.