October 16, 20169 yr Hi I've been stopping and starting my new array a lot as I start playing with it. I'm finding that most of the time, when I attempt to stop the array, the GUI becomes unresponsive. As expected on stopping array, the array shares become unavailable, flash drive and unassigned devices are still mounted. CLI can still be accessed. No parity or other issues evident with array on restarting via CLI. Any advice? Latest log attached. Thanks. storage-diagnostics-20161016-1810.zip
October 20, 20169 yr Author Hi, bit disappointed by the lack of response. Is there another way I can get support?
October 20, 20169 yr Community Expert Read through this thread. https://lime-technology.com/forum/index.php?topic=51983.0 If you really need a solution now, you can download the 6.3.0-rc2 release. You can find it here: http://lime-technology.com/forum/index.php?topic=52917.0
October 20, 20169 yr Hi I've been stopping and starting my new array a lot as I start playing with it. I'm finding that most of the time, when I attempt to stop the array, the GUI becomes unresponsive. As expected on stopping array, the array shares become unavailable, flash drive and unassigned devices are still mounted. CLI can still be accessed. No parity or other issues evident with array on restarting via CLI. Any advice? Latest log attached. Thanks. What do you mean "restarting via CLI"? Start/Stop can take a while with docker and VM's running. Once you click Start or Stop button let the browser sit there awhile before you decide it's hung.
October 20, 20169 yr I only looked at your syslog but I think your problem may be related to this: Oct 10 21:58:57 storage kernel: ata6.00: ATA-8: OCZ-VERTEX PLUS R2, 482VF6ZPM62ZURU9KDEJ, 1.2, max UDMA/133 ... Oct 10 22:11:20 storage kernel: ata6: hard resetting link Oct 10 22:11:20 storage kernel: ata6: SATA link down (SStatus 0 SControl 300) Oct 10 22:11:20 storage kernel: ata6: limiting SATA link speed to 1.5 Gbps Oct 10 22:11:25 storage kernel: ata6: hard resetting link Oct 10 22:11:26 storage emhttp: err: ckmbr: read: Input/output error Oct 10 22:11:26 storage emhttp: device /dev/sdf problem getting size Oct 10 22:11:26 storage kernel: ata6: SATA link down (SStatus 0 SControl 310) Oct 10 22:11:26 storage kernel: ata6.00: disabled Oct 10 22:11:26 storage kernel: ata6: EH complete Oct 10 22:11:26 storage kernel: ata6.00: detaching (SCSI 7:0:0:0) Your SSD's controller is losing contact with the SSD and it's resetting the SATA link. Check the cable, though it might be a dying SSD or controller. If that's your cache disk and you're running Docker, it's going to cause freezes if the disk drops offline.
October 20, 20169 yr Author Read through this thread. https://lime-technology.com/forum/index.php?topic=51983.0 ... Thanks but this occurs when stopping the array, not on attempting to power it down., so I don't think it's relevant?
October 20, 20169 yr Author What do you mean "restarting via CLI"? Start/Stop can take a while with docker and VM's running. Once you click Start or Stop button let the browser sit there awhile before you decide it's hung. I meant using command line 'powerdown'. It definitely hung. When all works well, with the couple of Dockers I have running, it takes a only a minute or so, and there's a series of messages at the bottom of the screen which update to tell you what's happening.
October 20, 20169 yr Author I only looked at your syslog but I think your problem may be related to this: Oct 10 21:58:57 storage kernel: ata6.00: ATA-8: OCZ-VERTEX PLUS R2, 482VF6ZPM62ZURU9KDEJ, 1.2, max UDMA/133 ... Your SSD's controller is losing contact with the SSD and it's resetting the SATA link. Check the cable, though it might be a dying SSD or controller. If that's your cache disk and you're running Docker, it's going to cause freezes if the disk drops offline. Interesting. In fact that SSD is an Unassigned Device that I'd physically installed and pre-cleared OK, in preparation for using as cache, but had pretty much decided to instead use that last remaining slot for another storage HD for now. I don't have any cache drive. I will fiddle with cables and retest, and also retest with the SSD removed. Now I think about it, I had noticed odd delays sometimes showing the content of the Unassigned Devices pane. Many thanks for your advice.
Archived
This topic is now archived and is closed to further replies.