-
Posts
61,692 -
Joined
-
Last visited
-
Days Won
650
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JorgeB
-
-
23 minutes ago, teakmeister said:
picking increasing UDMA CRC error count in SMART.
This is usually a SATA cable problem, replace the SATA cable and see if it stops increasing.
-
Reboot, try again, and if it still fails post the complete diagnostics.
-
Sorry, though you posted the complete diags.
CRC UDMA errors are usually a SATA cable problem, replace the SATA cable and acknowledge the current value, as long as it doesn't keep increasing, the problem is resolved.
- 1
-
If it's a hardware issue most likely there won't be anything logged, you can start by running memtest or using for example a different PSU.
- 1
-
8 minutes ago, tgiannak said:
after 3 months with stable server, the last 2 days started to make reboots!!
If you mean the server is rebooting on its own, that's almost always a hardware problem.
-
Maybe you have a script running? Check User Scripts.
-
Still problems with disk2, it may be failing, you can try to swap cables with a different disk as a final check.
-
Which drive?
-
Looks more like a power/connection problem, replace/swap cables and try again.
-
Don't recommend using zfs for the array at the moment, since there's a know performance issue with writes, it doesn't affect pools, only the array.
Pools can also be used with disk shares, or exclusive shares.
-
16 hours ago, elangva said:
im running verison 6.12.6
You need to update to latest release for Starter keys to be supported.
-
13 hours ago, icarus69 said:
I'm curious about what the default setting for RAM allocation is before you added this conf file though.
1/8 installed RAM
-
Look for the existing support thread for that container:
- 1
-
Please post the diagnostics, if you cannot get the full diags post the syslog at least.
-
There's something writing to disk1.
-
There appears to be something else reading from disk26, try stopping all other activity.
- 1
-
Just now, weirdcrap said:
But that's just a share on my array?
No, because it already exists before array start, so something else is creating that folder.
-
I'm not seeing any OOM error, but IIRC correctly this will trigger FCP:
Apr 27 11:17:43 Hal-9000 emhttpd: cmd: /usr/local/emhttp/plugins/user.scripts/showLog.php Out Of Memory Check - Hrly
Change that script name
-
You have something creating this folder before the array starts:
Apr 28 04:40:42 Node emhttpd: error: malloc_share_locations, 7199: Operation not supported (95): getxattr: /mnt/user/CommunityApplicationsAppdataBackup
You need to correct that, or the shares won't then work correctly.
-
Trial does not prevent later using a paid license.
-
Diags are after rebooting so we can't see what happened, but SMART looks fine, check/replace/swap cables to rule that out and re-sync parity, and if it happens again save the diags before rebooting.
https://docs.unraid.net/unraid-os/manual/storage-management#rebuilding-a-drive-onto-itself
-
Once a key is transferred it cannot be undone, you can use the new flash drive with the old server and start a new trial with a different one.
-
10 hours ago, couzin2000 said:
Server back on, my array is completely different-- my disks were all mixed up and not able to start because somehow the parity disk had been moved to the data disks...???
That suggests a flash drive problem.
10 hours ago, couzin2000 said:Now, my array is in the same config, only the Parity drive is showing as a NEW DEVICE. It's exactly the same drive in the same spot! Am I going to lose everything here? the array doesn't want to start anymore because It's say "Too many wrong and/or missing disks!"
If you have all the original disks assigned to the correct slots, you can do a new config and check "parity is already valid" before array start, then start array and you can try replacing the bad disk again.
-
13 hours ago, crittersfritters said:
as it's not nearly old enough to be failing.
Any hardware can fail at any time, even new one.
13 hours ago, crittersfritters said:Assuming faulty hardware is not the root cause, what else could be causing complete shutdowns with no logging?
If the server shutdowns, vs. crashing or hanging, first suspects would be CPU temp or bad PSU, could also be board related.
Swap parity drive with a current data disk
in General Support
Posted
What would described won't work, you could manually move the data from one of the 3TB disks, then do a new config without it and use it as parity.