JorgeB
-
Posts
67,504 -
Joined
-
Last visited
-
Days Won
706
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by JorgeB
-
On the diags posted I only see issues with disk6, could be the Seagate doesn't like that Jmicron controller, try swapping it with one the disks on the onboard SATA ports.
-
Unlikely to be the CPU, very rare to have a CPU go bad, but it's possible.
-
You have both dimms on the same channel, so it's overloading that channel and running out of spec, it's also running slower than it would in dual channel. You need to to alternate the slots when installing just two dimms, usually they are color codded so both dimms should be on the same color slots.
-
Likely a result of the crashing, not the reason for it, but you need to check filesystem on disk9. You should also try this, it might catch the beginning of the crash problem.
-
You can extended the trial using the GUI twice for an additional 15 days each time, so total trial can be up to 60 days.
-
Pools can only be btrfs, with the array stopped run: blkdiscard /dev/sdX Replace X by the correct letters for both devices and run it one at a time, this will do a full trim on the devices complete wiping them, then start the array and you'll have the option to format.
-
Correct, though it could be faster if for your use case you can read files from different devices simultaneously. -
Array should still stop, make sure mc is closed and close the ssh session, but you can unmount with umount /x
-
Missed that, changing to minor which seems the most appropriate.
-
If you have VMs keep existing file, also good practice to have a backup of that file.
-
Did you also stop overclocking the RAM? On the diags posted it's above max supported speeds, also explained on the link above.
-
Adding some more details: -non correcting check works correctly after first array start (with auto-start enable or disable) -the firs parity check after stopping and re-starting the array is always correct, even if you uncheck the "write corrections" box, if you cancel and run another one (without stopping the array) it works correctly.
-
You can but you'll still need to run a correcting check, a few sync errors would be expected.
-
On the console type "mc" to open midnight commander, then navigate to /x on the left side and to where you want to copy on the right, then just copy from one side to the other.
-
It could.
-
Yes, but you won't know until you try it, also some recovery options here if needed.
-
Cache filesystem is corrupt, best bet is to backup anything important and re-format the pool.
-
Yes, pools can use all the available btrfs raid profiles (for the number of disks used).
-
HBA should be capable of 2500MB/s to 3000MB/s, there's a known issue with v6.8.x where parity checks can be slower, especially for larger arrays, you could do a quick test with v6.7 to confirm if it's that.
-
Very possibly that's the problem.
-
DiskSpeed, hdd/ssd benchmarking (unRAID 6+), version 2.10.9
JorgeB replied to jbartlett's topic in Docker Containers
Those are SMR, they will only show the correct performance after being written completely at least once. -
Type "powerdown" on the console, if it doesn't shutdown after a couple of minutes you'll need to force it.
-
Server is still crashing: Aug 14 09:30:39 Warptower kernel: BUG: unable to handle kernel paging request at 0000000000cd0038 Possibly a hardware issue, start by running memtest.
-
Run an iperf test to check your LAN.
-
You should, there is indeed a bug, it works correctly at first array start (auto-start enable or disable) but it doesn't the first time you do it after stopping and re-starting the array. Since it still happens on the latest beta and that's the one being developed please report it here: https://forums.unraid.net/bug-reports/prereleases/
