July 7, 201312 yr Second screenshot with array started and no drive temp, Disk17 (sdp) FYI, BTW, I used to have a disk8,9,10 a while back, once I removed them and cleared the config, I still get the entries "Not installed" in the webgui, this used to not happen back in the days when one cleared the drive configuration. You would not get "Not installed" entries in the WebGui. Forgot to mention this oddity a while back.
July 7, 201312 yr Just tried to spin down drives, then spin up drives, choked on spin up command on drive 17 (sdp) Jul 6 23:07:47 Tower kernel: sd 0:0:13:0: attempting task abort! scmd(f1d01f00) Jul 6 23:07:47 Tower kernel: sd 0:0:13:0: [sdp] CDB: Jul 6 23:07:47 Tower kernel: cdb[0]=0x12: 12 00 00 00 24 00 Jul 6 23:07:47 Tower kernel: scsi target0:0:13: handle(0x0017), sas_address(0x5001517e85bfcfe8), phy( Jul 6 23:07:47 Tower kernel: scsi target0:0:13: enclosure_logical_id(0x5001517e85bfcfff), slot( Jul 6 23:07:48 Tower kernel: sd 0:0:13:0: task abort: SUCCESS scmd(f1d01f00) Jul 6 23:07:48 Tower kernel: sd 0:0:13:0: attempting task abort! scmd(f116e0c0) Jul 6 23:07:48 Tower kernel: sd 0:0:13:0: [sdp] CDB: Jul 6 23:07:48 Tower kernel: cdb[0]=0x85: 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e3 00 Jul 6 23:07:48 Tower kernel: scsi target0:0:13: handle(0x0017), sas_address(0x5001517e85bfcfe8), phy( Jul 6 23:07:48 Tower kernel: scsi target0:0:13: enclosure_logical_id(0x5001517e85bfcfff), slot( Jul 6 23:07:48 Tower kernel: sd 0:0:13:0: task abort: SUCCESS scmd(f116e0c0) Jul 6 23:07:58 Tower kernel: sd 0:0:13:0: attempting task abort! scmd(f1d01f00) Jul 6 23:07:58 Tower kernel: sd 0:0:13:0: [sdp] CDB: Jul 6 23:07:58 Tower kernel: cdb[0]=0x0: 00 00 00 00 00 00 Jul 6 23:07:58 Tower kernel: scsi target0:0:13: handle(0x0017), sas_address(0x5001517e85bfcfe8), phy( Jul 6 23:07:58 Tower kernel: scsi target0:0:13: enclosure_logical_id(0x5001517e85bfcfff), slot( Jul 6 23:07:58 Tower kernel: sd 0:0:13:0: task abort: SUCCESS scmd(f1d01f00) Jul 6 23:07:58 Tower kernel: scsi target0:0:13: attempting device reset! scmd(f1d01f00) Jul 6 23:07:58 Tower kernel: sd 0:0:13:0: [sdp] CDB: Jul 6 23:07:58 Tower kernel: cdb[0]=0x12: 12 00 00 00 24 00 Jul 6 23:07:58 Tower kernel: scsi target0:0:13: handle(0x0017), sas_address(0x5001517e85bfcfe8), phy( Jul 6 23:07:58 Tower kernel: scsi target0:0:13: enclosure_logical_id(0x5001517e85bfcfff), slot( Jul 6 23:07:58 Tower kernel: sd 0:0:13:0: device reset: SUCCESS scmd(f1d01f00) Jul 6 23:07:58 Tower kernel: md: disk17: ATA_OP e3 ioctl error: -22 Jul 6 23:07:58 Tower kernel: program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO Syslog attached, continuation from above syslog, Jul 6 23:06:48 is when I started the spin down of all drives. http://lime-technology.com/forum/index.php?topic=17508.0 smartctl smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net I think we are a bit behind on the smartmontools, no? syslog_sindownthenup.txt
July 7, 201312 yr Forgive my confusion. I'm not sure if you answered my question. Since you don't understand english upgradepkg --install-new smartmontools-5.43-i486-1.txz +============================================================================== | Installing new package ./smartmontools-5.43-i486-1.txz +============================================================================== Verifying package smartmontools-5.43-i486-1.txz. Installing package smartmontools-5.43-i486-1.txz: PACKAGE DESCRIPTION: # smartmontools (hard drive monitoring utilities) # # SMARTMONTOOLS contains utilities that control and monitor storage # devices using the Self-Monitoring, Analysis and Reporting Technology # (S.M.A.R.T.) system build into ATA and SCSI Hard Drives. This is used # to check the reliability of the hard drive and to predict drive # failures. SMARTMONTOOLS Version 5.x is designed to comply to the # ATA/ATAPI-5 specification (Revision 1). Future releases of # SMARTMONTOOLS (Versions 6.x and 7.x) will comply with the ATA/ATAPI-6 # and ATA/ATAPI-7 specifications. # Executing install script for smartmontools-5.43-i486-1.txz. Package smartmontools-5.43-i486-1.txz installed. smartctl smartctl 5.43 2012-06-30 r3573 [i686-linux-3.9.6p-unRAID] (local build) Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net Same crap upon attempt to spin up drives, chokes on disk 17 "program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO"
July 7, 201312 yr So no, installing a more recent smartmontools doesn't make your problem go away. Then bringing up that smartmontools is old only distracts from your particular problem. 5.43 is not the most recent UnRaid may use smartmontools to read disk temperatures, but it certainly does not use smartmontools to spin up drives. For what I know it doesn't use hdparm for that either. It rather relies on some custom disk spin up functionality in the md-mod driver. Really, are you sure about that?
July 7, 201312 yr The only thing I am thinking right now is something changed... but to weed this out some more, I will need to downgrade back to RC15a tomorrow and see if I get the same behaviour as I did this evening on RC16c. Even though prior to the upgrade this evening I didn't have this behaviour on RC15a. And I didn't physically touch the server in any manner (cables, drives, etc...). This will display if anything physically went south and just a stroke of bad luck (cable, driver, etc...) while upgrading. If you wish to compile 6.1 in your spare time, I would try it, once I downgrade and see if this is a non-issue in RC15a. If so, then its worth trying an upgraded version of smartmontools under RC16c to see what's the deal then. 5.10 of smartmontools is old thought, and that is a fact. Think about this for a moment, I issued a spin up via webgui, it ends with the following line "program smartctl is using a deprecated SCSI ioctl, please convert it to SG_IO", I didn't issue a smartctl command, I clicked the "spin up" button... I got these 2TB drives all around the same time: Disk#17 smartctl -a -A /dev/sdp smartctl 5.43 2012-06-30 r3573 [i686-linux-3.9.6p-unRAID] (local build) Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 5K3000 Device Model: Hitachi HDS5C3020ALA632 Serial Number: ML0220F312HMWD LU WWN Device Id: 5 000cca 369cf3af6 Firmware Version: ML6OA580 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Jul 7 00:03:23 2013 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Error SMART Values Read failed: scsi error aborted command Smartctl: SMART Read Values failed. === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. Error SMART Error Log Read failed: scsi error aborted command Smartctl: SMART Error Log Read Failed Error SMART Error Self-Test Log Read failed: scsi error aborted command Smartctl: SMART Self Test Log Read Failed Device does not support Selective Self Tests/Logging Disk#16 smartctl -a -A /dev/sdr smartctl 5.43 2012-06-30 r3573 [i686-linux-3.9.6p-unRAID] (local build) Copyright © 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 5K3000 Device Model: Hitachi HDS5C3020ALA632 Serial Number: ML0220F30W5GND LU WWN Device Id: 5 000cca 369cc5a90 Firmware Version: ML6OA580 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4 Local Time is: Sun Jul 7 00:08:18 2013 EDT 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: (0x80) Offline data collection activity was never started. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (23306) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 389) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. 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 0x000b 100 100 016 Pre-fail Always - 0 2 Throughput_Performance 0x0005 133 133 054 Pre-fail Offline - 104 3 Spin_Up_Time 0x0007 137 137 024 Pre-fail Always - 400 (Average 400) 4 Start_Stop_Count 0x0012 100 100 000 Old_age Always - 1768 5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 067 Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 146 146 020 Pre-fail Offline - 29 9 Power_On_Hours 0x0012 099 099 000 Old_age Always - 10647 10 Spin_Retry_Count 0x0013 100 100 060 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 49 192 Power-Off_Retract_Count 0x0032 099 099 000 Old_age Always - 1768 193 Load_Cycle_Count 0x0012 099 099 000 Old_age Always - 1768 194 Temperature_Celsius 0x0002 176 176 000 Old_age Always - 34 (Min/Max 18/36) 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.
July 7, 201312 yr server been running rc16c now for 22 hours, no issues. Parity check completed with; Last checked on Sat Jul 6 13:13:04 2013 PDT (yesterday), finding 0 errors. > Duration: 12 hours, 48 minutes, 56 seconds. Average speed: 65.0 MB/sec All good so far.
July 7, 201312 yr So far have run nearly 24 hours on rc16c with ZERO ISSUES!!! Well done, Tom - it appears my transport's ends are well connected
July 7, 201312 yr Happy with the new release! Apart from some AFP issues, which can be resolved when moving to latest netatalk, the FUSE issues have been fixed. Cheers!
July 7, 201312 yr Happy with the new release! Apart from some AFP issues, which can be resolved when moving to latest netatalk, the FUSE issues have been fixed. Cheers! What AFP issues? What does adding the netalk fix for you? I do have a imac that use TimeMachine to save to my unraid. I think it's working fine. I will go confirm now, after reading this.
July 7, 201312 yr Happy with the new release! Apart from some AFP issues, which can be resolved when moving to latest netatalk, the FUSE issues have been fixed. Cheers! What AFP issues? What does adding the netalk fix for you? I do have a imac that use TimeMachine to save to my unraid. I think it's working fine. I will go confirm now, after reading this. I'm getting random disconnects when dealing with a copy of thousands of files. I've confirmed that Netatalk 2 is the culprit on some other servers I have, Netatalk 3 fixed many issues. I presume the same problems exist with the current version of unRAID. This isn't a deal breaker, as using SMB works just fine for that situation right now. To clarify, Time Machine and AFP works fine for the average home user (like my unRAID server at home).
July 7, 201312 yr All seems fine after a couple days of copying to/from under various loads; ran two parity checks (one with, one without Cache_Dirs active) with results within 30 seconds of last couple versions (7:41 without, 7:44 with ... a speed of 107MB/Sec). Writes in the low 30's, reads ~110MB/s. Definitely looking good for a v5.0
July 7, 201312 yr Parity Check is at 45% and running fine. Looking at the Syslog I do see the following WARNING that is new - i.e. I didn't receive it on RC12a. Jul 6 20:29:47 NAS-03 emhttp: Start AVAHI... (Other emhttp) Jul 6 20:29:47 NAS-03 emhttp: shcmd (: /etc/rc.d/rc.avahidaemon start |$stuff$ logger (Other emhttp) Jul 6 20:29:47 NAS-03 logger: Starting Avahi mDNS/DNS-SD Daemon: /usr/sbin/avahi-daemon -D Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: Found user 'avahi' (UID 61) and group 'avahi' (GID 214). Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: Successfully dropped root privileges. Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: avahi-daemon 0.6.31 starting up. Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns! (Minor Issues) Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: Successfully called chroot(). Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: Successfully dropped remaining capabilities. Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: Loading service file /services/smb.service. Jul 6 20:29:47 NAS-03 avahi-daemon[1877]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.63. (Network) TheWombat
July 7, 201312 yr I'm getting random disconnects when dealing with a copy of thousands of files. Just for kicks, can you get the same disconnects when you boot that server with less than 4gb ram? Server is configured with 4GB of ram. Do you mean drop it below 4GB and test?
July 7, 201312 yr Nice work Tom. This is feeling like it will never end though with these RC's. I agree with earlier comments that dual parity should be a priority over other things we can already achieve via plugins like UPS/Email support. Otherwise, it would be good to see this thread stay on topic of testing this RC16C release with no addons.
July 7, 201312 yr ... I agree with earlier comments that dual parity should be a priority over other things we can already achieve via plugins like UPS/Email support. ... Lets fork that thought cause i could not disagree more
July 7, 201312 yr If you wish to compile 6.1 in your spare time, I would try it Done. File size came to 216KB, and this forum allows attachments up to 192KB PER-POST, so I had to split it in two pieces. If you can't put it together, PM me an email where I can send a whole .txz. smartctl -a -A /dev/sdr Btw, what's with that "-A"? Can't a `smartctl -a /dev/sdr` do it? ---- Edit: Posting error: "You cannot upload that type of file. The only allowed extensions are txt,doc,pdf,jpg,gif,mpg,png,zip,conf,cfg." So I just added a ".zip" ending manually to both files. Never mind that. Very thankful for this! I decided to upgrade the smartmontools first since the server is still on RC16a since last night and see if there was any difference. First, no more errors being logged to syslog upon clicking "spin up" drives. WebGui immediately responsive now, amazingly fast like never before!!!(no reboot, server has been up since the upgrade last night), so the change from SCSI ioctl to utilizing SG_IO made a large difference in various aspects. One can only wonder why we would not want to update this. Drive#17 still not showing temp thought. Also a greater level of detail with smartmontools 6.1 Disk#17 smartctl -a -A /dev/sdp Red = new data complements of updated smartmontools Blue = data I was not able to get back from this (will call it troubled drive for now) drive via previous smartmontools, but updated smartmontools is able to parse. smartctl 6.1 2013-03-16 r3800 [i686-linux-3.9.6p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Hitachi Deskstar 5K3000 Device Model: Hitachi HDS5C3020ALA632 Serial Number: ML0220F312HMWD LU WWN Device Id: 5 000cca 369cf3af6 Firmware Version: ML6OA580 User Capacity: 2,000,398,934,016 bytes [2.00 TB] Sector Size: 512 bytes logical/physical Rotation Rate: 5940 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS T13/1699-D revision 4 SATA Version is: SATA 2.6, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sun Jul 7 12:26:46 2013 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled Read SMART Thresholds failed: scsi error aborted command === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: UNKNOWN! SMART Status, Attributes and Thresholds cannot be read. General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (21777) seconds. Offline data collection capabilities: (0x5b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. No Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 1) minutes. Extended self-test routine recommended polling time: ( 363) minutes. SCT capabilities: (0x003d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. 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 0x000b 100 100 --- Pre-fail Always - 0 2 Throughput_Performance 0x0005 136 136 --- Pre-fail Offline - 95 3 Spin_Up_Time 0x0007 136 136 --- Pre-fail Always - 402 (Average 402) 4 Start_Stop_Count 0x0012 100 100 --- Old_age Always - 1004 5 Reallocated_Sector_Ct 0x0033 100 100 --- Pre-fail Always - 0 7 Seek_Error_Rate 0x000b 100 100 --- Pre-fail Always - 0 8 Seek_Time_Performance 0x0005 146 146 --- Pre-fail Offline - 29 9 Power_On_Hours 0x0012 099 099 --- Old_age Always - 8929 10 Spin_Retry_Count 0x0013 100 100 --- Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 --- Old_age Always - 47 192 Power-Off_Retract_Count 0x0032 099 099 --- Old_age Always - 1650 193 Load_Cycle_Count 0x0012 099 099 --- Old_age Always - 1650 194 Temperature_Celsius 0x0002 206 206 --- Old_age Always - 29 (Min/Max 18/36) 196 Reallocated_Event_Count 0x0032 100 100 --- Old_age Always - 0 197 Current_Pending_Sector 0x0022 100 100 --- Old_age Always - 0 198 Offline_Uncorrectable 0x0008 100 100 --- Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x000a 200 200 --- Old_age Always - 0 Read SMART Error Log failed: scsi error aborted command Read SMART Self-test Log failed: scsi error aborted command Read SMART Selective Self-test Log failed: scsi error aborted command So how are temps being collected? '194 Temperature_Celsius' was not obtainable via smartmontools 5.10, is with 6.1 (for this one particular drive) Drive#17 hdparm -I /dev/sdp /dev/sdp: ATA device, with non-removable media Model Number: Hitachi HDS5C3020ALA632 Serial Number: ML0220F312HMWD Firmware Revision: ML6OA580 Transport: Serial, ATA8-AST, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6; Revision: ATA8-AST T13 Project D1697 Revision 0b Standards: Used: unknown (minor revision code 0x0029) Supported: 8 7 6 5 Likely used: 8 Configuration: Logical max current cylinders 16383 16383 heads 16 16 sectors/track 63 63 -- CHS current addressable sectors: 16514064 LBA user addressable sectors: 268435455 LBA48 user addressable sectors: 3907029168 Logical Sector size: 512 bytes Physical Sector size: 512 bytes device size with M = 1024*1024: 1907729 MBytes device size with M = 1000*1000: 2000398 MBytes (2000 GB) cache/buffer size = 26129 KBytes (type=DualPortCache) Form Factor: 3.5 inch Nominal Media Rotation Rate: 5940 Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, no device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 Advanced power management level: disabled DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 udma5 *udma6 Cycle time: min=120ns recommended=120ns PIO: pio0 pio1 pio2 pio3 pio4 Cycle time: no flow control=120ns IORDY flow control=120ns Commands/features: Enabled Supported: * SMART feature set Security Mode feature set * Power Management feature set * Write cache * Look-ahead * Host Protected Area feature set * WRITE_BUFFER command * READ_BUFFER command * NOP cmd * DOWNLOAD_MICROCODE Advanced Power Management feature set Power-Up In Standby feature set * SET_FEATURES required to spinup after power up SET_MAX security extension * 48-bit Address feature set * Device Configuration Overlay feature set * Mandatory FLUSH_CACHE * FLUSH_CACHE_EXT * SMART error logging * SMART self-test Media Card Pass-Through * General Purpose Logging feature set * WRITE_{DMA|MULTIPLE}_FUA_EXT * 64-bit World wide name * URG for READ_STREAM[_DMA]_EXT * URG for WRITE_STREAM[_DMA]_EXT * WRITE_UNCORRECTABLE_EXT command * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE unknown 119[7] * Gen1 signaling speed (1.5Gb/s) * Gen2 signaling speed (3.0Gb/s) * Gen3 signaling speed (6.0Gb/s) * Native Command Queueing (NCQ) * Host-initiated interface power management * Phy event counters * NCQ priority information Non-Zero buffer offsets in DMA Setup FIS * DMA Setup Auto-Activate optimization Device-initiated interface power management In-order data delivery * Software settings preservation * SMART Command Transport (SCT) feature set * SCT LBA Segment Access (AC2) * SCT Error Recovery Control (AC3) * SCT Features Control (AC4) * SCT Data Tables (AC5) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count not supported: enhanced erase 480min for SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 5000cca369cf3af6 NAA : 5 IEEE OUI : 000cca Unique ID : 369cf3af6 Checksum: correct Lets run a test manually, check drive temp, state. Then spin up, check state, spin down, check state hdparm -H /dev/sdp /dev/sdp: drive temperature (celsius) is: 30 drive temperature in range: yes hdparm -C /dev/sdp /dev/sdp: drive state is: standby hdparm -S0 /dev/sdp /dev/sdp: setting standby to 0 (off) hdparm -C /dev/sdp /dev/sdp: drive state is: active/idle hdparm -C /dev/sdp /dev/sdp: drive state is: active/idle hdparm -y /dev/sdp /dev/sdp: issuing standby command hdparm -C /dev/sdp /dev/sdp: drive state is: standby Still no drive temp for this drive in the WebGUI... SO 1) update smartmontools 6.1 can read temp value 2) hdparm 9.37 gets temp value as well 3) Can't obtain/read SMART logs from this one particular drive, other data/attributes are obtainable via update smartmontools 4) WebGUI doesn't display temp for this one drive, still xnas can you compile hdparm 9.43, please, when you have a moment of free time? Would like to try something with the update version of hdparm as well.
July 7, 201312 yr ... I agree with earlier comments that dual parity should be a priority over other things we can already achieve via plugins like UPS/Email support. ... Lets fork that thought cause i could not disagree more This isn't the thread to do it so I apologize, but since others chose this venue to argue the point... I agree with NAS. I am totally against dual parity and the like before UPS and email support. Back on topic. I tried rc16c and it worked good for me. Hope no other major bugs are found and it becomes Final.
July 7, 201312 yr I made the switch to rc16c today. Looking at my syslog, there are two things that didn't happen with rc12a. Firstly there seem to be memory problems? At least unmenu highlights them in red: Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Jul 7 19:18:01 lafiel kernel: [mem 0x00000000-0x000fffff] page 4k Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Jul 7 19:18:01 lafiel kernel: [mem 0x37800000-0x379fffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Jul 7 19:18:01 lafiel kernel: [mem 0x34000000-0x377fffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff] Jul 7 19:18:01 lafiel kernel: [mem 0x00100000-0x001fffff] page 4k Jul 7 19:18:01 lafiel kernel: [mem 0x00200000-0x1fffffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x20200000-0x33ffffff] Jul 7 19:18:01 lafiel kernel: [mem 0x20200000-0x33ffffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Jul 7 19:18:01 lafiel kernel: [mem 0x37a00000-0x37bfdfff] page 4k and then there are problems when I make the system sleep: Jul 7 19:51:52 lafiel kernel: ------------[ cut here ]------------ Jul 7 19:51:52 lafiel kernel: WARNING: at drivers/pci/pci.c:1393 pci_disable_device+0x50/0x79() (Minor Issues) Jul 7 19:51:52 lafiel kernel: Hardware name: To Be Filled By O.E.M. Jul 7 19:51:52 lafiel kernel: Device mpt2sas (Drive related) Jul 7 19:51:52 lafiel kernel: disabling already-disabled device Jul 7 19:51:52 lafiel kernel: Modules linked in: w83627ehf hwmon_vid md_mod sg mpt2sas i2c_i801 i2c_core scsi_transport_sas raid_class ahci libahci r8168(O) coretemp hwmon (Drive related) Jul 7 19:51:52 lafiel kernel: Pid: 2075, comm: kworker/u:2 Tainted: G O 3.9.6p-unRAID #23 (Errors) Jul 7 19:51:52 lafiel kernel: Call Trace: (Errors) Jul 7 19:51:52 lafiel kernel: [<c1029269>] warn_slowpath_common+0x77/0x8e (Errors) Jul 7 19:51:52 lafiel kernel: [<c1276a75>] ? pci_disable_device+0x50/0x79 (Errors) Jul 7 19:51:52 lafiel kernel: [<c1276a75>] ? pci_disable_device+0x50/0x79 (Errors) Jul 7 19:51:52 lafiel kernel: [<c10292fc>] warn_slowpath_fmt+0x2e/0x30 (Errors) Jul 7 19:51:52 lafiel kernel: [<c1276a75>] pci_disable_device+0x50/0x79 (Errors) Jul 7 19:51:52 lafiel kernel: [<f8570107>] _scsih_suspend+0x79/0x8c [mpt2sas] (Errors) Jul 7 19:51:52 lafiel kernel: [<c12779f1>] pci_legacy_suspend+0x24/0x9e (Errors) Jul 7 19:51:52 lafiel kernel: [<c1277e78>] pci_pm_suspend+0x31/0xe1 (Errors) Jul 7 19:51:52 lafiel kernel: [<c12e0eb9>] ? device_pm_wait_for_dev+0x1b/0x1b (Errors) Jul 7 19:51:52 lafiel kernel: [<c13f591f>] ? klist_next+0x29/0xa3 (Errors) Jul 7 19:51:52 lafiel kernel: [<c1401fab>] ? wait_for_completion+0x12/0x14 (Errors) Anybody with more knowledge can tell me what goes wrong? It might be something not stock unraid related, so moderators feel free to move it to a seperate thread. syslog-2013-07-07.zip
July 7, 201312 yr @SLrG, based on ur syslog, you are a perfect candidate to boot from safe mode first and see what happens (grab a copy of the syslog from booting from safe mode). BTW, are you intentionally running jumbo frames mtu 9000?
July 7, 201312 yr I had no issues booting with 16c and my original 8GB RAM. Also ran a parity check with no issues however: I just increased the RAM from 8GB to 16GB and on booting up the console appeared to freeze for what seemed like several minutes part way through the bootup. In the syslog there is the following: Jul 7 14:47:11 NAS-03 kernel: INFO: rcu_sched self-detected stall on CPU { 2} (t=25109 jiffies g=4294967119 c=4294967118 q=45) Jul 7 14:47:11 NAS-03 kernel: Pid: 0, comm: swapper/2 Not tainted 3.9.6p-unRAID #23 Jul 7 14:47:11 NAS-03 kernel: Call Trace: Jul 7 14:47:11 NAS-03 kernel: [<c1062ba6>] print_cpu_stall+0xbc/0x107 Jul 7 14:47:11 NAS-03 kernel: [<c1062e36>] __rcu_pending+0x4f/0x12a Jul 7 14:47:11 NAS-03 kernel: [<c1062f84>] rcu_check_callbacks+0x73/0x9b Jul 7 14:47:11 NAS-03 kernel: [<c1032ead>] update_process_times+0x2d/0x53 Jul 7 14:47:11 NAS-03 kernel: [<c1055167>] tick_sched_timer+0x77/0xa1 Jul 7 14:47:11 NAS-03 kernel: [<c1040d86>] ? __remove_hrtimer+0x25/0x7a Jul 7 14:47:11 NAS-03 kernel: [<c1040ec9>] __run_hrtimer+0x45/0xaf Jul 7 14:47:11 NAS-03 kernel: [<c1041231>] hrtimer_interrupt+0xf1/0x1e7 Jul 7 14:47:11 NAS-03 kernel: [<c1054632>] tick_do_broadcast+0x2e/0x57 Jul 7 14:47:11 NAS-03 logger: /etc/rc.d/rc.inet1: /sbin/ifconfig eth0 192.168.1.63 broadcast 192.168.1.255 netmask 255.255.255.0 Jul 7 14:47:11 NAS-03 kernel: [<c1054705>] tick_handle_oneshot_broadcast+0xaa/0xd9 Jul 7 14:47:11 NAS-03 kernel: [<c10041e1>] timer_interrupt+0xd/0x14 Jul 7 14:47:11 NAS-03 kernel: [<c105def1>] handle_irq_event_percpu+0x2a/0x11a Jul 7 14:47:11 NAS-03 kernel: [<c10603a1>] ? irq_set_chip_and_handler_name+0x27/0x27 Jul 7 14:47:11 NAS-03 kernel: [<c105e006>] handle_irq_event+0x25/0x3c Jul 7 14:47:11 NAS-03 kernel: [<c10603a1>] ? irq_set_chip_and_handler_name+0x27/0x27 Jul 7 14:47:11 NAS-03 kernel: [<c106044f>] handle_edge_irq+0xae/0xcf Jul 7 14:47:11 NAS-03 kernel: <IRQ> [<c100362e>] ? do_IRQ+0x37/0x9b Jul 7 14:47:11 NAS-03 kernel: [<c1403d2c>] ? common_interrupt+0x2c/0x31 Jul 7 14:47:11 NAS-03 kernel: [<c100865d>] ? default_idle+0x1c/0x2c Jul 7 14:47:11 NAS-03 kernel: [<c1008788>] ? amd_e400_idle+0xb6/0xd1 Jul 7 14:47:11 NAS-03 kernel: [<c100880c>] ? cpu_idle+0x50/0x6f Jul 7 14:47:11 NAS-03 kernel: [<c13fe565>] ? start_secondary+0x9a/0x9c Jul 7 14:47:11 NAS-03 kernel: Hangcheck: hangcheck value past margin! I have attached the syslog showing the CPU Stall and a photo of what was being displayed on the console. I stopped the array via the WebGui and rebooted via the WebGui and the issue was NOT repeated. The syslog following the reboot seems fine. I don't currently have the opportunity to test further, however I am including this post for reference in case anyone else notices a similar issue, otherwise I'll assume it is an isolated and non-repeatable quirk. TheWombat syslog-20130707-145404.zip
July 7, 201312 yr xnas can you compile hdparm 9.43, please Done. Thanks! No problem. Get them while they're hot. It's that time of the month again when Tom can delete my account at any moment. LOL, be good man, u are always welcome here, just come off like a ukrainian coding coke head some times
July 7, 201312 yr I made the switch to rc16c today. Looking at my syslog, there are two things that didn't happen with rc12a. Firstly there seem to be memory problems? At least unmenu highlights them in red: It looks like you've not updated your unMENU. Those lines simply matched an old pattern affiliated with an error, but in the latest kernel they are just telling you how the memory is being allocated. They are informational, not errors at all. Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x00000000-0x000fffff] Jul 7 19:18:01 lafiel kernel: [mem 0x00000000-0x000fffff] page 4k Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x37800000-0x379fffff] Jul 7 19:18:01 lafiel kernel: [mem 0x37800000-0x379fffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x34000000-0x377fffff] Jul 7 19:18:01 lafiel kernel: [mem 0x34000000-0x377fffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x00100000-0x1fffffff] Jul 7 19:18:01 lafiel kernel: [mem 0x00100000-0x001fffff] page 4k Jul 7 19:18:01 lafiel kernel: [mem 0x00200000-0x1fffffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x20200000-0x33ffffff] Jul 7 19:18:01 lafiel kernel: [mem 0x20200000-0x33ffffff] page 2M Jul 7 19:18:01 lafiel kernel: init_memory_mapping: [mem 0x37a00000-0x37bfdfff] Jul 7 19:18:01 lafiel kernel: [mem 0x37a00000-0x37bfdfff] page 4k and then there are problems when I make the system sleep: Jul 7 19:51:52 lafiel kernel: ------------[ cut here ]------------ Jul 7 19:51:52 lafiel kernel: WARNING: at drivers/pci/pci.c:1393 pci_disable_device+0x50/0x79() (Minor Issues) Jul 7 19:51:52 lafiel kernel: Hardware name: To Be Filled By O.E.M. Jul 7 19:51:52 lafiel kernel: Device mpt2sas (Drive related) Jul 7 19:51:52 lafiel kernel: disabling already-disabled device Jul 7 19:51:52 lafiel kernel: Modules linked in: w83627ehf hwmon_vid md_mod sg mpt2sas i2c_i801 i2c_core scsi_transport_sas raid_class ahci libahci r8168(O) coretemp hwmon (Drive related) Jul 7 19:51:52 lafiel kernel: Pid: 2075, comm: kworker/u:2 Tainted: G O 3.9.6p-unRAID #23 (Errors) Jul 7 19:51:52 lafiel kernel: Call Trace: (Errors) Jul 7 19:51:52 lafiel kernel: [<c1029269>] warn_slowpath_common+0x77/0x8e (Errors) Jul 7 19:51:52 lafiel kernel: [<c1276a75>] ? pci_disable_device+0x50/0x79 (Errors) Jul 7 19:51:52 lafiel kernel: [<c1276a75>] ? pci_disable_device+0x50/0x79 (Errors) Jul 7 19:51:52 lafiel kernel: [<c10292fc>] warn_slowpath_fmt+0x2e/0x30 (Errors) Jul 7 19:51:52 lafiel kernel: [<c1276a75>] pci_disable_device+0x50/0x79 (Errors) Jul 7 19:51:52 lafiel kernel: [<f8570107>] _scsih_suspend+0x79/0x8c [mpt2sas] (Errors) Jul 7 19:51:52 lafiel kernel: [<c12779f1>] pci_legacy_suspend+0x24/0x9e (Errors) Jul 7 19:51:52 lafiel kernel: [<c1277e78>] pci_pm_suspend+0x31/0xe1 (Errors) Jul 7 19:51:52 lafiel kernel: [<c12e0eb9>] ? device_pm_wait_for_dev+0x1b/0x1b (Errors) Jul 7 19:51:52 lafiel kernel: [<c13f591f>] ? klist_next+0x29/0xa3 (Errors) Jul 7 19:51:52 lafiel kernel: [<c1401fab>] ? wait_for_completion+0x12/0x14 (Errors) Anybody with more knowledge can tell me what goes wrong? It might be something not stock unraid related, so moderators feel free to move it to a seperate thread. The second is probably also just informational. do you have more than one of the same type disk controller card? If so, it could be the kernel just telling you it already had unloaded the driver when the second card was being stopped.
Archived
This topic is now archived and is closed to further replies.