mbryanr

Members
  • Posts

    1294
  • Joined

  • Last visited

Posts posted by mbryanr

  1. When I saw your post and smart tests originally, I searched for "End to End Error" as it indicates it is "FAILING NOW" (and I have no experience with the new Seagates, and I have one waiting to be installed...)

     

     

    184 End-to-End_Error        0x0032  098  098  099    Old_age  Always  FAILING_NOW 2  (the other drive had a raw value of 7)

     

    I wouldn't trust Seatools as an indicator of a drive problem, especially if it is only reporting if the smart test "passed", which is not an indicator of a failing drive.  Usually a smart test will fail after it is too late to save your data.

     

    End-to-End Error-

    Appears to be an internal memory cache problem, although this seemed to be the most logical explanation:

    The "end-to-end" error count is the number of times the drive has detected the following problem:

    The data sent to the write mechanism did not match the data received from the computer.

     

    In other words, in means that the data was corrupted while in the drive controller. This is an electronic problem caused by an unstable processor on the drive.

     

    Theoretically, there are possibilities like bad power (or bad power connector), but this is almost always a sign of failing chips on the drive

  2. I'm with you...I'm not a big fan of the Samsung drives, but here is one of my smart reports. Normally, no reallocated or pending sectors is a good indicator.

    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
      1 Raw_Read_Error_Rate     0x002f   100   100   051    Pre-fail  Always       -       57
      2 Throughput_Performance  0x0026   252   252   000    Old_age   Always       -       0
      3 Spin_Up_Time            0x0023   067   067   025    Pre-fail  Always       -       10204
      4 Start_Stop_Count        0x0032   099   099   000    Old_age   Always       -       1342
      5 Reallocated_Sector_Ct   0x0033   252   252   010    Pre-fail  Always       -       0
      7 Seek_Error_Rate         0x002e   252   252   051    Old_age   Always       -       0
      8 Seek_Time_Performance   0x0024   252   252   015    Old_age   Offline      -       0
      9 Power_On_Hours          0x0032   100   100   000    Old_age   Always       -       2109
    10 Spin_Retry_Count        0x0032   252   252   051    Old_age   Always       -       0
    11 Calibration_Retry_Count 0x0032   252   252   000    Old_age   Always       -       0
    12 Power_Cycle_Count       0x0032   100   100   000    Old_age   Always       -       32
    181 Program_Fail_Cnt_Total  0x0022   252   252   000    Old_age   Always       -       0
    191 G-Sense_Error_Rate      0x0022   100   100   000    Old_age   Always       -       5
    192 Power-Off_Retract_Count 0x0022   252   252   000    Old_age   Always       -       0
    194 Temperature_Celsius     0x0002   064   063   000    Old_age   Always       -       19 (Min/Max 15/37)
    195 Hardware_ECC_Recovered  0x003a   100   100   000    Old_age   Always       -       0
    196 Reallocated_Event_Count 0x0032   252   252   000    Old_age   Always       -       0
    197 Current_Pending_Sector  0x0032   252   252   000    Old_age   Always       -       0
    198 Offline_Uncorrectable   0x0030   252   252   000    Old_age   Offline      -       0
    199 UDMA_CRC_Error_Count    0x0036   200   200   000    Old_age   Always       -       0
    200 Multi_Zone_Error_Rate   0x002a   100   100   000    Old_age   Always       -       3
    223 Load_Retry_Count        0x0032   252   252   000    Old_age   Always       -       0
    225 Load_Cycle_Count        0x0032   100   100   000    Old_age   Always       -       1343

     

     

    It has an error as shown below

    Error 20 occurred at disk power-on lifetime: 12311 hours (512 days + 23 hours)
      When the command that caused the error occurred, the device was active or idle.
    
      After command completion occurred, registers were:
      ER ST SC SN CL CH DH
      -- -- -- -- -- -- --
      40 51 08 40 00 3c e2  Error: UNC 8 sectors at LBA = 0x023c0040 = 37486656
    
      Commands leading to the command that caused the error were:
      CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
      -- -- -- -- -- -- -- --  ----------------  --------------------
      c8 00 08 40 00 3c e2 0a      00:00:40.214  READ DMA
      35 00 40 60 14 3b e0 0a      00:00:40.214  WRITE DMA EXT
      35 00 00 60 10 3b e0 0a      00:00:40.214  WRITE DMA EXT
      35 00 00 60 0c 3b e0 0a      00:00:40.214  WRITE DMA EXT
      25 00 40 60 14 3b e0 0a      00:00:40.214  READ DMA EXT[/quote]
    

    I would prepare to swap that drive out. Run a long smart test as well.

  3. The segfault is what I had remembered reading about -- but what you're saying is that's not an issue with 4.7 (which I what I'm running).

    I hadn't seen it reported, nor had I encountered the segfault on 4.7

    So ... this should be a "safe" sequence, right?

     

    killall emhttp

    nohup /usr/local/sbin/emhttp &

     

     

    "Safe" meaning that if it doesn't work, the array will still be running -- I'll just still not have a webGUI.

    Correct.  I remember on v5 that it gave segfault messages, but I could still telnet.

    ... and if that doesn't work, I'll just click on the "Power Down" button on Unmenu's User Scripts page, which should shut down gracefully.  [Note that I tried typing "powerdown" in a telnet window last night, but it didn't work -- but I think that was the built-in powerdown;  not the "clean powerdown" script that I think UnMenu would use].    Or do you think it's better to use the sequence described in the wiki?  [stop samba; umount all the drives one-at-a-time;  then do a mdcmd stop] ... and if so, does that actually power down, or just stop everything?

    I'd try the powerdown in unMenu, and if that doesn't work - the command line described above.  It just cleanly stops everything, at which point you can hit the power button (without incurring a parity check on reboot).

  4. You can continue to utilize the excellent unMENU (and/or SimpleFeatures) in 5.0, without those lines in your go script..they will not be reinstalled upon each reboot. None of the packages or plugins you mentioned are in the stock gui.

     

    http://lime-technology.com/forum/index.php?topic=19510.0

     

    I would be careful with duplicating packages/plugins. Particularly ones that use different versions of the same dependencies/libraries. But that is true for any package or plugin regardless if you are using unMENU or SimpleFeatures.

     

     

    If you find you need smartmontools, hdparm, etc - then stay with unMENU. There is not a plugin manager (yet); which can cause problems with startup/shutdown depending on the plugin installed.  I have not had an issue with the basic SimpleFeatures plugins (I don't use webserver or sleep).

     

     

     

     

     

     

     

     

     

  5. Correct. 11a was an interim release to test specific errors for a couple users.

     

     

    Changes from 5.0-rc11 to 5.0-rc11a
    ----------------------------------
    - shfs: return correct extended attribute value length
    - webGui: for 'FTP user(s)', permit multiple usernames separated by spaces
    
    Changes from 5.0-rc10 to 5.0-rc11
    ---------------------------------
    - emhttp: fixed spurious "title not found" log entries
    - emhttp: ensure new parity disk for 'swap disable' has a valid partition table
    - emhttp: fixed worker thread (format/clear/copy) inconsistent progress
    - emhttp: default timeZone "America/Los_Angeles" (eliminate first-boot error message)
    - flash boot: add menu item to boot kernel limiting memory use to 4GB
    - linux: use kernel 3.4.26 (for various disk controller and NIC driver bug fixes)
    - linux: added "Intel PIIX4 and compatible I2C driver" (i2c-piix4) per user request
    - linux: changed cpufreq drivers from modules to built-ins
    - shfs: fixed crash by replacing non-thread-safe readdir() with readdir_r()
    - shfs: use st_ino field to record object disk location
    - slack: add 10-sec timeout waiting for USB flash to appear as suggested by forum user Barzija
    - webGui: added very simple vsftp support
    - webGui: indexer: diplay disk location of objects

  6. I hate to post regarding something so simple, but I am not able to download 5.0 rc11. I click on the Download link on the first post in this thread and I get a 404 file not found message. Just for grins, I tried the same thing for 4.7 package and got the same 404 results.

     

    Are these files moved somewhere else or are they just down at the moment?

     

    I just tried the link as well. No go.

     

    This works though:

    http://download.lime-technology.com/download/