JorgeB
-
Posts
67,499 -
Joined
-
Last visited
-
Days Won
706
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
Moving array disks around to match bay placement
JorgeB replied to Idolwild's topic in General Support
You can do a new config, with single parity data device order doesn't matter, so you can check parity is already valid after the changes to avoid a parity sync (you can only change the order, all devices must remain the same). -
Like @trurlmentioned you should always post the complete diags, but this is a rather common problem with the onboard SATA controller and Ryzen boards, usually using the latest beta helps, but I see you're already using it, look for a bios update os disable IOMMU of not needed.
-
Please post diags so I can have a look at the hardware you have.
-
The backplane you have uses a direct connection the the drives, so no way to be faster, if you have performance issues it's not that, where are you trying to improve perfomance?
-
You're welcome.
-
No expander, each miniSAS plug connects directly to 4 devices.
-
Now might as well let it finish, but if/when you add a new disk do it the correct way.
-
Because it was set to xfs, default is auto. No, you don't need to do anything with UD, just assign it to an array slot, start the array, disk will be cleared (unless it was precleared already) and then you can format.
-
AFAIK Norcos don't usually have an expander, a SAS expander allows a single cable from the HBA to connect all disks, can you do that?
-
If it's a new disk it will use the default filesystem set on Settings -> Disk Settings, if you have an array disk and want to change it to a different filesystem then you click on it and change it there, then format at next array start.
-
That's not how you do it, you can or not preclear the drive, don't format, add to array, if the drive is not precleared it will be cleared by Unraid and then you can format it, if it precleared you'll just need to format it.
-
Stop array, click on the that disk and change the filesystem to the new one, start array and format.
-
If you do it inside the array there's no need for a check after.
-
Yes, all array disks should be formatted inside the array, or parity won't be updated and will become out of sync.
-
Auto will give the filesystem already on disk, if it's already formatted with one of the supported filesystems, or what's set on settings -> disk settings for any newly formatted disk.
-
Because you're not doing it right. Stop the array, click on disk3, set filesystem to auto, start array. You'll still need to run a parity check after.
-
But that was before, after formatting the disk with UD the next check will detect sync errors.
-
Unassigned devices plugin. No it's not, Unraid just has no way of knowing it's not, until you run a parity check, it will still say valid but there will be sync errors.
-
Very clean.
-
It's not, it's set to xfs. Also, why are you formatting array disks with UD? That will make parity invalid.
-
It's difficult to say, it can be good for weeks or months to come, or it can give more issues tomorrow.
-
Tools -> Diagnostics
-
That is mostly useless, it only changes if there's failing now attribute. Disk passed a recent extended SMART test, so it's fine for now (or it was at that time) and the pending sector is a "false positive", but SMART is showing some issues, likely will have more problems in the near future.
-
Click on disk1 and make sure fs is set to auto or btrfs, if it's not that post the diags.
-
Maybe, but that number on the SMART report can also be wrong, possibly a firmware issue.
