JorgeB
-
Posts
67,814 -
Joined
-
Last visited
-
Days Won
708
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
You can use UD to mount the drive.
-
It is, but the same solution was posted in the post above that one.
-
Browse /temp with for example midnight commander (mc on the console) and check contents.
-
Sdc is part of a different filesystem, should still be able to recover data from the NVMe device using the recovery options here, use the ones that have 'degraded' in the mount options.
-
Please post the output of: btrfs fi show
-
Type: btrfs-select-super -s 1 /dev/sdc1 Then post new diags.
-
That means the pool had another device, which is now missing, do you know/still have that device?
-
New diags please.
-
It should mount now.
-
Type in the console: btrfs-select-super -s 1 /dev/nvme0n1p1 If the command is successful see if it now mounts with UD or after re-assign to a pool, but to a pool without missing devices or it can be wiped (again).
-
Cache1 appears to be failing, run an extended SMART test.
-
If it happens again to the same disk please post in this thread so we can remember what was done.
-
And the GUI is still inaccessible correct? If yes, I'm not seeing anything obvious, try rebooting in safe mode, disable docker/VM services and start the array to see if there's any difference.
-
It should reconnect on its own, possibly depends on the router, you can always use a static IP address. -
Like the link above mentions you can get the diagnostics from the CLI by typing 'diagnostics'.
-
Use -L
-
After array start please.
-
Looks more like a power/connection problem, replace the cables (or swap them with another disk) and try again.
-
Please post the diagnostics.
-
Jul 29 18:32:36 Andisvault kernel: macvlan_broadcast+0x116/0x144 [macvlan] Jul 29 18:32:36 Andisvault kernel: macvlan_process_broadcast+0xc7/0x110 [macvlan] Macvlan call traces are usually the result of having dockers with a custom IP address, switching to ipvlan should fix it (Settings -> Docker Settings -> Docker custom network type -> ipvlan (advanced view must be enable, top right)), or see below for more info.
-
That's usually a flash drive problem, try using a different one to test.
-
Start by running a single stream iperf test to check network throughput.
-
You can just delete the old one and re-create.
-
Unusual for an LSI HBA making Unraid crash, but test for some more time, it's not impossible, there could be some compatibility issue with your board or other hardware.
-
Start by adding 30 secs or so the the shutdown timeout (Settings -> Disk settings), if that doesn't help and Unraid still can't do a clean shutdown it will save the diags to the logs folder in the flash drive, post those from the latest one.
