hawihoney

Members
  • Content count

    390
  • Joined

  • Last visited

Community Reputation

0 Neutral

About hawihoney

  • Rank
    Advanced Member
  • Birthday

Converted

  • Gender
    Undisclosed
  1. The smart reports in my diagnostics files do contain the following error: smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.7-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org ERROR: smartctl takes ONE device name as the final command-line argument. You have provided 2 device names: /dev/sdf Use smartctl -h to get a usage summary Did attach an diagnostics file. tower2-diagnostics-20170206-1008.zip
  2. Diagnostics command tried for the first time --> error. All smartreports do contain the following error: smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.7-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org ERROR: smartctl takes ONE device name as the final command-line argument. You have provided 2 device names: /dev/sdf Use smartctl -h to get a usage summary
  3. Ok, this one is ok for me: for d in /dev/sd?; do echo "$d " "$(udevadm info --query=all --name=$d|grep ID_SERIAL_SHORT=)"|awk '{if ($1 !~ /\/dev\/sda/){system("smartctl -A "$1" > "$3".txt")}}'; done
  4. I'm looking for a combination of linux commands that will find all attached devices, call smartctl for each device and will output a file per device. To make it perfect the name of the file should include the current date and the device identification. I tried the following command but I don't find the identification like "WDC_WD60EFRX-68L0BN1_WD-WX41D95PAC13": lsblk -d -n -oNAME,RO,MODEL | grep sd Any help is highly appreciated. ***EDIT:*** A little bit further now. Now I need to parse the output and create a smartctl call for every line giving a filename of the ID_SERIAL_SHORT as filename (with awk?): for d in /dev/sd?; do echo "$d" "$(udevadm info --query=all --name=$d|grep ID_SERIAL_SHORT)"; done
  5. Here's the screenshot.
  6. Do you have the Unassigned Devices plugin installed, it is causing some shifts in the display. No docker, no VM, no plugins except NERD pack for screen - pure NAS functionality.
  7. Small GUI glitch on 6.3. When watching the main page on a small display (e.g. Android tablet with Chrome) the buttons "Spin down" and "Clear statistics" are no longer column-aligned to the buttons above (e.g. History). They move to the right a little bit. Can send a screenshot if neccessary. TIA
  8. Good guess: My children think I'm a bot... The original question is from me. I do own these two machines. Currently there are 18 drives per machine with 7 6TBs per machine. No problems so far ... Wondering what happens if I add more.
  9. Now that I have the smart reports of 18 drives in *.txt files, how can I rate them? I've got a bigger drive and would like to replace the drive that - hm, what drive? Is there some sort of application that I can feed with a bulk of smart reports and that tells me what drive to replace next? Many thanks in advance.
  10. Found additional error reports in the announcement forum here: http://lime-technology.com/forum/index.php?topic=51874.msg499005#msg499005
  11. Yes, the history seems to be wrong as well: 2016 Sep 20 06:47:46|50906|117,9 MB/s|0 Regards
  12. On my 6.2 double parity rig I had to replace a failing disk. The data rebuild took place and finished successfully. After the data rebuild the UI shows a successful parity check with that same date of the data rebuild. The data disk has not been read - just written. How can this be a successful parity check? IMHO, the UI is wrong here. A successful data rebuild has been processed, no parity check. Many thank in advance.
  13. Sorry, need to clarify: If I issue a non-correcting parity check on a dual-parity 6.2 rig and "Errors (for a disk) > 0" but "Sync errors detected = 0". Parity is still correct? Really? TIA
  14. Thanks for your answer. So for these ~2000 blocks parity could not be checked and a "rebuild" took place. Hmm, interesting.
  15. Thanks for your answer. What I don't understand: If there are sectors that could not be read on disk1, and unRAID couldn't read them, how can parity check report successful completion? I don't get that.
Copyright © 2005-2017 Lime Technology, Inc. unRAIDĀ® is a registered trademark of Lime Technology, Inc.