JorgeB
-
Posts
67,572 -
Joined
-
Last visited
-
Days Won
707
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
That can only happen if the disk (or the emulated disk) was formatted by you, at most it could have been unmountable, but Unraid never formats a disk on its own. It will rebuild whatever is showing on the emulated disk, that should already show you data, and you can see that after starting the array with that disk unassigned.
-
You don't format the disk outside or inside the array, rebuilding will create the filesystem.
-
Make sure the cable is forward breakout, reverse breakout looks the same but won't work for this.
-
I find it pretty easy, but the other option it to just do a standard replacement of disk1, since you're using xfs there's no way of knowing which files will be corrupt though, unless you have pre-existing checksums.
-
Most likely, try backing up the config folder and then re-create the flash, if it fails transfer the key.
-
Something is mounting the disk before Unraid: Jan 7 00:36:52 RyzNas kernel: XFS (sdf1): Mounting V5 Filesystem Jan 7 00:36:52 RyzNas kernel: XFS (sdf1): Ending clean mount Also note that because of that parity won't be 100% in sync.
-
Cache is completely full, docker image ran out of space, resulting in lost writes = corruption.
-
This means there's already an fs mounted with the same UUID, please post output of: blkid
-
Adding Larger Data Disk Before Parity Disks Upgrade
JorgeB replied to Gico's topic in General Support
You can't have a data disk larger than parity, you can upgrade parity then use the old parity as a data disk. -
See here, respect max RAM speed for your config, currently it's overclocked, also make sure "power supply idle control" is correctly set.
-
This is likely a general support issue, also please post the diagnostics, if nothing else it will show the hardware you're using, there are some known issues if it's for example a Ryzen based server.
-
Errors - likely from me moving cables and such inside?
JorgeB replied to alexdodd's topic in General Support
Should be fine. -
Please post the diagnostics: Tools -> Diagnostics after a failed start attempt.
-
I recently create a bug report of the issue, please add to it if you find anything that works.
-
There are multiple read errors on disk1, which appears to be failing, that likely explains the sync errors.
-
Errors - likely from me moving cables and such inside?
JorgeB replied to alexdodd's topic in General Support
There's an issue with Smartmontools and those drives, there's no temp but also not any attributes, you can't even see SMART test results, so difficult to say if it's a disk problem or not, maybe by the way it's logged, you can a non correcting check to see if they repeat or not. P.S. There are cable problems with the unassigned Seagate drive -
I linked the FAQ entry the first time.
-
WD Reds are usually good (just avoid the new CMR ones, for performance reasons, not reliability), but any disk can fail at any time.
-
Convert the pool to raid1 then remove the old device.
-
Initial error is logged as a disk problem, but then it dropped offline so there's no SMART report, reboot/power cycle to see if it comes back online and post new diags.
-
There have been various reports of this error when booting Unraid on different Dell models, according to the post below using an updated syslinux helps with this:
-
Understood, not much more I can do but I'll create a bug report to see if LT can update the syslinux they're using.
-
Yes, same as any other Linux with early kernel 5.10.x, one of the reasons I'm still running an earlier beta.
-
As I understand you just need to install syslinux (after updating it) on the flash drive with: syslinux --install /dev/sdX1 Replace X with correct letter.
-
You can add multiple data drives at once, but you can't add parity2 and data drive(s) at the same time.
