thestewman

Members
  • Posts

    184
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

thestewman's Achievements

Apprentice

Apprentice (3/14)

1

Reputation

  1. I am having difficulty running the Smart report. It states drive is enabled but no report appears so I aborted each attempt. I note this but no idea how to change it Selective Self-tests/Logging not supported smartctl 6.2 2013-07-26 r3841 [x86_64-linux-4.1.18-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Indilinx Barefoot_2/Everest/Martini based SSDs Device Model: OCZ-VERTEX4 Serial Number: OCZ-53SM9JJ5AL5I2VDY LU WWN Device Id: 5 e83a97 bfc4e30b5 Firmware Version: 1.5 User Capacity: 512,110,190,592 bytes [512 GB] Sector Size: 512 bytes logical/physical Rotation Rate: Solid State Device Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Wed Nov 30 22:27:28 2016 CST SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 25) The self-test routine was aborted by the host. Total time to complete Offline data collection: ( 0) seconds. Offline data collection capabilities: (0x1d) SMART execute Offline immediate. No Auto Offline data collection support. Abort Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. No Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x00) Error logging NOT supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 0) minutes. Extended self-test routine recommended polling time: ( 0) minutes. SMART Attributes Data Structure revision number: 18 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x0000 006 000 000 Old_age Offline - 6 3 Spin_Up_Time 0x0000 100 100 000 Old_age Offline - 0 4 Start_Stop_Count 0x0000 100 100 000 Old_age Offline - 0 5 Reallocated_Sector_Ct 0x0000 100 100 000 Old_age Offline - 6 9 Power_On_Hours 0x0000 100 100 000 Old_age Offline - 27229 12 Power_Cycle_Count 0x0000 100 100 000 Old_age Offline - 152 232 Lifetime_Writes 0x0000 100 100 000 Old_age Offline - 65831649656 233 Media_Wearout_Indicator 0x0000 099 000 000 Old_age Offline - 99 SMART Error Log not supported SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Aborted by host 90% 0 - # 2 Short offline Aborted by host 90% 0 - # 3 Short offline Aborted by host 90% 0 - # 4 Extended offline Aborted by host 90% 0 - # 5 Short offline Aborted by host 90% 0 - # 6 Short offline Aborted by host 90% 0 - Selective Self-tests/Logging not supported
  2. Would you consider this bad enough to replace the cache SSD drive ? What else should I be looking for or correcting ? unRAID Cache disk SMART health [5]: 11-28-2016 12:15 AM Warning [TOWER] - reallocated sector ct is 6 OCZ-VERTEX4_OCZ-53SM9JJ5AL5I2VDY (sdb)
  3. That's is an easy one. There are "?" in the file name. Your question should be "Why are there "?" in the file name?" Device model: WDC WD10EADS-00L5B1 Serial number: WD-WCAU48551976 Looks like the plugin is attempting to underline the dashes in the serial number and text ?
  4. Can you tell me what this error message means? Running v6.1.9 and preclear ran to completion ??> RESULT: Preclear finished succesfully. /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1401: /boot/preclear_reports/preclear_report_WD?WCAU48551976_2016.08.3 1?02:47:53.txt: Invalid argument root@Tower:/usr/local/emhttp#
  5. Same problem I first stopped a Windows 7 VM and one Docker, Logitech Media Server I then upgraded to 6.2rc3 I can stop the system and assign an empty precleared/formatted 8TB HD that is in disc position 6 for the #2 parity. Since you cannot move 2 drives without a reconfiguration and I wanted to replace the empty #2 Parity drive position #6 I went to Tools Reconfig to assign another empty precleared/formatted 6tb HDD frrom position 16 to position 6 the position that was 8tb #2 parity drive. I assigned all the remaining drives and then went to stop to reboot after running reconfig. Unraid then enters into an never ending umounting disk loop and will not stop and is hung in that state. I can reboot using IPMI or the hard Reboot button on the case and it enters into the same unmounting disk loop when I try to stop and reboot I then have to temporarily load 6.1.9 again with a different flash drive to be able to use the server I ran Open Files and nothing is open I also ran Open file to stop all processes. No processes running How do I determine what is preventing Unraid from stopping. I now have new shares, Domains, ISOS, and System now in my shares tab for 6.1.9 The only thing I observed different is when stopping during 6.1.9 libvirt is the second item stopping and I don't see it stopping when stopping 6.2.0-rc3. I could not capture a Diagnostics log with the system hung at stopping. There is one for 6.1.9 attached tower-diagnostics-20160729-2103.zip
  6. Can you please post the fix. Thank you
  7. Isn't what he is asking is that he cannot see the Tower in Windows Explorer not the GUI. A common problem with Windows 10
  8. Any idea why one merchandiser would have higher failure rates than another with the same hard drive manufacturer ?
  9. Recently ran the Fix Common Problems plugin and the following were noted as problems. The LogitechMediaServer docker runs perfectly as installed so are these all false positives ? Docker Application LogitechMediaServer is currently set up to run in host mode The template for this application specifies that the application should run in bridge mode. Docker Application LogitechMediaServer, Container Port 3483 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Docker Application LogitechMediaServer, Container Port 3483 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Docker Application LogitechMediaServer, Container Port 9000 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. Docker Application LogitechMediaServer, Container Port 9090 not found or changed on installed application When changing ports on a docker container, you should only ever modify the HOST port, as the application in question will expect the container port to remain the same as what the template author dictated. LogitechMediaServer docker application has its /config folder set to /mnt/user/appdata/LogitechMediaServer Many (if not most docker applications) will not function correctly if their appData folder is set to a user share. Ideally, they should be set to a disk share. Either /mnt/cache/... or /mnt/diskX/...
  10. The time you waited after the writes doesn't matter. What you described in your initial post is NOT the same as doing a New Config -- i.e. you said "... It appears that I just need to stop the array and select the "parity is already valid" checkbox next to the start button and start it up. I see no checkbox there (or anywhere on the web gui). The disk is still marked with a red X (device is disabled)." That's because you simply replaced the disk and then looked for a "parity is already valid" checkbox => but did NOT do a New Config. The "parity is already valid" choice ONLY applies to new configurations ... and should only be used if you're CERTAIN that's the case. In your post you noted that with the disk out, "... Everything runs fine! Woo!", and that you had rebooted a few times, etc. Based on those comments trurl correctly noted that "... Your description is not sufficiently detailed to assure me that your parity is actually in sync ...". If you had definitely NOT done any writes to the array while the disk was out then you could in fact have simply done a New Config and checked the "already valid" box and all would have been fine. You basically repeated the test today ... but this time you in fact did a New Config -- so you got the "already valid" choice. How long you waited after the writes is completely irrelevant ... you could have done it immediately after you finished. So as a newer user of Unraid without a lot of background in software I would like to ask this question. Or maybe I clearly don't understand his method he described of removing the HDD. "Hi! I just got my new unraid server (v. 6.1.9) up and running with shares, and I copied a bunch of data onto it. I have a hot-swappable rack server with 4 8TB drives, so I thought I should test to make sure unraid does what it says it does, so I popped out the drive that had the most data on it. Everything runs fine! Woo!" He has a hot -swappable rack server and he states he just pulls a data drive. He does this without taking the system off-line or shutting it down ? Is this correct method of pulling a drive ? How can the system be accessed without the data drive ?
  11. Many, many, many threads about this in this forum (and the internet in general with regards to other NAS devices) My failsafe solution is to simply navigate to the server in the explorer address bar, then pin the server to the quick access section. Simple, and never fails. Personally, after doing this, I really don't care if the server doesn't show up in the Network section. I know this sounds stupid but I can't figure out how to do what you are recommending. Could you please do it step by step for a dummy.
  12. Parity finished with no errors. Rebooted system and it now starts on the Main page as expected
  13. Good idea and will be the first thing I do when it finishes the parity check. With an 8tb parity HDD past the 1/2 way point I don't want to interrupt it
  14. I am using v6.1.9 and this is occurring with any browser so it is not the auto complete action. I purchased a new registration today to use a new flash drive and after registering the GUI opening page is always stuck on registration so it is something in the OS.
  15. System probably isn't recognizing your key file. Do you have it stored in the config folder on the flash drive? Same flash drive that it was registered against? Post Diagnostics Sorry if my question was worded improperly. My system is correctly registered, starts, and is currently performing a parity check. The key file is in the config folder. Its the opening page that is stuck opening at http://192.168.1.58/registration when I enter http//192.168.1.58 instead of the Main page