Posts posted by JonathanM
-
-
-
-
-
-
-
Just now, another_hoarder said:
You also asked about the parity check / history - does that give us an idea if I could try popping in another disk and rebuilding from parity? Or has parity been indeed rebuilt yesterday and I'm out of luck on that front?
The emulated disk is being emulated from parity. What you see is what would be rebuilt on another disk.
Normally when a disk is detected as new and set to be cleared, it shows up with a blue square, at least on current versions. You didn't mention that, which struck me as strange. Once a disk is cleared, data recovery from the physical disk is practically impossible. That's why I was hoping against hope that parity wasn't changed since the incident, as the clearing process is normally done to AVOID the need to update parity when adding a new disk.
Before you throw in the towel I'd at least let the check run to completion.
-
-
-
5 minutes ago, another_hoarder said:
I couldn't find the option from the GUI.
If the file system type is set as Auto, and it can't figure out what type it was, it won't offer an option.
Set the file system type to XFS and the check filesystem section should show up.
-
30 minutes ago, ToXIc said:
heres what i see in krusader
I find the Dynamix File Manager to be less intuitive than some alternatives, to get to the same point you show in your krusader screenshot, click on the house in the upper left after you open one of the shares or disks in the file manager.
I'm not aware of a direct shortcut to that view.
-
1 hour ago, Renegade605 said:
enterprise customers weren't shutting down their services every hour to run snapshots
They are also not typically running software that chokes if the file wasn't closed during backup. Many consumer level software packages behave poorly if the recovered file is in a state that indicates it's currently in use.
-
-
7 minutes ago, another_hoarder said:
Also, disk check has been running on the emulated disk8
Did you run the check from the GUI or at the command line? It's easy to get wrong at the command line.
It is the emulated disk (red X instead of green dot) that you are checking, correct?
9 minutes ago, another_hoarder said:Crucial question - how would I know if parity is still valid from before the disk dropped as opposed to anything done since having updated parity?
When was your last parity check that completed with zero errors?
-
6 minutes ago, Espressomatic said:
Instead of starting a new thread, here we go, better late than never. Step by step instructions for setting up Stremio Web on Unraid with the ability to access and play content from any device, including iOS via browser without addons or other apps.
https://github.com/tsaridas/stremio-docker/issues/44#issuecomment-2383343627
Why is the 1st prereq to setting up a self hosted instance to get a login to their site?
Is the self hosted still reliant on their service?
-
Do you have backups of all the important data? Moving stuff around like this is one of the riskiest things you can do, it's all too easy to accidentally delete stuff.
If not, I recommend NOT removing any of the old drives, instead be patient and add drives to Unraid as you have the resources, and make copies instead of moving.
-
10 hours ago, another_hoarder said:
I see. Thanks, will attempt that next. Although it was weird in first place upon booting up that the drive in question showed up in Unassigned Devices and Array didn't show as degraded. 🤨
That makes me think something went terribly wrong. I hope you have good backups, sounds like parity may not be valid with that disk. Hopefully it's still valid from before the disk dropped.
-
-
-
5 minutes ago, another_hoarder said:
could I just try to rebuild this drive from parity since it hasn't yet been updated? Wouldn't that be one way of getting this data back?
If you want to, you could physically disconnect that disk, then when Unraid is started it will show what is emulated by parity. Be aware that doing that will put you in a riskier spot, if one of your other disks fails you would be at a greater risk of losing both drives.
Just be very very sure you remove the correct disk, and once you remove it, don't put it back in the system until the emulated disk slot has a repaired filesystem. That way if the emulated disk is also corrupt, you at least get another shot at fixing the filesystem on the physical disk.
-
8 minutes ago, another_hoarder said:
Will this just format the drive and start rebuilding its data from parity?
It will update the parity drive to show that the drive is blank, overwriting the corrupt filesystem with a blank one, removing any data.
What you are seeing is what is on the drive, a corrupt filesystem. You need to run a filesystem check in the GUI for that drive.
The drive is not disabled, it doesn't have a red X.
https://docs.unraid.net/unraid-os/troubleshooting/data-recovery/#unmountable-disks
https://docs.unraid.net/unraid-os/manual/storage-management/#checking-a-file-system
-
-
-
-
Unassigned Devices Preclear - a utility to preclear disks before adding them to the array
in Plugin Support
I'm unclear how this version is implemented, but some versions only write the signature after the last pass is successful.