3ajs Posted February 27, 2020 Share Posted February 27, 2020 Hello, I've tried to preclear and format the new drive but both get stuck and requires a hard reset. Any help is greatly appreciated. beast-diagnostics-20200226-1555.zip Quote Link to comment
JorgeB Posted February 27, 2020 Share Posted February 27, 2020 Diags are after rebooting, try again and grab new ones if it happens again, if the GUI doesn't respond use the console and type diagnostics, if that also doesn't work enable syslog server and try again. Quote Link to comment
3ajs Posted March 3, 2020 Author Share Posted March 3, 2020 Here's an update: went through several cycles of leaving it alone for a few days, while it was stuck, GUI stopped responding, sometimes it would take down the whole LAN, unplug network cable LAN restored, hard reset Unraid server. After going through several cycles of this, the drive somehow appeared as Online and wrote 56GB of data. Now we have a new problem, whenever we start the array, it proceeds through to Array Started, but soon after the GUI becomes unresponsive. If left alone, it eventually leads to Unraid taking down the whole LAN, requiring us to unplug the network cable and hard reset Unraid. Attached is the diagnostic pulled before starting the Unraid, we will try to get the diagnostic while the GUI is hung up... beast-diagnostics-20200303-1630.zip Quote Link to comment
3ajs Posted March 3, 2020 Author Share Posted March 3, 2020 Another diagnostic after hard reset...system was hung up beast-diagnostics-20200303-1808.zip Quote Link to comment
JorgeB Posted March 3, 2020 Share Posted March 3, 2020 13 minutes ago, 3ajs said: Another diagnostic after hard reset Those don't really help, did you: On 2/27/2020 at 3:27 PM, johnnie.black said: enable syslog server Quote Link to comment
3ajs Posted March 5, 2020 Author Share Posted March 5, 2020 thanks heres the syslog attached. the ui became unresponsive some time after the array was started. a hard reset was done about 12 hours later and the syslog was pulled after the reset syslog Quote Link to comment
JorgeB Posted March 5, 2020 Share Posted March 5, 2020 There are issues with the flash drive, backup and re-create: Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (5 != 4) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): Filesystem has been set read-only Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (6 != 5) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (7 != 6) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (8 != 7) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (9 != 8) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (10 != 9) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (11 != 10) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (12 != 11) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (13 != 12) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (14 != 13) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (15 != 14) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (16 != 15) Mar 4 16:31:44 Beast kernel: ata11.00: configured for UDMA/133 Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (17 != 16) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (18 != 17) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (19 != 18) Mar 4 16:31:44 Beast kernel: FAT-fs (sda1): error, clusters badly computed (20 != 19) Quote Link to comment
3ajs Posted March 12, 2020 Author Share Posted March 12, 2020 Much appreciated...replaced flash drive...replaced registration key....UI working fine with array stopped, started array, hung up network about 20 minutes later. Attached syslog from flash drive syslog (1) Quote Link to comment
JorgeB Posted March 12, 2020 Share Posted March 12, 2020 SAT2-MV8 controller keeps crashing, those controllers have issues with recent devices (both HDD and SSD) and not recommended for some time, they usually work fine with all older disks up to 2/3TB, but have issues with some newer ones, it *might* work if you disconnect the 8TB disk. Quote Link to comment
3ajs Posted March 12, 2020 Author Share Posted March 12, 2020 50 minutes ago, johnnie.black said: SAT2-MV8 controller keeps crashing, those controllers have issues with recent devices (both HDD and SSD) and not recommended for some time, they usually work fine with all older disks up to 2/3TB, but have issues with some newer ones, it *might* work if you disconnect the 8TB disk. Thanks so much for your quick reply. Is it possible to switch to a different controller? Quote Link to comment
JorgeB Posted March 13, 2020 Share Posted March 13, 2020 Yes, drives are tracked by serial number, though you'll need a PCIe controller, there aren't any good PCI-X options. Quote Link to comment
3ajs Posted March 16, 2020 Author Share Posted March 16, 2020 On 3/13/2020 at 3:30 AM, johnnie.black said: Yes, drives are tracked by serial number, though you'll need a PCIe controller, there aren't any good PCI-X options. Really appreciate your advice. Have you heard of one that works well for swapping into the Supermicro 24 bay machines? Quote Link to comment
JorgeB Posted March 16, 2020 Share Posted March 16, 2020 Any LSI with a SAS2008/2308/3008/3408 chipset in IT mode, e.g., 9201-8i, 9211-8i, 9207-8i, 9300-8i, 9400-8i, etc and clones, like the Dell H200/H310 and IBM M1015, these latter ones need to be crossflashed. Quote Link to comment
cyruspy Posted May 11, 2020 Share Posted May 11, 2020 On 3/12/2020 at 3:47 PM, johnnie.black said: SAT2-MV8 controller keeps crashing, those controllers have issues with recent devices (both HDD and SSD) and not recommended for some time, they usually work fine with all older disks up to 2/3TB, but have issues with some newer ones, it *might* work if you disconnect the 8TB disk. Fix might be available via the openSUSE guys: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/ata/sata_mv.c?id=e9f691d899188679746eeb96e6cb520459eda9b4 I assume it would hit unRAID at one point in time. Quote Link to comment
limetech Posted June 18, 2020 Share Posted June 18, 2020 On 5/11/2020 at 9:45 AM, cyruspy said: Fix might be available via the openSUSE guys: That patch is already in kernel 5.7.2 used by Unraid OS 6.9.0-beta22 2 Quote Link to comment
3ajs Posted June 26, 2020 Author Share Posted June 26, 2020 On 6/18/2020 at 5:54 PM, limetech said: That patch is already in kernel 5.7.2 used by Unraid OS 6.9.0-beta22 Does that patch allow use of larger TB drives with SAT2-MV8? Quote Link to comment
JorgeB Posted June 26, 2020 Share Posted June 26, 2020 50 minutes ago, 3ajs said: Does that patch allow use of larger TB drives with SAT2-MV8? It should, but it's not a capacity issue, there was a problem using some recent devices on that controller, it also affected some small SSDs, please test and report back. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.