June 29, 201313 yr Hi guys, I connected a 3tb drive into my existing system, don't know if the drive is connected to AOC-SASLP-MV8 or LSISAS1068E, the drive has been installed in 5x3 drive caddy. However when I added the drive the web interface shows the drive as 2.2 tb drive, can I do something to fix this? Will I lose the data I already put on it. It's sdt WDC_WD30EZRX-00MMMB0 WD-WCAWZ1895639 Here is the preclear report Disk: /dev/sdt smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD30EZRX-00MMMB0 Serial Number: WD-WCAWZ1895639 Firmware Version: 80.00A80 User Capacity: 3,000,592,982,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sat Jun 29 02:23:59 2013 PDT 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: (49500) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. 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: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3035) 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 175 175 021 Pre-fail Always - 8233 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 47 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 6 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 5 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 21 194 Temperature_Celsius 0x0022 122 109 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 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. I have also attached the syslog. Hopefully someone smarter can assist. Thanks again. syslog-2013-06-29.zip
June 29, 201313 yr Was this used in an unRaid 4.7 system before and was logically shrunk down to 2.2 TB to work in the v4.7 system?
June 29, 201313 yr Author no never in 4.7 with 5 rc15. problem seems that it's not formatted as gpt it used mbr which can only address 2.2tb, could it be because I did not reboot the server after adding the drive?
June 29, 201313 yr no never in 4.7 with 5 rc15. problem seems that it's not formatted as gpt it used mbr which can only address 2.2tb, could it be because I did not reboot the server after adding the drive? What does the hdparm command show? hdparm -N /dev/sdX Many utilities under linux do not know how to deal with disks larger than 2.2TB as that is the largest an MBR partition can define. It has nothing to do with rebooting the server.
June 29, 201313 yr Author root@Tower:~# hdparm -N /dev/sdt /dev/sdt: max sectors = 5860533168/5860533168, HPA is disabled another drive of mine was correctly integrated as a 3tb drive and has the same output /dev/sdi: max sectors = 5860533168/5860533168, HPA is disabled HDParm Info for /dev/sdt WDC_WD30EZRX-00MMMB0_WD-WCAWZ1895639 /dev/sdt: ATA device, with non-removable media Model Number: WDC WD30EZRX-00MMMB0 Serial Number: WD-WCAWZ1895639 Firmware Revision: 80.00A80 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: 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: 5860533168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 2861588 MBytes device size with M = 1000*1000: 3000592 MBytes (3000 GB) cache/buffer size = unknown Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 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 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 * General Purpose Logging feature set * 64-bit World wide name * {READ,WRITE}_DMA_EXT_GPL commands * Segmented DOWNLOAD_MICROCODE * 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 DMA Setup Auto-Activate optimization * Software settings preservation * SMART Command Transport (SCT) feature set * SCT LBA Segment Access (AC2) * SCT Features Control (AC4) * SCT Data Tables (AC5) unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 504min for SECURITY ERASE UNIT. 504min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee2b1539614 NAA : 5 IEEE OUI : 0014ee Unique ID : 2b1539614 Checksum: correct the good drive is HDParm Info for /dev/sdi WDC_WD30EFRX-68AX9N0_WD-WMC1T1079164 /dev/sdi: ATA device, with non-removable media Model Number: WDC WD30EFRX-68AX9N0 Serial Number: WD-WMC1T1079164 Firmware Revision: 80.00A80 Transport: Serial, SATA 1.0a, SATA II Extensions, SATA Rev 2.5, SATA Rev 2.6, SATA Rev 3.0 Standards: Supported: 9 8 7 6 5 Likely used: 9 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: 5860533168 Logical Sector size: 512 bytes Physical Sector size: 4096 bytes Logical Sector-0 offset: 0 bytes device size with M = 1024*1024: 2861588 MBytes device size with M = 1000*1000: 3000592 MBytes (3000 GB) cache/buffer size = unknown Capabilities: LBA, IORDY(can be disabled) Queue depth: 32 Standby timer values: spec'd by Standard, with device specific minimum R/W multiple sector transfer: Max = 16 Current = 0 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 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 * 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 * 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 * unknown 76[15] DMA Setup Auto-Activate optimization Device-initiated interface power management * 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) unknown 206[7] unknown 206[12] (vendor specific) unknown 206[13] (vendor specific) unknown 206[14] (vendor specific) Security: Master password revision code = 65534 supported not enabled not locked not frozen not expired: security count supported: enhanced erase 440min for SECURITY ERASE UNIT. 440min for ENHANCED SECURITY ERASE UNIT. Logical Unit WWN Device Identifier: 50014ee6ad94a492 NAA : 5 IEEE OUI : 0014ee Unique ID : 6ad94a492 Checksum: correct
June 29, 201313 yr don't know if the drive is connected to AOC-SASLP-MV8 or LSISAS1068E AFAIK The LSISAS1068E does not support drives >2.2Tb... The AOC-SASLP-MV8 does
June 29, 201313 yr Author so how can I fix this, unplug it from the LSISAS1068E and plug into the AOC-SASLP-MV8, and how do I then get the GPT partition?
June 29, 201313 yr I would migrate all data off. Then i would do a low level format that removes the mbr. I have a utility that does this. It is called hdd low level format 4.25 . The newest version can just remove the mbr with out the full format. Then re preclear on correct card. Sent from my YP-G70 using Tapatalk 2
June 29, 201313 yr I would migrate all data off. Then i would do a low level format that removes the mbr. I have a utility that does this. It is called hdd low level format 4.25 . The newest version can just remove the mbr with out the full format. Then re preclear on correct card. preclear_disk.sh -z /dev/sdX will write zeros to the MBR. (same as the other utility mentioned) Any preclear will itself set the MBR correctly for unRAID. (so actually, no need to do anything at all to the disk ahead of time if you are preclearing it, not even using the -z option.)
June 29, 201313 yr Author Joe L. I did the preclear_disk.sh -z and that was successful, but I did not do another preclear afterwards, I power cycled the unit to swap the sata cables, afterwards it did not start the array, because it detected that the drive was now a 3tb drive no longer a 2.2tb, now it's doing a data rebuild, don't know why it's doing that... but I guess nothing I can do right now because it tells me I cannot abort it....
June 29, 201313 yr Joe L. I did the preclear_disk.sh -z and that was successful, but I did not do another preclear afterwards, I power cycled the unit to swap the sata cables, afterwards it did not start the array, because it detected that the drive was now a 3tb drive no longer a 2.2tb, now it's doing a data rebuild, don't know why it's doing that... but I guess nothing I can do right now because it tells me I cannot abort it.... It thinks it is a different disk, so it is re-constructing onto it. Let it complete. Joe L.
June 29, 201313 yr Author Now I have the drive red balled, when it was doing the rebuilding... any clues what I can do to fix this now? Should I just do another preclear operation to fix this now? syslog.zip syslog.zip
June 29, 201313 yr Now I have the drive red balled, when it was doing the rebuilding... any clues what I can do to fix this now? Should I just do another preclear operation to fix this now? A "red" indicator say that a "Write" to the disk failed. Very unlikely another clearing of the drive will fix that. For a write to fail, it indicates a bigger issue... either a loose or intermittent cable (power or data), or intermittent power supply splitter, or drive tray, or a power supply too small, or a bad drive, or a bad disk controller port. Only way to even have a clue is if you post a syslog. It might have a clue to the type of failure.
June 29, 201313 yr According to your syslog, the disk has stopped responding. (most likely either a loose cable, although it could just be a failed disk) The OS did try a number of times to reset the disk controller and re-establish communications, but failed. Jun 29 13:39:05 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen Jun 29 13:39:05 Tower kernel: ata8.00: failed command: READ FPDMA QUEUED Jun 29 13:39:05 Tower kernel: ata8.00: cmd 60/08:00:40:00:10/00:00:06:00:00/40 tag 0 ncq 4096 in Jun 29 13:39:05 Tower kernel: res 40/00:04:f0:8e:b6/00:00:11:00:00/40 Emask 0x4 (timeout) Jun 29 13:39:05 Tower kernel: ata8.00: status: { DRDY } Jun 29 13:39:05 Tower kernel: ata8: hard resetting link Jun 29 13:39:05 Tower kernel: sas: ata9: end_device-1:2: dev error handler Jun 29 13:39:05 Tower kernel: sas: ata10: end_device-1:3: dev error handler Jun 29 13:39:05 Tower kernel: sas: ata11: end_device-1:4: dev error handler Jun 29 13:39:05 Tower kernel: ata11.00: exception Emask 0x0 SAct 0x37 SErr 0x0 action 0x6 frozen Jun 29 13:39:05 Tower kernel: ata11.00: failed command: WRITE FPDMA QUEUED Jun 29 13:39:05 Tower kernel: ata11.00: cmd 61/00:00:e8:c7:56/02:00:2b:00:00/40 tag 0 ncq 262144 out Jun 29 13:39:05 Tower kernel: res 40/00:00:f0:90:b6/00:02:11:00:00/40 Emask 0x4 (timeout) Jun 29 13:39:05 Tower kernel: ata11.00: status: { DRDY } Jun 29 13:39:05 Tower kernel: ata11.00: failed command: WRITE FPDMA QUEUED Jun 29 13:39:05 Tower kernel: ata11.00: cmd 61/00:00:e8:cd:56/02:00:2b:00:00/40 tag 1 ncq 262144 out Jun 29 13:39:05 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 29 13:39:05 Tower kernel: ata11.00: status: { DRDY } Jun 29 13:39:05 Tower kernel: ata11.00: failed command: WRITE FPDMA QUEUED Jun 29 13:39:05 Tower kernel: ata11.00: cmd 61/00:00:e8:c3:56/02:00:2b:00:00/40 tag 2 ncq 262144 out Jun 29 13:39:05 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 29 13:39:05 Tower kernel: ata11.00: status: { DRDY } Jun 29 13:39:05 Tower kernel: ata11.00: failed command: WRITE FPDMA QUEUED Jun 29 13:39:05 Tower kernel: ata11.00: cmd 61/00:00:e8:c9:56/02:00:2b:00:00/40 tag 4 ncq 262144 out Jun 29 13:39:05 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 29 13:39:05 Tower kernel: ata11.00: status: { DRDY } Jun 29 13:39:05 Tower kernel: ata11.00: failed command: WRITE FPDMA QUEUED Jun 29 13:39:05 Tower kernel: ata11.00: cmd 61/00:00:e8:cb:56/02:00:2b:00:00/40 tag 5 ncq 262144 out Jun 29 13:39:05 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Jun 29 13:39:05 Tower kernel: ata11.00: status: { DRDY } Jun 29 13:39:05 Tower kernel: ata11: hard resetting link Jun 29 13:39:05 Tower kernel: sas: ata12: end_device-1:5: dev error handler Jun 29 13:39:05 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[4]:rc= 0 Jun 29 13:39:05 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[1]:rc= 0 Jun 29 13:39:05 Tower kernel: sas: sas_ata_task_done: SAS error 8a Jun 29 13:39:05 Tower last message repeated 2 times Jun 29 13:39:05 Tower kernel: ata11.00: both IDENTIFYs aborted, assuming NODEV
June 30, 201313 yr Author thanks Joe, I have now connected a diffent sata cable to the same controller port and the rebuild has been running for several hours without incident and just completed successfully... still find it strange that it took so long even though I had moved all data from the drive, but it had over 1 million writes to it... I wonder why... there was nothing there.
July 1, 201313 yr thanks Joe, I have now connected a diffent sata cable to the same controller port and the rebuild has been running for several hours without incident and just completed successfully... still find it strange that it took so long even though I had moved all data from the drive, but it had over 1 million writes to it... I wonder why... there was nothing there. A data rebuild is independent of the amount of data on a drive as it works at the physical level. It is therefore determined by the size of the drive.
Archived
This topic is now archived and is closed to further replies.