trurl
-
Posts
43882 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by trurl
-
-
UPS should only be on battery long enough to get past brief outage, then if power doesn't come back very soon, shutdown. You don't want to run on UPS, only shutdown on UPS.
-
Those small laptop HDDs probably don't perform well. And your parity disk is SMR which might be the reason a pause helps it out.
-
syslog says it is correcting, but I think unclean shutdown parity check is supposed to be non-correcting. I don't know if plugin affects that or not.
Seems like more sync errors than I would expect from unclean shutdown. Were previous parity checks zero sync errors?
-
Check filesystem on disk2 from the webUI. Capture the output and post it.
-
Just now, wgstarks said:
thought I had seen something like that
First post in thread 😉
-
39 minutes ago, UNPAID said:
Disk 1 is absolutely full and none of the other disks are being used at all
Probably because of your split level setting
-
32 minutes ago, wgstarks said:
is it possible to use this plugin to overwrite a drive with random zeros and ones?
On 2/27/2022 at 9:55 AM, dlandon said:Erase and Clear Disk - random patterns are written to the disk and then zeroes are written. This is a good choice for a disk to be discard to ensure all traces of files are removed.
-
You're right, it only lets me set it to a user share path. Which is probably better anyway since UD devices may not be mounted. And in the more general case where you are really sending syslog to a remote server, it has to be a shared path.
Does it work with both NFS and SMB? Or does it do it some other way?
-
You should be able to see your CPU temps in the BIOS. And Dynamix System Temps plugin shows this for me in Unraid.
-
4 hours ago, Zonediver said:
mirror the syslog to an unassigned device?
The flash drive is the only device that is guaranteed to exist. You can configure syslog server to use a path on an Unassigned Device with the other settings, but flash is the only thing that makes sense for "mirror" since it doesn't require you to set any path.
-
19 minutes ago, wall1s said:
replace drive 1 asap
Not clear there is anything wrong with disk1, and replacing/rebuilding it won't fix its filesystem.
-
Probably better to start a new thread with your diagnostics than post to a 5 year old thread about a version you don't have.
-
2 minutes ago, trurl said:
Even if parity rebuild won't succeed, parity contains none of your data as mentioned.
I often recommend not even using parity with USB since if something disconnects, the array won't be out-of-sync since there is nothing to be in-sync with. So nothing to rebuild. But nothing can be rebuilt.
-
Each data disk in the Unraid array is an independent filesystem that can be read all by itself on any Linux.
You could just New Config disk7 back into the array and rebuild both parity. Maybe physical disk7 is actually mountable and not corrupted. And then live with whatever results from repairing disk1 and possibly disk7 (until the next time). Even if parity rebuild won't succeed, parity contains none of your data as mentioned.
Your earlier diagnostics seemed to indicate there was a lost+found share, which would have been the result of an earlier check filesystem. It doesn't show as currently existing, possibly it is on the unmountable disk7 so can't be seen until repaired (again).
-
1 hour ago, LonelyScythe said:
random dockers magically deleting themselves
Maybe because they had empty mappings, which is technically a syntax error. Previous versions allowed this. You can get rid of the empty mappings, or install Docker Patch plugin.
-
4 hours ago, trurl said:
Before doing anything, it would be best to get those disks connected without USB.
-
Diagnostics after reboot can't tell us what happened before. Setup syslog server.
You have some out-of-date plugins. This one in particular has caused problems recently:
disklocation-master.plg - 2024.03.10 (Update available: 2024.03.22)
This might be related:
-
When you add a disk to a new slot in an array that already has valid parity, Unraid will clear the disk unless it has been precleared so parity will remain valid. All those zeros on a clear disk has no effect on parity. This is the only scenario where Unraid requires a clear disk. After the disk has been cleared and added to the array, you can format it so it can be used for files.
A disk that hasn't yet been formatted will appear as unmountable. In Main - Array Operation, it will list all unmountable disks and give you a checkbox to enable the format button and allow you to format them. You can see this in the screenshot you posted above.
NEVER format a disk that should contain your data. An unmountable disk that should have data on it needs to have its filesystem repaired. That is what check filesystem is for. Or, as suggested above, maybe its partition needs to be fixed.
1 hour ago, JorgeB said:As for disk2, once the rebuild finishes, unassign it and start the array, if the partition is the issue, doing that will recreate it, and if it looks good, then rebuild on top.
DO NOT FORMAT!!!
-
28 minutes ago, wall1s said:
And everything should be covered by parity.
I don't know what you mean by that. Parity is not a substitute for backup, whether Unraid or some other system.
Parity contains none of your data. Parity is just an extra bit that allows a missing bit to be calculated from all the other bits. That is basically how parity works in any system, Unraid or otherwise.
Parity contains parity bits that allow the contents of a failed/missing/disabled/emulated/rebuilding disk to be calculated from the bits on all the other disks.
https://docs.unraid.net/unraid-os/manual/what-is-unraid/#parity-protected-array
Parity by itself can recover nothing. All bits of all other disks must be reliably read to reliably rebuild all bits of a disk.
And as we have seen, it doesn't appear that your current setup can reliably read all other disks.
-
Doesn't look like there were any problems communicating with disk1 during that.
Do you have another copy of anything important and irreplaceable?
-
Filesystem corruption is independent of disk health. It is the data on the disk (actually, the filesystem metadata that keeps track of the other data) that is bad, not the disk.
And that does look pretty bad.
Looks like disk1 is connected to this controller
00:17.0 SATA controller [0106]: Intel Corporation Comet Lake SATA AHCI Controller [8086:06d2] DeviceName: Onboard - SATA Subsystem: Micro-Star International Co., Ltd. [MSI] Comet Lake SATA AHCI Controller [1462:7c79] Kernel driver in use: ahci Kernel modules: ahci
So USB is not causing any problems with that disk.
Post new diagnostics.
-
Do you have another copy of anything important and irreplaceable?
If you insist on trying to get things all working again while still on USB, then I am going to recommend only attempting rebuild of disk1 to a new disk and leaving the original with its contents alone in case rebuild goes badly due to USB.
-
When a disk is disabled, it is no longer used. Instead, all other disks are read to get the data for the emulated disk from the parity calculation, and parity is updated to emulate writes to the disk so those can also be recovered by rebuild.
The initial failed write, and any subsequent writes to the emulated disk, can be recovered by rebuild.
Repairing the filesystem will involve writing the emulated disk.
But, if you try to work with the emulated disk, you are relying on all the other disks working well to emulate the disk. If other disks disconnect as before, that won't work. And rebuild won't work either since it must write the emulated data to the rebuilding disk.
1 hour ago, trurl said:Also looks like you have corruption on disk1, but perhaps that is because it can't really be read.
This might be real corruption since I saw that in the logs after reboot, when presumably all enabled disks were still connected. And since that disk isn't being emulated, we could start with that one since repairing it would only involve disk1 and the remaining parity.
Check filesystem on disk1 from the webUI. Capture the output and post it.
-
14 minutes ago, discreet-booby4798 said:
Yes, ti's the old disk
Have you examined it's data?
15 minutes ago, discreet-booby4798 said:setting parity-check to run frequenlty
No reason to do that. Most only do monthly or even less frequently.
Unraid on MacPro 6,1 (darth vader trash can).
in General Support
Posted
Is this assigned to the array? SSDs in the array cannot be trimmed.