-
Posts
61216 -
Joined
-
Last visited
-
Days Won
640
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JorgeB
-
-
Looks more like this issue:
-
Gateway for the 2nd NIC is GATEWAY[1]="0.0.0.0", I'm not sure but this could still be a problem, delete that entry, just leave it blank and apply.
-
Unassign all devices, start array, stop array, now set slots to 1 and re-assign the 1st device, then continue with
58 minutes ago, JorgeB said:start array with just the 1st device, stop array, set pool slots back to 2, re-assign 2nd device, start array, if it doesn't work post new diags.
-
48 minutes ago, segway said:
Where can I post it?
Here in the forum, just attach to your next post.
-
It could be the devices, but IMHO unlikely that two would have issues at the same time.
-
Also post the diagnostics.
-
There's still no Interface Rules, did you delete network.cfg and restarted?
-
Unlikely that it's a device problem, try bypassing the backplane.
-
5 minutes ago, segway said:
I uploaded the Hardware Diags from the Tools page, Here's the XML output.
We need the complete diagnostics zip.
-
2 minutes ago, skler said:
Can I manually change it
No, it's automatic, disk1 will always be a zpool called disk1.
-
Interface Rules is empty, delete/rename /boot/config.network.cfg and reboot to see if the NICs appear there, note that settings will go back to default DHCP.
-
That should not happen when adding a new device, something weird still going on there, try this:
Unassign the second nvme device, also wipe it with wipefs -a, set pool slots to one, start array with just the 1st device, stop array, set pool slots back to 2, re-assign 2nd device, start array, if it doesn't work post new diags.
-
8 minutes ago, segway said:
and the fastest write speeds I see are 150MB/s, which seems awful slow.
That's not that slow, Unraid doesn't stripe disks, so it's limited to the speed of the slowest disk at any point, you can post the diags so we can see the hardware used.
9 minutes ago, segway said:rsync starts at 200-300 MB/s but then slows down to 3.7 MB/sec
Is the parity sync/check done? If yes post the diags during a transfer, after it slows down.
-
Post new diags.
-
The zfs pool is corrupt, you should backup and re-format, see if it mounts read-only without panicking, you can then backup.
Reboot the server, don't start the array, and type:
zpool import -o readonly=on cacheIf OK, start the array, cache will show unmountable in the WebGUI, but the data will be under /mnt/cache, backup and then re-format.
-
If you were using /mnt/user for the mappings everything will remain working, if you were using /mnt/disk1 you need to change to /mnt/pool_name
-
58 minutes ago, oldguy said:
Why the system do not decrease the transfer speed ?
Because if the server is flushing the data slower it can cause temporary halts, could also be a network issue, assuming gigabit, transfer should start at 100MB/s while being cache to RAM, then slowdown to keep up with device speed, according to your video it's starting already at 50MB/s, suggesting the network has bandwidth issues, run iperf.
-
1 hour ago, xylcro said:
his I don't understand, what do you mean "should be per slot"?
If you enable bifurcation for for example PCIe slot2, only slot2 will use it
-
Just added and start the array, it should automatically create a mirrored pool (raid1).
-
After that you can also create a new pool with sdi, but make sure it's wiped first, just in case there's some old filesystem there causing issues, so before adding it to a new pool run:
wipefs -a /dev/sdX -
OK, you can now add the other NVMe device, if you want to make the pool redundant again.
-
There's still something strange going on there, leave sdi disconnect for now, unassign both nvme devices, start array, stop array, re-assign only /dev/nvme0n1p1 to the old pool, start array, post new diags
-
That suggests the devices are not keeping up with the transfer, your disks are SMR and the cache SSDs a white brand, do you have a non SMR disk you could test with?
-
That device it from the old pool correct? If yes, the other one was wiped, was the pool redundant?
Why does Parity-Check keep initiating spontaneously?
in General Support
Posted
Apr 16 14:11:01 Server emhttpd: unclean shutdown detectedSomething is causing the shutdowns to be unclean, look in the flash drive /logs folder for a diagnostics zip from the time of the last shutdown, and post them here.