Alert shows two drives down?

Status
Not open for further replies.
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
Hi,

I am using a number of older drives for testing purposes. All data on this box is duplicated elsewhere - except some VM's I have been playing with that are not important.

I received this email:

Device: /dev/ada2, FAILED SMART self-check. BACK UP DATA NOW!
Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Device: /dev/ada2, Failed SMART usage Attribute: 5 Reallocated_Sector_Ct.
Device: /dev/ada2, 1 Currently unreadable (pending) sectors
Device: /dev/ada1, 1 Offline uncorrectable sectors

When I logged into the freenas web page i have the following:

Alert System
  • CRITICAL: Device: /dev/ada2, FAILED SMART self-check. BACK UP DATA NOW!
  • CRITICAL: Device: /dev/ada2, Failed SMART usage Attribute: 5 Reallocated_Sector_Ct.
  • CRITICAL: Device: /dev/ada2, 1 Currently unreadable (pending) sectors
  • CRITICAL: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
  • CRITICAL: Device: /dev/ada1, 1 Offline uncorrectable sectors
I have not done anything else but post this. I was curious if it is typical to have two drives 'failing' at the same time?

The box has 6x 2tb drives of various ages running in raidz2.

Any thoughts on next steps? I was planning on buying 6x 6tb wd red drives but feel like this is a great way to test the system.

It is running very slowly at this point, big delay in web page loading, big delay in VM response.

Thanks,
Rich
 
danb35

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
RichTJ99 said:
I was curious if it is typical to have two drives 'failing' at the same time?
Click to expand...
I don't think it's "typical", but it certainly isn't unusual. But you have two different magnitude events here. First, ada1 has a bad sector. This isn't a good thing, but it isn't critical. I'd monitor this, but wouldn't consider it essential to do anything else immediately. Second, ada2 has failed a SMART self-test. This is bad, and the drive is failing. You should plan to replace it ASAP. If you can post the full SMART output for the drives (smartctl -a /dev/ada1 and ada2), in code tags, that might be helpful.

It's unlikely that either of these issues is causing significant slowness in your system, though--the cause of that likely lies elsewhere.
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
I am using the web 'shell' - is there a way to scroll up? The "smartctl -a /dev/ada1" command gives a few screens worth that shoot by but nothing I can read as its too fast.

Thanks,
Rich
 
-fun-

-fun-

Contributor
Joined
Oct 27, 2015
Messages
171
smartctl -a /dev/ada1 | less
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
I pulled out an extra 2tb drive out of another Freenas box (I bought a lot over the years) and plugged it into ADA2. I went to:

Storage
Clicked: FNPool
Clicked : Volume Status
Clicked on the unavailable drive
Clicked Replace
Shows member disk ada2 (2.0 TB)
Press replace disk

On the bottom the console shows (SORRY - SEE BOTTOM) - but end result is the replacement drive fails to add itself. Am I doing this wrong?


Thanks,
Rich



Jan 4 11:59:29 freenas notifier: shutdown: [pid 73854]
Jan 4 11:59:29 freenas notifier: Shutdown NOW!
Jan 4 11:59:29 freenas shutdown: power-down by root:
Jan 4 11:59:31 freenas notifier: Shutdown NOW!
Jan 4 11:59:31 freenas notifier:
Jan 4 11:59:31 freenas notifier: System shutdown time has arrived^G^G
Jan 4 12:14:07 freenas syslog-ng[1889]: syslog-ng starting up; version='3.5.6'
Jan 4 12:14:07 freenas Copyright (c) 1992-2014 The FreeBSD Project.
Jan 4 12:14:07 freenas Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Jan 4 12:14:07 freenas The Regents of the University of California. All rights reserved.
Jan 4 12:14:07 freenas FreeBSD is a registered trademark of The FreeBSD Foundation.
Jan 4 12:14:07 freenas FreeBSD 9.3-RELEASE-p28 #0 r288272+f229c79: Sat Dec 12 11:58:01 PST 2015
Jan 4 12:14:07 freenas root@build3.ixsystems.com:/tank/home/stable-builds/FN/objs/os-base/amd64/tank/home/stable-builds/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
Jan 4 12:14:07 freenas gcc version 4.2.1 20070831 patched [FreeBSD]
Jan 4 12:14:07 freenas CPU: Intel(R) Xeon(R) CPU E3-1231 v3 @ 3.40GHz (3400.07-MHz K8-class CPU)
Jan 4 12:14:07 freenas Origin = "GenuineIntel" Id = 0x306c3 Family = 0x6 Model = 0x3c Stepping = 3
Jan 4 12:14:07 freenas Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Jan 4 12:14:07 freenas Features2=0x7ffafbff<SSE3,PCLMULQDQ,DTES64,MON,DS_CPL,VMX,SMX,EST,TM2,SSSE3,<b11>,FMA,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,TSCDLT,AESNI,XSAVE,OSXSAVE,AVX,F16C,RDRAND>
Jan 4 12:14:07 freenas AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
Jan 4 12:14:07 freenas AMD Features2=0x21<LAHF,ABM>
Jan 4 12:14:07 freenas Standard Extended Features=0x27ab<GSFSBASE,TSCADJ,SMEP,ENHMOVSB,INVPCID>
Jan 4 12:14:07 freenas TSC: P-state invariant, performance statistics
Jan 4 12:14:07 freenas real memory = 34896609280 (33280 MB)
Jan 4 12:14:07 freenas avail memory = 33124188160 (31589 MB)
Jan 4 12:14:07 freenas Event timer "LAPIC" quality 600
Jan 4 12:14:07 freenas ACPI APIC Table: <SUPERM SMCI--MB>
Jan 4 12:14:07 freenas FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
Jan 4 12:14:07 freenas FreeBSD/SMP: 1 package(s) x 4 core(s) x 2 SMT threads
Jan 4 12:14:07 freenas cpu0 (BSP): APIC ID: 0
Jan 4 12:14:07 freenas cpu1 (AP): APIC ID: 1
Jan 4 12:14:07 freenas cpu2 (AP): APIC ID: 2
Jan 4 12:14:07 freenas cpu3 (AP): APIC ID: 3
Jan 4 12:14:07 freenas cpu4 (AP): APIC ID: 4
Jan 4 12:14:07 freenas cpu5 (AP): APIC ID: 5
Jan 4 12:14:07 freenas cpu6 (AP): APIC ID: 6
Jan 4 12:14:07 freenas cpu7 (AP): APIC ID: 7
Jan 4 12:14:07 freenas WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Jan 4 12:14:07 freenas ACPI Warning: FADT (revision 5) is longer than ACPI 5.0 version, truncating length 268 to 256 (20111123/tbfadt-325)
Jan 4 12:14:07 freenas ioapic0 <Version 2.0> irqs 0-23 on motherboard
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_1040>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_1040_it>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_1080>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_1080_it>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_12160>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_12160_it>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2100>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2200>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2300>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2322>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2400>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2400_multi>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2500>
Jan 4 12:14:07 freenas ispfw: registered firmware <isp_2500_multi>
Jan 4 12:14:07 freenas kbd1 at kbdmux0
Jan 4 12:14:07 freenas cryptosoft0: <software crypto> on motherboard
Jan 4 12:14:07 freenas aesni0: <AES-CBC,AES-XTS> on motherboard
Jan 4 12:14:07 freenas padlock0: No ACE support.
Jan 4 12:14:07 freenas acpi0: <SUPERM SMCI--MB> on motherboard
Jan 4 12:14:07 freenas acpi0: Power Button (fixed)
Jan 4 12:14:07 freenas cpu0: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu1: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu2: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu3: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu4: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu5: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu6: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas cpu7: <ACPI CPU> on acpi0
Jan 4 12:14:07 freenas hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Jan 4 12:14:07 freenas Timecounter "HPET" frequency 14318180 Hz quality 950
Jan 4 12:14:07 freenas Event timer "HPET" frequency 14318180 Hz quality 550
Jan 4 12:14:07 freenas atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
Jan 4 12:14:07 freenas Event timer "RTC" frequency 32768 Hz quality 0
Jan 4 12:14:07 freenas attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Jan 4 12:14:07 freenas Timecounter "i8254" frequency 1193182 Hz quality 0
Jan 4 12:14:07 freenas Event timer "i8254" frequency 1193182 Hz quality 100
Jan 4 12:14:07 freenas Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Jan 4 12:14:07 freenas acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
Jan 4 12:14:07 freenas pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
Jan 4 12:14:07 freenas pci0: <ACPI PCI bus> on pcib0
Jan 4 12:14:07 freenas pcib1: <ACPI PCI-PCI bridge> irq 16 at device 1.0 on pci0
Jan 4 12:14:07 freenas pci1: <ACPI PCI bus> on pcib1
Jan 4 12:14:07 freenas pcib2: <ACPI PCI-PCI bridge> irq 16 at device 1.1 on pci0
Jan 4 12:14:07 freenas pci2: <ACPI PCI bus> on pcib2
Jan 4 12:14:07 freenas mps0: <Avago Technologies (LSI) SAS2308> port 0xe000-0xe0ff mem 0xf7240000-0xf724ffff,0xf7200000-0xf723ffff irq 17 at device 0.0 on pci2
Jan 4 12:14:07 freenas mps0: Firmware: 20.00.04.00, Driver: 20.00.00.00-fbsd
Jan 4 12:14:07 freenas mps0: IOCCapabilities: 5285c<ScsiTaskFull,DiagTrace,SnapBuf,EEDP,TransRetry,EventReplay,HostDisc>
Jan 4 12:14:07 freenas ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf7504000-0xf75043ff irq 16 at device 26.0 on pci0
Jan 4 12:14:07 freenas usbus0: EHCI version 1.0
Jan 4 12:14:07 freenas usbus0 on ehci0
Jan 4 12:14:07 freenas pcib3: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
Jan 4 12:14:07 freenas pci3: <ACPI PCI bus> on pcib3
Jan 4 12:14:07 freenas pcib4: <ACPI PCI-PCI bridge> at device 0.0 on pci3
Jan 4 12:14:07 freenas pci4: <ACPI PCI bus> on pcib4
Jan 4 12:14:07 freenas vgapci0: <VGA-compatible display> port 0xd000-0xd07f mem 0xf6000000-0xf6ffffff,0xf7000000-0xf701ffff irq 16 at device 0.0 on pci4
Jan 4 12:14:07 freenas vgapci0: Boot video device
Jan 4 12:14:07 freenas pcib5: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
Jan 4 12:14:07 freenas pci5: <ACPI PCI bus> on pcib5
Jan 4 12:14:07 freenas igb0: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xc000-0xc01f mem 0xf7400000-0xf747ffff,0xf7480000-0xf7483fff irq 18 at device 0.0 on pci5
Jan 4 12:14:07 freenas igb0: Using MSIX interrupts with 5 vectors
Jan 4 12:14:07 freenas igb0: Ethernet address: 0c:c4:7a:6b:e4:a4
Jan 4 12:14:07 freenas igb0: Bound queue 0 to cpu 0
Jan 4 12:14:07 freenas igb0: Bound queue 1 to cpu 1
Jan 4 12:14:07 freenas igb0: Bound queue 2 to cpu 2
Jan 4 12:14:07 freenas igb0: Bound queue 3 to cpu 3
Jan 4 12:14:07 freenas pcib6: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
Jan 4 12:14:07 freenas pci6: <ACPI PCI bus> on pcib6
Jan 4 12:14:07 freenas igb1: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xb000-0xb01f mem 0xf7300000-0xf737ffff,0xf7380000-0xf7383fff irq 19 at device 0.0 on pci6
Jan 4 12:14:07 freenas igb1: Using MSIX interrupts with 5 vectors
Jan 4 12:14:07 freenas igb1: Ethernet address: 0c:c4:7a:6b:e4:a5
Jan 4 12:14:07 freenas igb1: Bound queue 0 to cpu 4
Jan 4 12:14:07 freenas igb1: Bound queue 1 to cpu 5
Jan 4 12:14:07 freenas igb1: Bound queue 2 to cpu 6
Jan 4 12:14:07 freenas igb1: Bound queue 3 to cpu 7
Jan 4 12:14:07 freenas ehci1: <EHCI (generic) USB 2.0 controller> mem 0xf7503000-0xf75033ff irq 22 at device 29.0 on pci0
Jan 4 12:14:07 freenas usbus1: EHCI version 1.0
Jan 4 12:14:07 freenas usbus1 on ehci1
Jan 4 12:14:07 freenas isab0: <PCI-ISA bridge> at device 31.0 on pci0
Jan 4 12:14:07 freenas isa0: <ISA bus> on isab0
Jan 4 12:14:07 freenas ahci0: <Intel Lynx Point AHCI SATA controller> port 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf000-0xf01f mem 0xf7502000-0xf75027ff irq 19 at device 31.2 on pci0
Jan 4 12:14:07 freenas ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported
Jan 4 12:14:07 freenas ahcich0: <AHCI channel> at channel 0 on ahci0
Jan 4 12:14:07 freenas ahcich1: <AHCI channel> at channel 1 on ahci0
Jan 4 12:14:07 freenas ahcich2: <AHCI channel> at channel 2 on ahci0
Jan 4 12:14:07 freenas ahcich3: <AHCI channel> at channel 3 on ahci0
Jan 4 12:14:07 freenas ahcich4: <AHCI channel> at channel 4 on ahci0
Jan 4 12:14:07 freenas ahcich5: <AHCI channel> at channel 5 on ahci0
Jan 4 12:14:07 freenas acpi_button0: <Sleep Button> on acpi0
Jan 4 12:14:07 freenas acpi_button1: <Power Button> on acpi0
Jan 4 12:14:07 freenas acpi_tz0: <Thermal Zone> on acpi0
Jan 4 12:14:07 freenas acpi_tz1: <Thermal Zone> on acpi0
Jan 4 12:14:07 freenas uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Jan 4 12:14:07 freenas uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
Jan 4 12:14:07 freenas uart2: <16550 or compatible> port 0x3e8-0x3ef irq 5 on acpi0
Jan 4 12:14:07 freenas orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc87ff on isa0
Jan 4 12:14:07 freenas sc0: <System console> at flags 0x100 on isa0
Jan 4 12:14:07 freenas sc0: CGA <16 virtual consoles, flags=0x300>
Jan 4 12:14:07 freenas vga0: <Generic ISA VGA> at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0
Jan 4 12:14:07 freenas wbwd0: DevID 0xc3 DevRev 0x33, will not attach, please report this.
Jan 4 12:14:07 freenas coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Jan 4 12:14:07 freenas est0: <Enhanced SpeedStep Frequency Control> on cpu0
Jan 4 12:14:07 freenas coretemp1: <CPU On-Die Thermal Sensors> on cpu1
Jan 4 12:14:07 freenas est1: <Enhanced SpeedStep Frequency Control> on cpu1
Jan 4 12:14:07 freenas coretemp2: <CPU On-Die Thermal Sensors> on cpu2
Jan 4 12:14:07 freenas est2: <Enhanced SpeedStep Frequency Control> on cpu2
Jan 4 12:14:07 freenas coretemp3: <CPU On-Die Thermal Sensors> on cpu3
Jan 4 12:14:07 freenas est3: <Enhanced SpeedStep Frequency Control> on cpu3
Jan 4 12:14:07 freenas coretemp4: <CPU On-Die Thermal Sensors> on cpu4
Jan 4 12:14:07 freenas est4: <Enhanced SpeedStep Frequency Control> on cpu4
Jan 4 12:14:07 freenas coretemp5: <CPU On-Die Thermal Sensors> on cpu5
Jan 4 12:14:07 freenas est5: <Enhanced SpeedStep Frequency Control> on cpu5
Jan 4 12:14:07 freenas coretemp6: <CPU On-Die Thermal Sensors> on cpu6
Jan 4 12:14:07 freenas est6: <Enhanced SpeedStep Frequency Control> on cpu6
Jan 4 12:14:07 freenas coretemp7: <CPU On-Die Thermal Sensors> on cpu7
Jan 4 12:14:07 freenas est7: <Enhanced SpeedStep Frequency Control> on cpu7
Jan 4 12:14:07 freenas ZFS filesystem version: 5
Jan 4 12:14:07 freenas ZFS storage pool version: features support (5000)
Jan 4 12:14:07 freenas Timecounters tick every 1.000 msec
Jan 4 12:14:07 freenas ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
Jan 4 12:14:07 freenas usbus0: 480Mbps High Speed USB v2.0
Jan 4 12:14:07 freenas usbus1: 480Mbps High Speed USB v2.0
Jan 4 12:14:07 freenas ugen0.1: <Intel> at usbus0
Jan 4 12:14:07 freenas uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
Jan 4 12:14:07 freenas ugen1.1: <Intel> at usbus1
Jan 4 12:14:07 freenas uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
Jan 4 12:14:07 freenas uhub0: 2 ports with 2 removable, self powered
Jan 4 12:14:07 freenas uhub1: 2 ports with 2 removable, self powered
Jan 4 12:14:07 freenas ugen0.2: <vendor 0x8087> at usbus0
Jan 4 12:14:07 freenas uhub2: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.05, addr 2> on usbus0
Jan 4 12:14:07 freenas ugen1.2: <vendor 0x8087> at usbus1
Jan 4 12:14:07 freenas uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.05, addr 2> on usbus1
Jan 4 12:14:07 freenas uhub2: 4 ports with 4 removable, self powered
Jan 4 12:14:07 freenas uhub3: 6 ports with 6 removable, self powered
Jan 4 12:14:07 freenas ugen0.3: <vendor 0x0557> at usbus0
Jan 4 12:14:07 freenas uhub4: <vendor 0x0557 product 0x7000, class 9/0, rev 2.00/0.00, addr 3> on usbus0
Jan 4 12:14:07 freenas uhub4: 4 ports with 3 removable, self powered
Jan 4 12:14:07 freenas ugen0.4: <vendor 0x0557> at usbus0
Jan 4 12:14:07 freenas ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
Jan 4 12:14:07 freenas kbd0 at ukbd0
Jan 4 12:14:07 freenas ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
Jan 4 12:14:07 freenas ums0: 3 buttons and [Z] coordinates ID=0
Jan 4 12:14:07 freenas ugen1.3: <SanDisk> at usbus1
Jan 4 12:14:07 freenas umass0: <SanDisk Cruzer Fit, class 0/0, rev 2.00/1.27, addr 3> on usbus1
Jan 4 12:14:07 freenas umass0: SCSI over Bulk-Only; quirks = 0x8100
Jan 4 12:14:07 freenas umass0:8:0:-1: Attached to scbus8
Jan 4 12:14:07 freenas ugen1.4: <SanDisk> at usbus1
Jan 4 12:14:07 freenas umass1: <SanDisk Cruzer Fit, class 0/0, rev 2.00/1.27, addr 4> on usbus1
Jan 4 12:14:07 freenas umass1: SCSI over Bulk-Only; quirks = 0x8100
Jan 4 12:14:07 freenas umass1:9:1:-1: Attached to scbus9
Jan 4 12:14:07 freenas ugen1.5: <Dell> at usbus1
Jan 4 12:14:07 freenas ukbd1: <Dell Dell USB Keyboard, class 0/0, rev 1.10/3.07, addr 5> on usbus1
Jan 4 12:14:07 freenas kbd2 at ukbd1
Jan 4 12:14:07 freenas da0 at umass-sim0 bus 0 scbus8 target 0 lun 0
Jan 4 12:14:07 freenas da0: <SanDisk Cruzer Fit 1.27> Removable Direct Access SCSI-6 device
Jan 4 12:14:07 freenas da0: Serial Number 4C530001220421122530
Jan 4 12:14:07 freenas da0: 40.000MB/s transfers
Jan 4 12:14:07 freenas da0: 14907MB (30529536 512 byte sectors: 255H 63S/T 1900C)
Jan 4 12:14:07 freenas da0: quirks=0x2<NO_6_BYTE>
Jan 4 12:14:07 freenas da1 at umass-sim1 bus 1 scbus9 target 0 lun 0
Jan 4 12:14:07 freenas da1: <SanDisk Cruzer Fit 1.27> Removable Direct Access SCSI-6 device
Jan 4 12:14:07 freenas da1: Serial Number 4C530001230421123032
Jan 4 12:14:07 freenas da1: 40.000MB/s transfers
Jan 4 12:14:07 freenas da1: 14907MB (30529536 512 byte sectors: 255H 63S/T 1900C)
Jan 4 12:14:07 freenas da1: quirks=0x2<NO_6_BYTE>
Jan 4 12:14:07 freenas ada0 at ahcich0 bus 0 scbus1 target 0 lun 0
Jan 4 12:14:07 freenas ada0: <WDC WD20EARX-00PASB0 51.0AB51> ATA-8 SATA 3.x device
Jan 4 12:14:07 freenas ada0: Serial Number WD-WCAZAD922496
Jan 4 12:14:07 freenas ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 8192bytes)
Jan 4 12:14:07 freenas ada0: Command Queueing enabled
Jan 4 12:14:07 freenas ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jan 4 12:14:07 freenas ada0: quirks=0x1<4K>
Jan 4 12:14:07 freenas ada0: Previously was known as ad4
Jan 4 12:14:07 freenas ada1 at ahcich1 bus 0 scbus2 target 0 lun 0
Jan 4 12:14:07 freenas ada1: <ST32000542AS CC34> ATA-8 SATA 2.x device
Jan 4 12:14:07 freenas ada1: Serial Number 5XW2MEHF
Jan 4 12:14:07 freenas ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jan 4 12:14:07 freenas ada1: Command Queueing enabled
Jan 4 12:14:07 freenas ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jan 4 12:14:07 freenas ada1: Previously was known as ad6
Jan 4 12:14:07 freenas ada2 at ahcich2 bus 0 scbus3 target 0 lun 0
Jan 4 12:14:07 freenas ada2: <SAMSUNG HD203WI 1AN10003> ATA-8 SATA 2.x device
Jan 4 12:14:07 freenas ada2: Serial Number S1UYJ1ZZ502105
Jan 4 12:14:07 freenas ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jan 4 12:14:07 freenas ada2: Command Queueing enabled
Jan 4 12:14:07 freenas ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jan 4 12:14:07 freenas ada2: Previously was known as ad8
Jan 4 12:14:07 freenas ada3 at ahcich3 bus 0 scbus4 target 0 lun 0
Jan 4 12:14:07 freenas ada3: <Hitachi HDS722020ALA330 JKAOA28A> ATA-8 SATA 2.x device
Jan 4 12:14:07 freenas ada3: Serial Number JK1130YAHSZ66T
Jan 4 12:14:07 freenas ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jan 4 12:14:07 freenas ada3: Command Queueing enabled
Jan 4 12:14:07 freenas ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jan 4 12:14:07 freenas ada3: Previously was known as ad10
Jan 4 12:14:07 freenas ada4 at ahcich4 bus 0 scbus5 target 0 lun 0
Jan 4 12:14:07 freenas ada4: <WDC WD20EZRX-00D8PB0 80.00A80> ATA-9 SATA 3.x device
Jan 4 12:14:07 freenas ada4: Serial Number WD-WMC4M0D2590F
Jan 4 12:14:07 freenas ada4: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jan 4 12:14:07 freenas ada4: Command Queueing enabled
Jan 4 12:14:07 freenas ada4: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jan 4 12:14:07 freenas ada4: quirks=0x1<4K>
Jan 4 12:14:07 freenas ada4: Previously was known as ad12
Jan 4 12:14:07 freenas ada5 at ahcich5 bus 0 scbus6 target 0 lun 0
Jan 4 12:14:07 freenas ada5: <Hitachi HDS722020ALA330 JKAOA3MA> ATA-8 SATA 2.x device
Jan 4 12:14:07 freenas ada5: Serial Number JK11A1YAJBYYWV
Jan 4 12:14:07 freenas ada5: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Jan 4 12:14:07 freenas ada5: Command Queueing enabled
Jan 4 12:14:07 freenas ada5: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Jan 4 12:14:07 freenas ada5: Previously was known as ad14
Jan 4 12:14:07 freenas SMP: AP CPU #1 Launched!
Jan 4 12:14:07 freenas SMP: AP CPU #2 Launched!
Jan 4 12:14:07 freenas SMP: AP CPU #5 Launched!
Jan 4 12:14:07 freenas SMP: AP CPU #6 Launched!
Jan 4 12:14:07 freenas SMP: AP CPU #4 Launched!
Jan 4 12:14:07 freenas SMP: AP CPU #3 Launched!
Jan 4 12:14:07 freenas SMP: AP CPU #7 Launched!
Jan 4 12:14:07 freenas Timecounter "TSC-low" frequency 1700032770 Hz quality 1000
Jan 4 12:14:07 freenas Trying to mount root from zfs:freenas-boot/ROOT/FreeNAS-9.3-STABLE-201512121950 []...
Jan 4 12:14:07 freenas GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
Jan 4 12:14:07 freenas ipmi0: <IPMI System Interface> port 0xca2,0xca3 on acpi0
Jan 4 12:14:07 freenas ipmi0: KCS mode found at io 0xca2 on acpi
Jan 4 12:14:07 freenas ipmi0: IPMI device rev. 1, firmware rev. 1.92, version 2.0
Jan 4 12:14:07 freenas ipmi0: Number of channels 2
Jan 4 12:14:07 freenas ipmi0: Attached watchdog
Jan 4 12:14:07 freenas ipmi1: <IPMI System Interface> on isa0
Jan 4 12:14:07 freenas device_attach: ipmi1 attach returned 16
Jan 4 12:14:07 freenas wbwd0: DevID 0xc3 DevRev 0x33, will not attach, please report this.
Jan 4 12:14:07 freenas wbwd0: HEFRAS and EFER do not align: EFER 0x4e DevID 0x00 DevRev 0x00 CR26 0x00
Jan 4 12:14:10 freenas GEOM_ELI: Device ada0p1.eli created.
Jan 4 12:14:10 freenas GEOM_ELI: Encryption: AES-XTS 256
Jan 4 12:14:10 freenas GEOM_ELI: Crypto: hardware
Jan 4 12:14:11 freenas GEOM_ELI: Device ada3p1.eli created.
Jan 4 12:14:11 freenas GEOM_ELI: Encryption: AES-XTS 256
Jan 4 12:14:11 freenas GEOM_ELI: Crypto: hardware
Jan 4 12:14:11 freenas GEOM_ELI: Device ada5p1.eli created.
Jan 4 12:14:11 freenas GEOM_ELI: Encryption: AES-XTS 256
Jan 4 12:14:11 freenas GEOM_ELI: Crypto: hardware
Jan 4 12:14:11 freenas GEOM_ELI: Device ada4p1.eli created.
Jan 4 12:14:11 freenas GEOM_ELI: Encryption: AES-XTS 256
Jan 4 12:14:11 freenas GEOM_ELI: Crypto: hardware
Jan 4 12:14:11 freenas GEOM_ELI: Device ada1p1.eli created.
Jan 4 12:14:11 freenas GEOM_ELI: Encryption: AES-XTS 256
Jan 4 12:14:11 freenas GEOM_ELI: Crypto: hardware
Jan 4 12:14:12 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Jan 4 12:14:12 freenas vboxdrv: fAsync=0 offMin=0x1f4 offMax=0xec7
Jan 4 12:14:15 freenas ntpd[2534]: ntpd 4.2.4p5-a (1)
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: /usr/local/bin/net -d 0 getlocalsid
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: zfs list -H -o mountpoint
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: zfs list -H -o mountpoint
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: zfs list -H -o mountpoint
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: zfs list -H -o mountpoint
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: /usr/local/bin/net -d 0 getlocalsid
Jan 4 12:14:19 freenas generate_smb4_conf.py: [common.pipesubr:71] Popen()ing: /usr/local/bin/net -d 0 setlocalsid S-1-5-21-3340196178-2627841965-3997456428
Jan 4 12:14:20 freenas nmbd[2810]: [2016/01/04 12:14:20.350284, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 4 12:14:20 freenas winbindd[2816]: [2016/01/04 12:14:20.471320, 0] ../source3/winbindd/winbindd_cache.c:3196(initialize_winbindd_cache)
Jan 4 12:14:20 freenas winbindd[2816]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
Jan 4 12:14:20 freenas winbindd[2816]: [2016/01/04 12:14:20.474616, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 4 12:14:20 freenas smartd[2819]: Device: /dev/ada1, WARNING: A firmware update for this drive may be available,
Jan 4 12:14:20 freenas smartd[2819]: see the following Seagate web pages:
Jan 4 12:14:20 freenas smartd[2819]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en
Jan 4 12:14:20 freenas smartd[2819]: http://knowledge.seagate.com/articles/en_US/FAQ/213915en
Jan 4 12:14:20 freenas smartd[2819]: Device: /dev/ada1, WARNING: A firmware update for this drive may be available,
Jan 4 12:14:20 freenas smartd[2819]: see the following Seagate web pages:
Jan 4 12:14:20 freenas smartd[2819]: http://knowledge.seagate.com/articles/en_US/FAQ/207931en
Jan 4 12:14:20 freenas smartd[2819]: http://knowledge.seagate.com/articles/en_US/FAQ/213915en
Jan 4 12:14:22 freenas smbd[2813]: [2016/01/04 12:14:22.852869, 0] ../lib/util/become_daemon.c:136(daemon_ready)
Jan 4 12:14:22 freenas smbd[2813]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 1
Jan 4 12:14:22 freenas ntpd[2535]: time reset -0.847441 s
Jan 4 12:14:23 freenas smbd[2813]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 2
Jan 4 12:14:24 freenas smbd[2813]: dnssd_clientstub ConnectToServer: connect()-> No of tries: 3
Jan 4 12:14:25 freenas smbd[2813]: dnssd_clientstub ConnectToServer: connect() failed Socket:33 Err:-1 Errno:2 No such file or directory
Jan 4 12:14:26 freenas smartd[2819]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Jan 4 12:14:26 freenas smartd[2819]: Device: /dev/ada1, 1 Offline uncorrectable sectors
Jan 4 12:14:26 freenas smartd[2819]: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
Jan 4 12:14:26 freenas smartd[2819]: Device: /dev/ada1, 1 Offline uncorrectable sectors
Jan 4 12:14:40 freenas bridge0: Ethernet address: 02:a2:90:82:11:00
Jan 4 12:14:40 freenas kernel: bridge0: link state changed to UP
Jan 4 12:14:40 freenas kernel: bridge0: link state changed to UP
Jan 4 12:14:40 freenas kernel: igb0: promiscuous mode enabled
Jan 4 12:14:40 freenas epair0a: Ethernet address: 02:28:c8:00:08:0a
Jan 4 12:14:40 freenas epair0b: Ethernet address: 02:28:c8:00:09:0b
Jan 4 12:14:40 freenas kernel: epair0a: link state changed to UP
Jan 4 12:14:40 freenas kernel: epair0a: link state changed to UP
Jan 4 12:14:40 freenas kernel: epair0b: link state changed to UP
Jan 4 12:14:40 freenas kernel: epair0b: link state changed to UP
Jan 4 12:14:40 freenas kernel: epair0a: promiscuous mode enabled
Jan 4 12:14:40 freenas kernel: igb0: link state changed to DOWN
Jan 4 12:14:40 freenas kernel: igb0: link state changed to DOWN
Jan 4 12:14:41 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 4 12:14:41 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair0b
Jan 4 12:14:45 freenas kernel: igb0: link state changed to UP
Jan 4 12:14:45 freenas kernel: igb0: link state changed to UP
Jan 4 12:14:49 freenas epair1a: Ethernet address: 02:e1:0b:00:09:0a
Jan 4 12:14:49 freenas epair1b: Ethernet address: 02:e1:0b:00:0a:0b
Jan 4 12:14:49 freenas kernel: epair1a: link state changed to UP
Jan 4 12:14:49 freenas kernel: epair1a: link state changed to UP
Jan 4 12:14:49 freenas kernel: epair1b: link state changed to UP
Jan 4 12:14:49 freenas kernel: epair1b: link state changed to UP
Jan 4 12:14:49 freenas kernel: epair1a: promiscuous mode enabled
Jan 4 12:14:49 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jan 4 12:14:49 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair1b
Jan 4 12:14:54 freenas epair2a: Ethernet address: 02:7b:36:00:0a:0a
Jan 4 12:14:54 freenas epair2b: Ethernet address: 02:7b:36:00:0b:0b
Jan 4 12:14:54 freenas kernel: epair2a: link state changed to UP
Jan 4 12:14:54 freenas kernel: epair2a: link state changed to UP
Jan 4 12:14:54 freenas kernel: epair2b: link state changed to UP
Jan 4 12:14:54 freenas kernel: epair2b: link state changed to UP
Jan 4 12:14:54 freenas kernel: epair2a: promiscuous mode enabled
Jan 4 12:14:54 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 4 12:14:54 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 4 12:16:01 freenas autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs snapshot "FNPool@auto-20160104.1216-2w"
Jan 4 12:16:01 freenas autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "FNPool@auto-20151221.1200-2w"
Jan 4 12:17:59 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or directory
Jan 4 12:17:59 freenas notifier: geli: No such device: /dev/ada2p1.
Jan 4 12:18:01 freenas notifier: 32+0 records in
Jan 4 12:18:01 freenas notifier: 32+0 records out
Jan 4 12:18:01 freenas notifier: 33554432 bytes transferred in 2.052611 secs (16347194 bytes/sec)
Jan 4 12:18:01 freenas notifier: dd: /dev/ada2: short write on character device
Jan 4 12:18:01 freenas notifier: dd: /dev/ada2: end of device
Jan 4 12:18:01 freenas notifier: 33+0 records in
Jan 4 12:18:01 freenas notifier: 32+1 records out
Jan 4 12:18:01 freenas notifier: 33644544 bytes transferred in 0.195855 secs (171783007 bytes/sec)
Jan 4 12:18:03 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or directory
Jan 4 12:18:03 freenas notifier: geli: No such device: /dev/ada2p1.
Jan 4 12:18:03 freenas manage.py: [middleware.exceptions:37] [MiddlewareError: Disk replacement failed: "invalid vdev specification, use '-f' to override the following errors:, /dev/gptid/1cafd63a-b307-11e5-9777-0cc47a6be4a4 is part of potentially active pool 'DellNas', "]
Jan 4 12:21:21 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or directory
Jan 4 12:21:21 freenas notifier: geli: No such device: /dev/ada2p1.
Jan 4 12:21:23 freenas notifier: 32+0 records in
Jan 4 12:21:23 freenas notifier: 32+0 records out
Jan 4 12:21:23 freenas notifier: 33554432 bytes transferred in 2.047053 secs (16391581 bytes/sec)
Jan 4 12:21:23 freenas notifier: dd: /dev/ada2: short write on character device
Jan 4 12:21:23 freenas notifier: dd: /dev/ada2: end of device
Jan 4 12:21:23 freenas notifier: 33+0 records in
Jan 4 12:21:23 freenas notifier: 32+1 records out
Jan 4 12:21:23 freenas notifier: 33644544 bytes transferred in 0.173498 secs (193919010 bytes/sec)
Jan 4 12:21:25 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or directory
Jan 4 12:21:25 freenas notifier: geli: No such device: /dev/ada2p1.
Jan 4 12:21:25 freenas manage.py: [middleware.exceptions:37] [MiddlewareError: Disk replacement failed: "invalid vdev specification, use '-f' to override the following errors:, /dev/gptid/957443f1-b307-11e5-9777-0cc47a6be4a4 is part of potentially active pool 'DellNas', "]
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
Hi,

I think i may have had to much data. I took the drive out, put it in a windows machine, formatted the drive to NTFS. Wrote some data to the drive. Then put the drive back into the freenas box & tried again to add the disk into my FNPool volume:

Jan 4 15:01:24 freenas kernel: epair2b: link state changed to UP
Jan 4 15:01:24 freenas kernel: epair2a: promiscuous mode enabled
Jan 4 15:01:24 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 4 15:01:24 freenas kernel: ng_ether_ifnet_arrival_event: can't re-name node epair2b
Jan 4 15:02:00 freenas autosnap.py: [tools.autosnap:71] Popen()ing: /sbin/zfs destroy -r -d "FNPool@auto-20151221.1500-2w"
Jan 4 15:05:51 freenas notifier: 32+0 records in
Jan 4 15:05:51 freenas notifier: 32+0 records out
Jan 4 15:05:51 freenas notifier: 33554432 bytes transferred in 2.136485 secs (15705437 bytes/sec)
Jan 4 15:05:52 freenas notifier: dd: /dev/ada2: short write on character device
Jan 4 15:05:52 freenas notifier: dd: /dev/ada2: end of device
Jan 4 15:05:52 freenas notifier: 33+0 records in
Jan 4 15:05:52 freenas notifier: 32+1 records out
Jan 4 15:05:52 freenas notifier: 33644544 bytes transferred in 0.172519 secs (195019390 bytes/sec)
Jan 4 15:05:54 freenas notifier: swapoff: /dev/ada2p1.eli: No such file or directory
Jan 4 15:05:54 freenas notifier: geli: No such device: /dev/ada2p1.
Jan 4 15:05:54 freenas manage.py: [middleware.exceptions:37] [MiddlewareError: Disk replacement failed: "invalid vdev specification, use '-f' to override the following errors:, /dev/gptid/8f4930ff-b31e-11e5-9b55-0cc47a6be4a4 is part of potentially active pool 'DellNas', "]


Any idea what I am doing wrong? I will rebuild the DellNas at some point in the future but I want to figure out how to fix the FNpool.

Thanks,
Rich
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
I wiped the drive via the gui & am adding it back in. Not sure how to monitor the rebuild status though.


Smart status with smartctl -a /dev/ada1 | less


smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p28 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda LP
Device Model: ST32000542AS
Serial Number: 5XW2MEHF
LU WWN Device Id: 5 000c50 032ce8b0e
Firmware Version: CC34
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5900 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, 3.0 Gb/s
Local Time is: Mon Jan 4 15:38:29 2016 EST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213915en

SMART support is: Available - device has SMART capability.
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p28 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda LP
Device Model: ST32000542AS
Serial Number: 5XW2MEHF
LU WWN Device Id: 5 000c50 032ce8b0e
Firmware Version: CC34
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5900 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, 3.0 Gb/s
Local Time is: Mon Jan 4 15:38:29 2016 EST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213915en

SMART support is: Available - device has SMART capability.
smartctl 6.3 2014-07-26 r3976 [FreeBSD 9.3-RELEASE-p28 amd64] (local build)
Copyright (C) 2002-14, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Seagate Barracuda LP
Device Model: ST32000542AS
Serial Number: 5XW2MEHF
LU WWN Device Id: 5 000c50 032ce8b0e
Firmware Version: CC34
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5900 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, 3.0 Gb/s
Local Time is: Mon Jan 4 15:38:29 2016 EST

==> WARNING: A firmware update for this drive may be available,
see the following Seagate web pages:
http://knowledge.seagate.com/articles/en_US/FAQ/207931en
http://knowledge.seagate.com/articles/en_US/FAQ/213915en

SMART support is: Available - device has SMART capability.

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: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 437) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.

SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_
FAILED RAW_VALUE

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 116 099 006 Pre-fail Always -
105449409
3 Spin_Up_Time 0x0003 100 100 000 Pre-fail Always -
0
4 Start_Stop_Count 0x0032 099 099 020 Old_age Always -
1190
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always -
0
7 Seek_Error_Rate 0x000f 079 060 030 Pre-fail Always -
52718333034
9 Power_On_Hours 0x0032 062 062 000 Old_age Always -
34078
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always -
0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always -
156
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always -
0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always -

184 End-to-End_Error 0x0032 100 100 099 Old_age Always -
0
187 Reported_Uncorrect 0x0032 072 072 000 Old_age Always -
28
188 Command_Timeout 0x0032 100 099 000 Old_age Always -
4295032837
189 High_Fly_Writes 0x003a 097 097 000 Old_age Always -
3
190 Airflow_Temperature_Cel 0x0022 061 041 045 Old_age Always In_th
e_past 39 (1 93 39 32 0)
194 Temperature_Celsius 0x0022 039 059 000 Old_age Always -
39 (0 5 0 0 0)
195 Hardware_ECC_Recovered 0x001a 035 025 000 Old_age Always -
105449409
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always -
1
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline -
1
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always -
0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline -
32705 (158 163 0)
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline
1918098655
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline -
198342938

SMART Error Log Version: 1
ATA Error Count: 66 (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 66 occurred at disk power-on lifetime: 8226 hours (342 days + 18 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 ff ff ff 4f 00 00:07:23.907 READ FPDMA QUEUED
60 00 40 ff ff ff 4f 00 00:07:23.863 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:23.863 READ FPDMA QUEUED
60 00 00 18 08 60 40 00 00:07:23.862 READ FPDMA QUEUED
60 00 a8 18 09 60 40 00 00:07:23.862 READ FPDMA QUEUED

Error 65 occurred at disk power-on lifetime: 8226 hours (342 days + 18 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 08 ff ff ff 4f 00 00:07:16.439 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:16.439 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:16.439 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:16.434 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:16.433 READ FPDMA QUEUED

Error 64 occurred at disk power-on lifetime: 8226 hours (342 days + 18 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 ff ff ff 4f 00 00:07:12.657 READ FPDMA QUEUED
60 00 40 ff ff ff 4f 00 00:07:12.636 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:12.635 READ FPDMA QUEUED
2f 00 01 10 00 00 40 00 00:07:12.611 READ LOG EXT
60 00 10 ff ff ff 4f 00 00:07:08.974 READ FPDMA QUEUED

Error 63 occurred at disk power-on lifetime: 8226 hours (342 days + 18 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 ff ff ff 4f 00 00:07:08.974 READ FPDMA QUEUED
60 00 40 ff ff ff 4f 00 00:07:08.959 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:08.958 READ FPDMA QUEUED
2f 00 01 10 00 00 40 00 00:07:08.877 READ LOG EXT
60 00 10 ff ff ff 4f 00 00:07:05.216 READ FPDMA QUEUED

Error 62 occurred at disk power-on lifetime: 8226 hours (342 days + 18 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 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455

Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 00 10 ff ff ff 4f 00 00:07:05.216 READ FPDMA QUEUED
60 00 08 ff ff ff 4f 00 00:07:05.214 READ FPDMA QUEUED
60 00 40 ff ff ff 4f 00 00:07:05.195 READ FPDMA QUEUED
60 00 10 ff ff ff 4f 00 00:07:05.195 READ FPDMA QUEUED
ec 00 00 00 00 00 40 00 00:07:05.111 IDENTIFY DEVICE

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

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.

(END)
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
To check the status:

zpool status {poolname}
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
Thanks - i ended up wiping hte drive from the other freenas pool and was able to add it to the degraded pool.

In terms of ADA1 -
  • CRITICAL: Device: /dev/ada1, 1 Currently unreadable (pending) sectors
  • CRITICAL: Device: /dev/ada1, 1 Offline uncorrectable sectors
What should I do to fix this?

Thanks,
Rich
 
danb35

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
RichTJ99 said:
What should I do to fix this?
Click to expand...
The only way to "fix" this is to replace ada1 as well. However, they don't indicate a critical problem at this time. I'd monitor those. If the numbers start going up, time to replace, but if they're steady at 1, I wouldn't think it's a major concern. Your drive otherwise looks reasonably healthy--warm (it's at 39C, and we want to see no more than 40C), but within tolerance. It's had some SMART errors, but they were 26,000 hours ago, so I wouldn't think they're a significant present concern.
 
danb35

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
RichTJ99 said:
I am using the web 'shell' - is there a way to scroll up?
Click to expand...
This is one of many reasons not to use the web shell unless absolutely necessary. Set up ssh on the server and ssh into it.
 
R

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
RichTJ99 said:
i ended up wiping hte drive from the other freenas pool and was able to add it to the degraded pool.
Click to expand...
Do you mean you followed the replacement procedure? If not, exactly what did you do? Consider posting the output from zpool status (between CODE tags for legibility).
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
I took an extra 2tb drive from a spare freenas box I had running (dellnas) and put it into my main freenas (FNPool). It would not add the disk from the Dellnas pool. I wiped that drive, then added it to the FNPool & seems to be OK. Please see the results below.

Zpool status:

Code:
[root@freenas] ~# zpool status
  pool: FNPool
 state: ONLINE
  scan: resilvered 347G in 2h15m with 0 errors on Mon Jan  4 17:51:49 2016
config:

        NAME                                            STATE     READ WRITE CKS                                                                                                                                                             UM
        FNPool                                          ONLINE       0     0                                                                                                                                                                  0
          raidz2-0                                      ONLINE       0     0                                                                                                                                                                  0
            gptid/ebd46b58-a34e-11e5-86c5-0cc47a6be4a4  ONLINE       0     0                                                                                                                                                                  0
            gptid/ec346e71-a34e-11e5-86c5-0cc47a6be4a4  ONLINE       0     0                                                                                                                                                                  0
            gptid/ec9b31d2-a34e-11e5-86c5-0cc47a6be4a4  ONLINE       0     0                                                                                                                                                                  0
            gptid/cff9dda6-b322-11e5-9b55-0cc47a6be4a4  ONLINE       0     0                                                                                                                                                                  0
            gptid/edc8e892-a34e-11e5-86c5-0cc47a6be4a4  ONLINE       0     0                                                                                                                                                                  0
            gptid/ee249ed8-a34e-11e5-86c5-0cc47a6be4a4  ONLINE       0     0                                                                                                                                                                  0

errors: No known data errors

  pool: freenas-boot
 state: ONLINE
  scan: none requested
config:

        NAME        STATE     READ WRITE CKSUM
        freenas-boot  ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            da0p2   ONLINE       0     0     0
            da1p2   ONLINE       0     0     0

errors: No known data errors
 
Bidule0hm

Bidule0hm

Server Electronics Sorcerer
Joined
Aug 5, 2013
Messages
3,710
Everything looks good ;)
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
So the drive with the smart error - ADA1 - is there anything i can do to fix it or shut it up? I hate to start ignoring the daily smart errors & miss something important.
 
Bidule0hm

Bidule0hm

Server Electronics Sorcerer
Joined
Aug 5, 2013
Messages
3,710
Well, keep it as a spare, 1 bad sector isn't really a big deal, what you don't want is the number to increase to more than something like a dozen ;)
 
R

RichTJ99

Patron
Joined
Sep 12, 2013
Messages
384
The drive is still under warranty (WD green 2tb), should I do an advanced RMA?

The other 2TB drive that died (top of thread) is also still under warranty & going back to WD. If i pull part of a raidz2 drive & send it back is the data recoverable (if the WD engineers wanted to look)?
 
R

Robert Trevellyan

Pony Wrangler
Joined
May 16, 2014
Messages
3,778
RichTJ99 said:
is there anything i can do to fix it or shut it up?
Click to expand...
You can try to force a drive to remap bad sectors by wiping it, e.g. with DBAN or badblocks, but that means removing it from your pool, at least temporarily.
RichTJ99 said:
The drive is still under warranty
Click to expand...
In that case, return it.
RichTJ99 said:
is the data recoverable
Click to expand...
There is a small possibility of data leakage, so if it's a real concern, wipe it before returning it.
 
Status
Not open for further replies.

Similar threads

F
  • Locked
Critical Alert
Replies
4
Views
1K
jgreco
jgreco
B
  • Locked
Worrying looking errors!!!!
2
Replies
23
Views
5K
b0redom
B
selfsame
  • Locked
System hangs at night
Replies
4
Views
2K
selfsame
selfsame
S
What does this really mean ? Device: /dev/ada2, 3 Currently unreadable (pending) sectors
Replies
9
Views
2K
danb35
danb35
adrianwi
  • Locked
Offline unreadable/uncorrectable sectors
Replies
11
Views
4K
Bidule0hm
Bidule0hm
Top