Suddenly get this error when trying to use the webterminal. Same issue on all browsers and in incognito mode from all connected machines.

Rebooted to see if that would fix it and can ping and ssh but now webgui is completely not working nor are any of the web services. Getting really worried now, what is going on?

Edited April 7, 20214 yr by cinereus

https://wiki.unraid.net/Manual/Troubleshooting#Capturing_Diagnostic_Information

Sorry took me a while to work out how to access the zip file. SMB wasn't up.   

fs-diagnostics-20210407-2220.zip

Edited April 7, 20214 yr by cinereus

Now getting "Docker Service failed to start."

 

And under Settings>Docker:

 

 

Apr  7 22:08:12 fs emhttpd: /mnt/cache mount error: No file system
Apr  7 22:08:12 fs emhttpd: shcmd (48): umount /mnt/cache
Apr  7 22:08:12 fs kernel: XFS (sdi1): Invalid superblock magic number

Run the File System Check against the cache drive

6 minutes ago, Squid said:

Apr  7 22:08:12 fs emhttpd: /mnt/cache mount error: No file system
Apr  7 22:08:12 fs emhttpd: shcmd (48): umount /mnt/cache
Apr  7 22:08:12 fs kernel: XFS (sdi1): Invalid superblock magic number

Run the File System Check against the cache drive

Thanks. Just noticed cache is "Unmountable: No file system"

 

There's a lot of chat about "If the file system is XFS or ReiserFS (but NOT BTRFS), then you must start the array in Maintenance mode, by clicking the Maintenance mode check box before clicking the Start button. "

 

But I assume the cache is not part of the array so I can just go ahead? It seems the general command is "xfs_repair -v /dev/md1" but how on earth do I find what /dev/??? is my cache drive?

It's called "sdi". Does that mean a working command is

 

xfs_repair -v /dev/sdi

 

?

2 minutes ago, cinereus said:

It's called "sdi". Does that mean a working command is

 

xfs_repair -v /dev/sdi

 

?

Not quite   when using the raw device names (the sdX type) then you need to include the partition number so it is /dev/sdi1 

@Squid @itimpi

 

"Sorry, could not find valid secondary superblock
Exiting now."

 

What now? No idea what it had an issue in the first place...

What did you have on cache? appdata I assume, did you have it backed up? Anything else important?

5 hours ago, trurl said:

What did you have on cache? appdata I assume, did you have it backed up? Anything else important?

Not sure. How do I tell? From my screenshot above it seems I might have had system on there too? What's best practise for restoring? 

Did you have any VMs?

1 minute ago, trurl said:

Did you have any VMs?

Yes but not fussed if I lose them. Mainly just want to get the system up and running asap. It was just that the Docker screen said the docker.img was lost too.

Edited April 8, 20214 yr by cinereus

docker.img isn't important. It is only the executables of your containers, and those are easily downloaded again. The Previous Apps feature on the Apps page will reinstall your dockers exactly as they were. But if you don't have appdata then the applications themselves would be starting over.

Thanks, so what's the process exactly? Reformat cache and then just copy paste appdata folder over? Then work out which dockers I was actually using and reinstall them one by one? 

Edited April 8, 20214 yr by cinereus

Previous Apps actually shows you all dockers you had previously installed and lets you select any of them. Some may be listed that you weren't using any more if they have a template on flash.

 

https://wiki.unraid.net/Manual/Storage_Management#Reformatting_a_cache_drive

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Create_the_Docker_image_file

 

https://wiki.unraid.net/Manual/Docker_Management#Re-Installing_Docker_Applications

What's the correct order? Reinstall before copying appdata or after?

Installing a docker starts it, and the dockers need to have their appdata already in place when they start or they will create new appdata.

Thanks all.

 

It's worth noting that my appdata and system shares have completely disappeared. Will these steps automatically re-create them? And obviously I've lost all data that was on cache?

 

So the precise order of steps I need to follow is as follows?

 

1. Reformat cache?

2. Recreate docker.img?

3. Copy appdata

4. Reinstall dockers?

Edited April 8, 20214 yr by cinereus

And under "Reformatting a cache drive" I have no idea what step 4 is asking me to do:

 

"Set all shares that have files on the cache and are currently not have a Use Cache:Yes to BE Cache:Yes. Make a note of which shares you changed and what setting they had before the change"

 

I have two shares that are "Cache: Yes" but obviously no shares have files on cache as there is no working cache at the moment. 

post new diagnostics

26 minutes ago, trurl said:

post new diagnostics

Okay it came up after 25 mins. I still don't have an appdata or a system share so unsure how to restore my appdata backup before re-installing dockers....

1 hour ago, trurl said:

post new diagnostics

 

4 hours ago, trurl said:

post new diagnostics

 

 

I think I got it working again. Although does anyone have any idea why my cache randomly corrupted itself in the first place?