JorgeB
-
Posts
67,435 -
Joined
-
Last visited
-
Days Won
706
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
Yes, you can test one by one
-
No. First: Then: -Tools -> New Config -> Retain current configuration: All -> Apply -Check all assignments and assign any missing disk(s) if needed. You can even check "parity is already valid", then just run a correcting check since a few sync errors are expected.
-
You can still write and use the user shares normally while avoiding the overheard by writing directly to a disk share, just enable disk shares and then write to: \\tower\cache\your_share instead of \\tower\your_share -
Check filesystem on disk5.
-
Unable to access unraid after certain amount of up time
JorgeB replied to FranciumF's topic in General Support
Syslog starts over after a reboot, if it keeps happening try this. -
In this case I would do a new config and re-sync parity, still make sure actual disk1 is mounting correctly before doing it, you can do that with UD, disk1 must unassigned and array stopped.
-
What warning?
-
User shares always add some overheat, but for some unknown reason (at least to me) some users are much more affected than others.
-
my 1 harddrive Lost its File System (unmountable)
JorgeB replied to comet424's topic in General Support
Please post the diagnostics: Tools -> Diagnostics -
Yes. Yes.
-
Likely related to this, there are some common issues with the Ryzen SATA controller under heavy load, usually during a parity check or rebuild, there are some reports that updating to v6.9-beta1 helps due to the newer kernel.
-
The device errors look more like a connection problem with this SSD: Device Model: CT240BX500SSD1 Serial Number: 1919E1816D1E Replace/swap both cables.
-
If the latest xfs_repair can't fix the filesystem don't have any other ideas besides the ones suggested above. P.S. don't forget to delete the "extra" folder on the flash drive.
-
Almost certainly a disk problem, you can run an extended SMART test to confirm.
-
Please post the diagnostics: Tools -> Diagnostics
-
Forgot to mention, CPU is overheating and throttling down, check cooling.
-
Syslog starts over after a reboot, try this.
-
Looks more like a controller problem, you're using a Marvell controller with/connected to SATA port multipliers, either one is not recommended, and especially not both together, still good idea to run an extended SMART test on parity.
-
Docker Service failed to start: panic: runtime error: index out of range
JorgeB replied to cinereus's topic in Docker Engine
Same if you boot in safe mode? P.S. in the future please attach diags directly to the forum. -
See the first couple of posts in the UD thread, they have the answers to your questions, but if you still need help please post there.
-
Latest version appears to be 5.6.0, then follow then instructions on the link above, mailing list is below: https://xfs.org/index.php/XFS_email_list_and_archives
-
The problem is the filesystem, not the disk, rebuilding from parity won't help since it will rebuild the same filesystem, this looks like an xfs_repair bug since it seams unable to fix it.
-
Note that for this you'd need to back up first, you can't format and rebuild from parity.
-
It appears it's still failing, start array again, if the fs is still corrupt you'll need to ask for help on the xfs mailing list, manually upgrade xfsprogs to latest (not the one on the link) and try again, wait for a newer Unraid or re-format the disk.
-
This is more a request than a bug report, newer kernels support btrfs raid1c3 (3 copies) and raid1c4 (4 copies), currently a pool converted to raid5 or raid6 by using the GUI options will use raid1 for metadata (and rightly so since it's not recommended to use raid5/6 for metadata), the problem for a raid6 pool is that redundancy won't be the same for data and metadata as warned in the log: kernel: BTRFS warning (device sdb1): balance: metadata profile raid1 has lower redundancy than data profile raid6 i.e., data pool data chunks can support two missing devices but metadata can only support one missing device, with the new raid1 profiles this doesn't need to happen anymore, so when converting a pool to raid6 metadata should be convert to raid1c3. Note that if the user downgrades to an older Unraid release the pool won't mount, but it can always be converted before downgrading. P.S. you could also add convert options to raid1c3/c4 for data with 3/4 devices, not sure that would be used by many, but always nice to have the option if not too much trouble.
