hi all

 

had a power outage last week and seems like the USB corrupted. rebuilt the USB and now curing recovery of the server I'm encountering one thing after another. Current issue, potentially one of the last:

 

I can see my shares on the system but with all the SMB settings turned on they won't show on my machine when I connect. 

 

 

here you see my flash I've made public jus to see something and the other shares in the background that are all there and visible. 

 

I can telnet to these shares on the machine:

e.g.

 

so the content definitely there and viewable just not sure why windows won't connect.

 

another symptom, potentially unrelated but in case it is related:

 

some of my docker containers work without issue

immich, PostgreSQL and cloudflare but the other images e.g. plex won't start and show 'bad parameter' 

 

at a guess this is because the config for appdata is on the cache and it can't see it for some reason. other docker images like sonarr have the head challenged auth issue which I need to reset but can't until I can get to the file drive (could probably do it on SSH but i haven't done that before only done it via smb update the txt file directly).

 

one other note:

when I rebuilt parity my second disk had an error and disconnected, not sure why will look into it, just going to new config it potentially but it's there as an issue either way after the outage

 

 

 

so if any one has any ideas, I'm looking to understand where should I debug next. are there some other settings I can configure and try out maybe see if that 'resets' the smb function or an alt way of connecting to the machine maybe. just a little stuck where to go next.

 

thanks

 

SMB settings

 

 

 

Regarding the shares first, are you exporting them? The screenshot you posted has that info covered, post a new one showing the full shares page.

1 hour ago, JorgeB said:

Regarding the shares first, are you exporting them? The screenshot you posted has that info covered, post a new one showing the full shares page.

Hi Jorge, 

 

Not sure what you mean by exporting them. That screenshot is the full shares page. here's a new image of the shares page zoomed out slightly to show nothing else on the same page

 

unless, apologies do you want this page e.g. the details of the share (this one is appdata when i click on it)

 

If you look in the SMB Security Settings you seem to have Export set to No.    this means the share is not set to be visible on the network.

This part here shows that none of the shares are being exported, since some time ago, they are not exported by default, so you just need to toggle export to yes, for the shares you want to access over SMB only:

 

ok thank you @JorgeB and @itimpi

 

the SMB issue I see now is fixed. ei totally missed the export option I thought that meant something else, not sure why. I can now see exported shares over SMB.

 

I still have an issue with plex launching though i suspect it won't only be plex having the issue its just the one I'm looking at. 

 

I tried updating it and it says 

 

I want to look at the settings and see if there's maybe a conflicting port, transcode option or GPU detail to look at but i can't get to the edit image details in the docker tab, it doesn't show for some reason. most interestingly I tried looking at the apps in the community applications centre but it says i have no matching applications found

 

 

 

interestingly I know immich is working and cloudflare as i can get to the served port on open internet so they work alright but they're not showing in comm manager. 

any ideas on this?

26 minutes ago, alcxander said:

I tried updating it and it says 

This means it's missing the user-template, do you have a flash drive backup? If yes, restore \config\plugins\dockerMan\templates-user

3 hours ago, JorgeB said:

This means it's missing the user-template, do you have a flash drive backup? If yes, restore \config\plugins\dockerMan\templates-user

Ive put in the latest backup I have but its from 2023 and i would've made changes in 2024 for sure. tried what you said copying the backup over but still gives bad parameter on launch. is it cooked will i need to reinstall it?

11 hours ago, alcxander said:

bad parameter on launch

That's a different issue, I just meant this error:

 

15 hours ago, alcxander said:

I tried updating it and it says 

 

 

Did you try deleting and reinstalling that container, deleting its image but keeping its appdata data?

On 1/18/2025 at 7:40 AM, JorgeB said:

That's a different issue, I just meant this error:

 

 

Did you try deleting and reinstalling that container, deleting its image but keeping its appdata data?

hey sorry, busy weekend. 

 

It wasn't super clear cut, took a couple go rounds on plex. not sure what exactly was the issue but first seemed to be unraid wouldn't let something go in community apps, after a restart though it was able to install the plex container again but then some config wouldn't load. after little searching someone suggested resetting my plex server claim and that seemed to do the trick now I have plex started again AND i can see the media on it and play it. so win there.

 

I think I'm all good now, just have to reset my other apps to run again and should hopefully be back to nominal status. 

 

On another note, how do you guys protect against power outages etc? is there a good practice I can follow for protecting against this in future?

6 minutes ago, alcxander said:

On another note, how do you guys protect against power outages etc? is there a good practice I can follow for protecting against this in future?

Get a UPS and go to    SETTINGS  >>>>   UPS Settings.   I have both of my UPS's set up to shutdown after 30 seconds on  battery.   (I know from experience that if the power is out for thirty seconds, it will be out for a minimum of two hours.  The shorter the time on battery, the longer that battery will last.)  Be sure and check how long it takes your array to stop by timing a actual manual stop.  Then adjust the default setting---  SETTINGS   >>>>  Disk Settings   >>>>  'Shutdown time-out (seconds):'  to be about 25% longer than what you timed to allow for a graceful shutdown.  (Read help for this setting for more details.)