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.

Help! The Stub received bad data

Featured Replies

On 4.5.6

 

Can't access my box on network. http://tower works find, but accessing the box via network gives by a not accessible error.  The user shares look like crap:  It contains titles and directories of all my files. 

 

Is there any way I can get my data back?

 

sever_error.jpg.f3a3d6b800c3fe69c5c9640f5b2afde3.jpg

Sorry I don't know how to solve your issue but just wanted to say the title of your post is the funniest I've ever read. LMAO!

  • 1 year later...

im getting the same error message as of a few days ago

 

i cant browse to \\tower

 

but can browse to \\tower\movies (and all other folders like this)

 

tried via to browse but still doesn't work

 

anyone find a fix for it?

  • 4 weeks later...

Same problem here. Those two links about don't help what so ever. Anyone can Google, pal. But having the correct information is the end result needed.

 

Thanks.

  • 3 weeks later...

My guess would be Windows workgroup issues.  Make sure your server and Windows computers are all on the same workgroup.  The default for unRAID, Windows Vista, and Win7 is MSHOME, and the default for WinXP is WORKGROUP.  Also try setting your unRAID server to be the local master, then reboot everything (including your router).

  • 1 year later...

I've had this happen a couple of times and I thought I'd worked out how to fix it, but can't find anything in my notes.

 

It only happens after an unRAID crash. It has nothing to do with Windows. My unRAID server crashed again yesterday and I have the same problem:

 

nl82xVb.png

 

I can access data by using \\micro\Movies or \\micro\disk1 but I can't browse the root.

 

I thought I'd fixed it by doing either a permissions run (unRAID utility) or doing a chmod on the root of /mnt/ or the root of all the /mnt/diskx/ but I just can't remember what I did. I'm running the unRAID permissions utility now, but I don't think it's going to fix it.

 

So, given that it is a problem within unRAID, unRAID support should give us a fix. Particularly if it's just a matter of typing in a simple command through telnet!  :P

  • 3 weeks later...

I've had this happen a couple of times and I thought I'd worked out how to fix it, but can't find anything in my notes.

 

It only happens after an unRAID crash. It has nothing to do with Windows. My unRAID server crashed again yesterday and I have the same problem:

 

nl82xVb.png

 

I can access data by using \\micro\Movies or \\micro\disk1 but I can't browse the root.

 

I thought I'd fixed it by doing either a permissions run (unRAID utility) or doing a chmod on the root of /mnt/ or the root of all the /mnt/diskx/ but I just can't remember what I did. I'm running the unRAID permissions utility now, but I don't think it's going to fix it.

 

So, given that it is a problem within unRAID, unRAID support should give us a fix. Particularly if it's just a matter of typing in a simple command through telnet!  :P

 

Still no solution to this.

  • 1 year later...

I'm having this problem. Started new topic but no replies. Any answer to this?

 

Joe M.

I did a little research, as this error was completely new to me, appears to be rare.  As much as I respect neilt0, this appears to always be a Windows bug, not very common but apparently possible in a number of situations and OS versions.  It occurred with WinXP SP2 with MS COM based programs (and there's a hotfix).  It occurred in Vista as a services related issue.  And it occurs with systems using AD, where login credentials were UPN based (logins with the @ symbol).  There, the workaround was to use domain\username syntax instead.  Unless that last applies to you, I don't have any other ideas, except to say if it occurs in your browser, try a different browser, and if it occurs in your file manager, try a different file manager.  (Sorry, I'm probably not going to be any help at all here.)

 

In neilt0's situation, I suspect that the Windows station was not able to handle something different when the UnRAID server came back online.  Just guessing...

The problem with this theory is that I have two Windows PCs and two unRAID servers.

 

Both Win PCs are running Win7.

 

Both unRAID servers are running the same version, although that's irrelevant, as this has remained on that one server across unRAID 5 and 6.

 

My unRAID servers are named MICRO and N36L.

 

I get the error on MICRO when I try to browse \\MICRO

 

I do not get the error when trying to browse \\N36L

 

When upgrading MICRO to 6, I started with a blank "go" file and the problem is there.

 

I can't browse MICRO from either Windows machine (I tried 3 in fact) but can browse N36L.

 

I can browse MICRO from my Android phone with ES  File Explorer. Which connects with Samba, I believe.

 

Mine is a new build that was working and now is not. I didn't have a cache drive when I first had the problem and I may not have properly cleared and formatted a new disk that I added to the array if that helps. I can access the tower from the web browser but not from the file server unless I go to a specific file (//tower/disk 1 for instance). My WD LiveTV box sees all of my files and I do think this is a Windows issue. Also, When I access tower, all of my movie files show up as well as each disk. On my other Unraid server, only the disks show up-I have to open disk one for instance to get to a movie.

 

Thanks,

 

Joe M.

It's a Windows issue but it's not Windows that's broken (per my post).

It's a Windows issue but it's not Windows that's broken (per my post).

 

I agree and was supporting what you said. I can get around the problem but would rather have it fixed to the way it was.

 

Joe

I've decided to format and reinstall the flash drive and see if that fixes the problem. Hopefully, I won't screw up the array. The problem first occurred after installing plugins which may have caused the issue. It's a very annoying problem.

 

Joe M.

That makes no difference, I've done that before.

When I click on Tower3 from my WDLive media player, Individual folders as well as each disk shows up. When I click on another server that doesn't have the problem (Tower1), only the individual disks without sub folders shows up. Maybe this is somehow related? In another thread, someone stated they made the problem go away by cleaning up the cache or temp files.

 

We can figure this out!

 

Joe

What cache?

I don’t see any mention of cache or temp files at that link?

That's worth a try.

I didn't have a cache drive when the problem first arose but now I do. I don't know how to "clean up" user shares.

I seem to have fixed the problem!

New Unraid flash drive install worked for me.

Awesome. I don't have any idea what caused the problem but hopefully it's gone now.

 

Joe M.

Interesting. I wonder if it's something in the config, the go script, or the share configuration.

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.