JorgeB
-
Posts
67,603 -
Joined
-
Last visited
-
Days Won
707
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
Please use the existing support thread: https://forums.unraid.net/topic/4351-cache_dirs-an-attempt-to-keep-directory-entries-in-ram-to-prevent-disk-spin-up/page/46/
-
Macvlan call traces are usually the result of having dockers with a custom IP address, more info below. https://forums.unraid.net/topic/70529-650-call-traces-when-assigning-ip-address-to-docker-containers/
-
The eSATA includes a port multiplier: Apr 17 14:05:41 Tower kernel: ata1.15: Port Multiplier 1.2, 0x197b:0x0562 r0, 2 ports, feat 0x5/0xf That's my guess on what's causing the problems, not even sure the onboard AMD SATA controller suports port multipliers, Intel doesn't. -
Note that you can still mount those disks inside Unraid using the UD plugin if you prefer to do a local transfer to the array.
-
I still don't get what the issue is here. Are these vdisks? I have no issues adding multiple vdisks.
-
Moving drives from old version to new version unRAID.
JorgeB replied to ChipBuffalo's topic in General Support
Just need to check "parity is already valid" after the new config and before array start. -
Yes, Unraid requires a specific partition layout so you'll need to re-format any disk to be used in the array or pool.
-
There were read errors on disk2, but it doesn't look like a disk problem, replace the cables and run reiserfsck again. P.S. In case you're not aware parity disable, so array is unprotected.
-
To logout click here: Don't understand what you mean.
-
This is difficult to diagnose with the diags, stop all your dockers/VMs and then enable one by one and let it run for a day or so to see if you find the culprit.
-
Please post the diagnostics: Tools -> Diagnostics
-
Yes, it was a problem with LSI, it kept resetting: Apr 17 13:38:11 NAS-NG kernel: mpt2sas_cm0: fault_state(0x2622)! Apr 17 13:38:11 NAS-NG kernel: mpt2sas_cm0: sending diag reset !! Apr 17 13:38:12 NAS-NG kernel: mpt2sas_cm0: diag reset: SUCCESS But strange that booting UEFI would cause this, I have no issues with that. might not be the reason, unless it's some BIOS bug.
-
Both checks were correcting and both found errors, and only on parity1, which is kind of strange, what was done between the two checks?
-
Related to this issue, see there for a workaround.
-
Reboot to clear the log, crate a new share with a name that never existed before and post new diags if it fails.
-
Changed Status to Closed Changed Priority to Other
-
This should be be in the general support forum, try recreating the flash drive using the same device, any more questions please continue below:
-
TBW is partially the expect life but mostly the limit for the device to be within warranty, it doesn't mean the SSD is going to fail when you reach that, for example the cache device for one of my servers has a TBW of 500TB and is currently at 847TB and still going strong, though it's a good idea to monitor that, on NVMe devices you just need to monitor this: This is the estimated life used percentage.
-
Apr 17 10:10:35 Tower root: mkdir: cannot create directory '/mnt/user/tmimacnew': No space left on device Was it this share?
-
Some are OEM, but also have IBM or HP, don't believe I have any Dell.
-
If the emulated disk is fixed after running xfs_repair and contents look correct, and only if that's true, you can rebuild on top by doing the follow: -stop array -unassign disk1 -start array -stop array -re-assign disk1 -start array to begin rebuild
-
Check filesystem on disk1: https://wiki.unraid.net/Check_Disk_Filesystems#Checking_and_fixing_drives_in_the_webGui Remove -n flag or nothing will be done and if it asks for it use -L
-
Please post the diagnostics: Tools -> Diagnostics
-
Adding a Drive into Array from Parity to Data Drive
JorgeB replied to fschris's topic in General Support
It will be formatted with the default filesystem set: Settings -> Disk Settings -
That suggests the disk is failing, post new diags after running that (and before rebooting).
