[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 488: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4762: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4764: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4765: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4766: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3897)
Mediasonic Forum • View topic - Enclosure resets periodically under Linux 4.3.3

Enclosure resets periodically under Linux 4.3.3

Support and Discussion for H82-SU3S2 ProBox - For PC Users

Enclosure resets periodically under Linux 4.3.3

Postby crystalkeeper » January 9th, 2016, 3:44 pm

crystalkeeper
 
Posts: 5
Joined: January 9th, 2016, 3:39 pm

Re: Enclosure resets periodically under Linux 4.3.3

Postby IceNine » January 9th, 2016, 6:01 pm

Hello Crystalkeeper,

This does look like a garden-variety disconnect.

Whenever this has happened to me in the past, it's always been the result of a failing drive. What seemed to happen - at least in my case - is when a bad block was attempted to be read or written, the drive focuses all of its efforts on retrying to read or write that block, which seems to cause a log-jam somehow. What appears to happen (I'm guessing partly) is that this causes a timeout of some sort in the jmicron USB to SATA translation process that causes it to "reset" the entire process, forcing the drives to disconnect while doing so.

My first step in troubleshooting this would be to install the Smartmon tools package on your linux distro (on debian/ubuntu, it's as simple as running 'sudo apt-get install smartmontools')

Second, I would use the package's 'smartctl' tool to perform a self-test on ALL drives in your mediasonic enclosure. Now, the jmicron chip that does the SATA translation requires a separate command line parameter to properly communicate with the drive '-d sat'. Make sure you use it. You also want to enable offline data collection and all smart-related features for your drives.

Next, you should make a note of which devices are in your enclosure (/dev/sdc, /dev/sdx, etc, or use the devices listed in /dev/disk/by-id, or /dev/disk/by-path, whatever you are most comfortable with).

Then, for each of those drives, enable all smart features (using /dev/sdx as an example):

sudo smartctl -d sat -s on -o on -S on /dev/sdx

Perform this command for all drives in your enclosure. In fact, I would perform it for all drives in your system.

Next, I would perform a long self-test on each drive in your enclosure. If a self-test fails in the middle of a test, it's fine because you already enabled offline data collection in the previous step, which means you will still be able to see the failure in the devices logs later via the smartctl command (more on that later).

Run the command below to initiate a long self-test on that particular drive (again using /dev/sdx as an example):

sudo smartctl -d sat -t long /dev/sdx

Repeat the above command with all other devices in your enclosure. You may also use the devices in /dev/disk/by-id, by-path, etc if you wish. The self-test will take some time to complete. You don't have to wait for one drive to complete the selftest to start the others. You can run the command consecutively for all drives in the enclosure, and they will all do their self-test thing.

To check the progress, or see the results of the self-test, run the following command (again, /dev/sdx being an example):

smartctl -d sat -a /dev/sdx

You should see a lot of statistics generated here. The important things to look for are obviously failed self-tests, as that shows you have an unhealthy drive.

The most damning evidence of a failing hard drive would be the "Reallocated_Sector_Ct" attribute. Every SATA disk you buy has a set of sectors allocated as "reallocation" sectors, in case a drive runs into a bad sector that it can no longer read or write. When your drive encounters one, it takes one of these spare sectors and allocates it in place of the "bad" one. Typically, once a drive starts making these allocations, a drive is on its way out. If the "RAW_VALUE" is anything but 0, you may have a drive failing on you.

If you need any help deciphering the smartctl output for your drives, feel free to post them here and I will be happy to help you decipher them.
IceNine
 
Posts: 3
Joined: October 11th, 2014, 9:56 pm

Re: Enclosure resets periodically under Linux 4.3.3

Postby crystalkeeper » January 10th, 2016, 7:32 pm

Thanks so much for the reply IceNine!

Your theory on the intermittent error makes sense and seems plausible.

I did a long self-check on all connected disks and looked at the Reallocated_Sector_Ct variable but there were no errors and it's 0 for all of my disks. It seems like the root cause may be a little bit more elusive.

Two of the disks have a non-zero Raw_Read_Error_Rate, one is "1" and the other is "35." I'll look into this variable more to see what others have said. Do you know anything about it?
crystalkeeper
 
Posts: 5
Joined: January 9th, 2016, 3:39 pm

Re: Enclosure resets periodically under Linux 4.3.3

Postby IceNine » January 11th, 2016, 3:04 pm

https://en.wikipedia.org/wiki/S.M.A.R.T ... attributes

That Attribute is mostly meaningless from what the wiki states (Note attributes in Pink). I would ignore it and look at the others. Also, I would try another cable just in case. Did you have to install any USB3 drivers under Linux, or did the included XHCI support work fine?
IceNine
 
Posts: 3
Joined: October 11th, 2014, 9:56 pm

Re: Enclosure resets periodically under Linux 4.3.3

Postby crystalkeeper » January 13th, 2016, 11:19 am

crystalkeeper
 
Posts: 5
Joined: January 9th, 2016, 3:39 pm

Re: Enclosure resets periodically under Linux 4.3.3

Postby crystalkeeper » February 9th, 2016, 8:04 pm

crystalkeeper
 
Posts: 5
Joined: January 9th, 2016, 3:39 pm


Return to H82-SU3S2 ProBox - For PC Users

Who is online

Users browsing this forum: No registered users and 1 guest