fschris Posted August 11, 2012 Share Posted August 11, 2012 DSK_DSBL .... I have read that this can be a number of things. I ran a SMARTCLT however it prints out the following. Other drives seem to print out normal data. Can any give me a next step on how to proceed? root@Tower:~# smartctl -a -A /dev/sdbd smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl open device: /dev/sdbd failed: No such device From the SYS LOG: Aug 11 10:21:42 Tower kernel: mdcmd (266405): spindown 2 (Routine)Aug 11 10:21:42 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -5 (Errors)Aug 11 10:21:52 Tower emhttp: mdcmd: write: Input/output error (Errors)Aug 11 10:21:52 Tower kernel: mdcmd (266406): spindown 2 (Routine)Aug 11 10:21:52 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -5 (Errors)Aug 11 10:22:02 Tower emhttp: mdcmd: write: Input/output error (Errors)Aug 11 10:22:02 Tower kernel: mdcmd (266407): spindown 2 (Routine)Aug 11 10:22:02 Tower kernel: md: disk2: ATA_OP_STANDBYNOW1 ioctl error: -5 (Errors)Aug 11 10:22:12 Tower emhttp: mdcmd: write: Input/output error (Errors)Aug 11 10:22:12 Tower kernel: mdcmd (266408): spindown 2 (Routine) From the Status page: DISK_DSBL /dev/md2 /mnt/disk2 /dev/sdb ST31500341AS_9VS4DH6K Link to comment
Joe L. Posted August 11, 2012 Share Posted August 11, 2012 you mis-typed the smartctl command. smartctl -a /dev/sdb (you typed /dev/sdbd) When a disk is disabled, there ONLY ONE reason. A write to it failed. The cause can be almost anything, from a bad disk, to a loose cable to the drive (either power or data) to a disk controller with a driver that is buggy. Since you elected to not attach a syslog, but instead provide only the pieces from it you think are important, can't help you much more. To put it back in service it must be re-constructed, as it is guaranteed it is not correct on the physical disk (remember, a write to it failed) It is completely normal and expected for reads and writes to the disabled drive to appear completely normal to you. It is being simulated by parity in combination with all your other data drives. if another drive were to fail now, you would lose the contents of BOTH drives. It is important to get the drive replaced/re-constructed ASAP. So, step 1. Post a syslog. step 2. get a SMART report. (If you can get a smart report, it indicates the drive is not completely dead. If you cannot. Proceed to step 3.) step 3. stop the array, power down, re-seat the connections to the drive. (even if you can get a smart report, as the connection could be intermittent) step 4. Power up again, try to get a smart report. If you cannot, try a different cable, or a different port on the disk controller before deciding the drive has died. If the drive provides a smart report, attempt to re-construct it using the steps below stop array un-assign the drive start array with it un-assigned stop the array once more re-assign the drive start the array once more. It will be re-constructed since the middle step of starting the array with it un-assigned will make the array forget its model/serial number, so it will think it is a new replacement drive. When completely re-constructed, you'll be parity protected once more. Do NOT format any drive, do NOT set a new disk configuration, do NOT press any button labeled as "restore" Joe L Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 The syslog is too big to attach! Link to comment
Joe L. Posted August 11, 2012 Share Posted August 11, 2012 The syslog is too big to attach! zip it. (they zip really well) Joe L. Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 smartctl -a -d ata /dev/sdb this returns root@Tower:~# smartctl -a -d ata /dev/sdb smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. Link to comment
Joe L. Posted August 11, 2012 Share Posted August 11, 2012 smartctl -a -d ata /dev/sdb this returns root@Tower:~# smartctl -a -d ata /dev/sdb smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. That indicates the drive is not responding at all. Either it has a bad connection to it, (power or data), or loose connection, or bad cable, or bad drive tray, or bad disk controller port, or it itself (the disk) has died. Some drives will lock-up and not respond again until power cycled, you won't know until you cycle power to the server. Joe L. Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 after a reboot... it says 'Not installed' disk2 Not installed - 1,465,138,552 45,899,156 - - Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 I did a smartctl -a -d ata /dev/sdb I can change out the sata cable... Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 UNRAID Drive Device Model/Serial Mounted File System Size Used %Used Free /dev/sde1 usb-_USB_Flash_Memory_0014225F365ABA40E60D0729-0:0 /boot vfat 4.00G 63.41M 2% 3.94G Cache Drive Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/sdb1 WDC_WD3200AAKS-00SBA0_WD-WMAPZ0267085 /mnt/cache reiserfs 35°C 320.06G 33.63M 1% 320.03G Drive Partitions - Not In Protected Array Device Model/Serial Mounted File System Temp Size Used %Used Free /dev/sdb WDC_WD3200AAKS-00SBA0_WD-WMAPZ0267085 35°C 320.07G /dev/sdd ST3320620AS_5QF55Z4G 38°C 320.07G /dev/sdd1 ST3320620AS_5QF55Z4G Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 root@Tower:~# smartctl -a -d ata /dev/sdb smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Blue Serial ATA family Device Model: WDC WD3200AAKS-00SBA0 Serial Number: WD-WMAPZ0267085 Firmware Version: 12.01B01 User Capacity: 320,071,851,520 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 7 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Aug 11 19:38:02 2012 Local time zone must be set--see zic m 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: (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: (8400) 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: ( 2) minutes. Extended self-test routine recommended polling time: ( 106) minutes. SCT capabilities: (0x103f) SCT Status 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 0x000f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0003 162 158 021 Pre-fail Always - 4900 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1633 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x000e 200 200 051 Old_age Always - 0 9 Power_On_Hours 0x0032 054 054 000 Old_age Always - 33990 10 Spin_Retry_Count 0x0012 100 100 051 Old_age Always - 0 11 Calibration_Retry_Count 0x0012 100 100 051 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 629 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 67 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 1633 194 Temperature_Celsius 0x0022 112 092 000 Old_age Always - 35 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 051 Old_age Offline - 0 SMART Error Log Version: 1 ATA Error Count: 6613 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days. Error 6613 occurred at disk power-on lifetime: 24603 hours (1025 days + 3 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 40 48 bd 63 e0 Error: UNC 64 sectors at LBA = 0x0063bd48 = 6536520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 48 bd 63 1c 00 12:45:20.406 READ DMA EXT 25 00 80 c0 c3 41 0b 00 12:45:20.386 READ DMA EXT 35 00 08 80 bd 5b 00 00 12:45:20.336 WRITE DMA EXT ea 00 00 00 00 00 7f 00 12:45:20.320 FLUSH CACHE EXT 35 00 08 78 bd 5b 00 00 12:45:20.320 WRITE DMA EXT Error 6612 occurred at disk power-on lifetime: 24603 hours (1025 days + 3 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 40 48 bd 63 e0 Error: UNC 64 sectors at LBA = 0x0063bd48 = 6536520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 48 bd 63 1c 00 12:31:17.615 READ DMA EXT 35 00 08 68 bd 5b 00 00 12:31:17.565 WRITE DMA EXT 35 00 08 78 bd 5b 00 00 12:31:17.565 WRITE DMA EXT 35 00 08 d0 8d 02 0f 00 12:31:17.565 WRITE DMA EXT 35 00 18 00 4c 5c 00 00 12:31:17.565 WRITE DMA EXT Error 6611 occurred at disk power-on lifetime: 24603 hours (1025 days + 3 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 40 48 bd 63 e0 Error: UNC 64 sectors at LBA = 0x0063bd48 = 6536520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 48 bd 63 1c 00 12:31:09.294 READ DMA EXT 35 00 08 78 49 5c 00 00 12:31:09.266 WRITE DMA EXT ea 00 00 00 00 00 87 00 12:31:09.238 FLUSH CACHE EXT 35 00 08 80 bd 5b 00 00 12:31:09.237 WRITE DMA EXT 25 00 80 c0 c3 41 0b 00 12:31:09.227 READ DMA EXT Error 6610 occurred at disk power-on lifetime: 24602 hours (1025 days + 2 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 40 48 bd 63 e0 Error: UNC 64 sectors at LBA = 0x0063bd48 = 6536520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 48 bd 63 1c 00 12:28:23.874 READ DMA EXT 25 00 40 40 d8 00 1a 00 12:28:23.862 READ DMA EXT 25 00 40 38 0d 02 1a 00 12:28:23.833 READ DMA EXT 25 00 08 88 f0 ac 0b 00 12:28:23.805 READ DMA EXT 25 00 08 80 f0 ac 0b 00 12:28:23.800 READ DMA EXT Error 6609 occurred at disk power-on lifetime: 24602 hours (1025 days + 2 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 40 48 bd 63 e0 Error: UNC 64 sectors at LBA = 0x0063bd48 = 6536520 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- 25 00 40 48 bd 63 1c 00 12:28:20.034 READ DMA EXT 35 00 08 80 bd 5b 00 00 12:28:19.996 WRITE DMA EXT 35 00 00 20 34 55 01 00 12:28:19.994 WRITE DMA EXT 35 00 00 20 33 55 01 00 12:28:19.978 WRITE DMA EXT 35 00 00 20 32 55 01 00 12:28:19.977 WRITE DMA EXT 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. Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 I dont uderstand this... Originally it had this disk as bad DISK_DSBL /dev/md2 /mnt/disk2 /dev/sdb ST31500341AS_9VS4DH6K But after a reboot and I do the SMRTCTL command with /sdb it give the info for this drive below?!??! Device Model: WDC WD3200AAKS-00SBA0 Serial Number: WD-WMAPZ0267085 Link to comment
jespeed Posted August 11, 2012 Share Posted August 11, 2012 Hello, I believe the disk assignment letters can and do change on reboots. It depends on the order that the drives are detected during bootup. You will need to figure out the correct drive assignment to perform the smart check on the problem disk drive. Hope this helps. Jim S. Link to comment
fschris Posted August 11, 2012 Author Share Posted August 11, 2012 jespeed...thanks! I thought something was awry! Link to comment
Influencer Posted August 12, 2012 Share Posted August 12, 2012 Yes, device designation (sdX) changes on every boot. They are assigned in the order they report during startup. This will most likely change on every boot. Link to comment
fschris Posted August 12, 2012 Author Share Posted August 12, 2012 I guess what is odd that it went from DSK DISABLE to Not Installed after the reboot. Link to comment
Joe L. Posted August 12, 2012 Share Posted August 12, 2012 I guess what is odd that it went from DSK DISABLE to Not Installed after the reboot. No odd at all if it is not responding any more. From its view-point, it is not installed if the BIOS does not see the drive. Link to comment
fschris Posted August 13, 2012 Author Share Posted August 13, 2012 i just did a RMA with seagate for a new drive. I will have a new one on the way. When i get it the first thing i will do is pre clear it. after that I will need to find the thread to change out a bad drive. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.