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
-
Looks like a problem with the device, but not necessarily connection related.
-
Looks like the server rebooted, though no unclean shutdown was detected, which is strange.
-
Start by running memtest.
-
There is a driver in the latest 6.9-rc, but possibly it has issues, you could try v6.8.3 to see if it works. -
I missed that, but unfortunately there's nothing logged before the crash, that points to a hardware issue, another thing you can try it to boot the server in safe mode with all docker/VMs disable, let it run as a basic NAS for a few days, if it still crashes it's likely a hardware problem, if it doesn't start turning on the other services one by one.
-
If everything is working no need to worry, many times I've ran one of my servers close to 90% with all the VMs.
-
If you need sync features in an easy to use way look for synback free for Windows.
-
Sorry, that's outside my wheelhouse.
-
If the drivers are connected to the HP raid controller use the LSI instead, though firmware should be updated when possible.
-
-
Could be a hardware issue but you can try this to see if it catches anything.
-
If it's related to this issue use this thread, so we can remember the full story.
-
Diags are just after rebooting so not much to see, assuming the "power supply idle control" is correctly set you can try this and then post that log.
-
Please use the existing Nvidia plugin support thread.
-
If it works normally with Windows it shouldn't be network related, why not use Windows or rsync?
-
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/
-
Changed Status to Closed Changed Priority to Other
-
Changed Priority to Other
-
There is a driver, but it's crashing and failing to initialize: Feb 8 13:55:57 Towerd kernel: tn40xx: MV88X3310 initdata applied Feb 8 13:55:57 Towerd kernel: tn40xx: MV88X3310 I/D version is 0.3.4.0 Feb 8 13:55:57 Towerd kernel: ------------[ cut here ]------------ Feb 8 13:55:57 Towerd kernel: WARNING: CPU: 3 PID: 1380 at net/ethtool/common.c:375 ethtool_check_ops+0xe/0x16 .... Feb 8 13:55:57 Towerd kernel: tn40xx: probe of 0000:04:00.0 failed with error -22 Can't tell you if it's a driver or NIC problem though.
-
You can rebuild on top, if, and only if, the emulated disk is mounting and data looks correct, or do a new config and re-sync parity.
-
Drives being disabled when stopping array or restarting when drives are asleep
JorgeB commented on SavellM's report in Prereleases
You can still download v6.8.3, extract all the bz* files to the flash drive overwriting existing ones, then reboot. -
Adding external drive enclosure to my array 6.8.3
JorgeB replied to Cark's topic in Storage Devices and Controllers
Don't know that model but if it's a standard SAS enclosure yes, you just need a SAS HBA, like an LSI 9200-8e. -
Both disks dropped offline are reconnected with a different identifier, this is usually a connection/power problem, could also be controller/expander related.
-
It failed the extended test, so it should be replaced, you can also try a full device write/discard to see if it clears the errors (all data would be deleted).
