Cheapest SSDs for jails that work

[alexhore]

So I built a new NAS a while ago couple USB for mirrored boot, couple of 4tb for storage and a couple of cheap Sandisk 60gb for jails.

I get the error below, turning it off fully and booting and re-silvering clears is and its find for a few hours to a few weeks but then one of them dies again. Power cycles of a few seconds are enough to bring it back so I honestly believe the drives are ok just BSD doesn't like them or maybe I have done something I shouldn't have, pro tips anyone, maybe ZFS should not be used for SSD and it's killing them.

Currently setup as single partition ZFS with just the jails on them.

If you have some things I can try / test would appreciate it but searching the forum I find people just telling you to go buy a Samsung SSD.

If I have to I'll go out and buy two Sammy drives just need to know someone is using them without issue and version to buy.

Budget is small thus cheap since I'm only using 8GB of space on the pool.

Thanks in advance

Edit, re-checked actualy Corsair drives

Build FreeNAS-9.10-MASTER-201604171730 (a62b0b2)
Platform Intel(R) Xeon(R) CPU L5410 @ 2.33GHz
S5000XVNSATA MOBO

Memory 16329MB
On board SATA Ports 0 and 1 = 2 x 4TB spinners no issues at all.
On board SATA Ports 2 and 3 = 2 x Corsair Force LS v2 2.5" 60GB 2.5 SSD
AHCI mode

Code:

 pool: System
state: DEGRADED
status: One or more devices could not be opened.  Sufficient replicas exist for
   the pool to continue functioning in a degraded state.
action: Attach the missing device and online it using 'zpool online'.
  see: http://illumos.org/msg/ZFS-8000-2Q
scan: scrub repaired 0 in 0h1m with 0 errors on Sat Apr 16 21:58:12 2016
config:

   NAME                                            STATE     READ WRITE CKSUM
   System                                          DEGRADED     0     0     0
     mirror-0                                      DEGRADED     0     0     0
       gptid/4a7b260a-97b8-11e5-a90c-001517e1ee7c  ONLINE       0     0     0
       7059177815891921569                         UNAVAIL      0     0     0  was /dev/gptid/4aefc948-97b8-11e5-a90c-001517e1ee7c

errors: No known data errors

Sent from my iPhone using Tapatalk

 

[nightshade00013]

Specs on the system are needed. Possibly the controller or worse could be a raid card dropping the drive.

https://forums.freenas.org/index.php?threads/forum-rules.22553/

 

[BigDave]

Specs on the system are needed. Possibly the controller or worse could be a raid card dropping the drive

^^^^THIS^^^^

Since the offending SSD is not available (shown above) take it out, plug it up to another machine
and use Sandisk tool on it. If this tool shows no issues with the drive itself:

1. check data cables (swap 'em/replace 'em)
2. switch SATA ports, see if issue follows device or port.
   

   maybe ZFS should not be used for SSD and it's killing them.

   It's more likely gonna be something else first...
   

 

[alexhore]

Specs on the system are needed. Possibly the controller or worse could be a raid card dropping the drive.

https://forums.freenas.org/index.php?threads/forum-rules.22553/

Updated, controller is fine with the spinners if that matters I dont know.

 

[alexhore]

^^^^THIS^^^^

Since the offending SSD is not available (shown above) take it out, plug it up to another machine
and use Sandisk tool on it. If this tool shows no issues with the drive itself:

1. check data cables (swap 'em/replace 'em)
2. switch SATA ports, see if issue follows device or port.
   
   It's more likely gonna be something else first...

Updated post with spec.

Brand new server grade cables no errors occuring sugesting consistant data flow.

Ill try port swapping.

Ill try testing the drive, in another machine but I bought three at the same time and the other is working a dream i the laptop its in but these two drop out.

I was planning on doing these things but the point of the post was to see if I am doing something blindingly stupid like even putting them in ZFS or putting jails on them or not turning something on/off or moving system dataset?????

 

[BigDave]

I was planning on doing these things but the point of the post was to see if I am doing something blindingly stupid like even putting them in ZFS or putting jails on them or not turning something on/off or moving system dataset?????

Lots of folks are using SSD drives for jails now, most of the failures reported (and there not many either) are hardware/controller related.
We are just asking questions and being diligent so you don't buy Sammys and have the same trouble with them.
Please understand that we are constantly having to poke peeps with a stick to get them to cough up basic information.
We enjoy helping people, that's why we're here, but some times noobs get frustrated with our "hardware first" mentality.
There are wear issues with some models of SSDs, but for the most part, those issues come after many hours of use.
I'm not familiar with your board, but it appears to have two different controllers, are the spinners and the SSDs all connected
to the blue ports (one controller) OR are the drives split between the black ports and the blue ports (different controllers).
Again, i'm not familiar with the board and could be talkin' out of my a$$ here...

 

[alexhore]

Sorry appreciate the help didn't mean to sound like I wasn't greatfull.

Didn't realise I pasted a url to newegg ignore that image it's the wrong image.

There are 2 or three versions of the board the one I have (the model number above is right) dose not have the sas controller so all the 6 ports (which are black) are connected to the onboard esb2-e.

Thanks again


Sent from my iPhone using Tapatalk

 

[jgreco]

Edit, re-checked actualy Corsair drives

Build FreeNAS-9.10-MASTER-201604171730 (a62b0b2)
Platform Intel(R) Xeon(R) CPU L5410 @ 2.33GHz
S5000XVNSATA MOBO

Wow. Really? Okay, well, just listen and don't start seeing red immediately, 'k?

First, that's a decade-old board. That's putting it on the wrong end of the "board is likely to be developing flakiness" slope.

Second, it gets its SATA from an Intel ESB2-E embedded RAID I/O controller, which is probably not swimmingly well supported. I'd be curious to see the related dmesg entries. There was a long while where the embedded RAID controllers were only sorta-reliable under FreeBSD.

Third, the Corsair SSD's are kinda old tech and may have bugs. If nothing else, make sure their firmware is up to date.

Fourth, that board was designed before SSD's, so it is entirely possible that you are the first person on the planet to have tried that board with its controller, with the Corsair SSD, with a current version of FreeNAS. There could be all sorts of problems such as "no one ever tried to cram data from a drive to the controller at SSD speeds."

I'm not saying your problems are unfixable, but I just want you to be prepared for the possibility that you are doing something that won't work out, even if we think it ought to.

 

[alexhore]

Wow. Really? Okay, well, just listen and don't start seeing red immediately, 'k?

First, that's a decade-old board. That's putting it on the wrong end of the "board is likely to be developing flakiness" slope.

Second, it gets its SATA from an Intel ESB2-E embedded RAID I/O controller, which is probably not swimmingly well supported. I'd be curious to see the related dmesg entries. There was a long while where the embedded RAID controllers were only sorta-reliable under FreeBSD.

Third, the Corsair SSD's are kinda old tech and may have bugs. If nothing else, make sure their firmware is up to date.

Fourth, that board was designed before SSD's, so it is entirely possible that you are the first person on the planet to have tried that board with its controller, with the Corsair SSD, with a current version of FreeNAS. There could be all sorts of problems such as "no one ever tried to cram data from a drive to the controller at SSD speeds."

I'm not saying your problems are unfixable, but I just want you to be prepared for the possibility that you are doing something that won't work out, even if we think it ought to.

My beans are chilled [emoji106]

Get your points about the board, just to be clear it's been in storage until last year as it was a replacement but took so long to arrive the server was swapped out so it was never used till now. Still valid points about it being old tech though.

I'm happy to pull logs from anywhere it might help just not sure where to start I'll google dmesg and start with that.

I did a firmware update before installing last year knowing I can't easily get under the hood but I'll put it on the list of things to do.

Might even work out cheaper to install a very basic pcie controller?

 

[jgreco]

Well, we don't really know what's wrong, so basically this boils down to trying things until there's an "aha" moment.

For the dmesg, you can find /var/run/dmesg.boot on your FreeNAS system which holds the recorded copy of what kernel messages spat out when the system booted. This tends to include a wealth of useful and also useless information. You can use something like PuTTY to ssh into your server if that makes retrieval more easy. I'm not holding out any great hopes that there would be happy revelations in there, but it gives us something more to work with. Post the content in CODE tags if you can.

 

[alexhore]

Well, we don't really know what's wrong, so basically this boils down to trying things until there's an "aha" moment.

For the dmesg, you can find /var/run/dmesg.boot on your FreeNAS system which holds the recorded copy of what kernel messages spat out when the system booted. This tends to include a wealth of useful and also useless information. You can use something like PuTTY to ssh into your server if that makes retrieval more easy. I'm not holding out any great hopes that there would be happy revelations in there, but it gives us something more to work with. Post the content in CODE tags if you can.

Code:

Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.3-RELEASE #4 f935af8(freebsd10): Sat Apr 16 10:32:06 PDT 2016
    root@build.ixsystems.com:/tank/home/nightlies/build-freenas9/_BE/objs/tank/$
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Xeon(R) CPU           L5410  @ 2.33GHz (2327.55-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x1067a  Family=0x6  Model=0x17  Stepping=10
  Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,$
  Features2=0xc0ce3bd<SSE3,DTES64,MON,DS_CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,D$
  AMD Features=0x20100800<SYSCALL,NX,LM>
  AMD Features2=0x1<LAHF>
  VT-x: HLT,PAUSE
  TSC: P-state invariant, performance statistics
real memory  = 18790481920 (17920 MB)
avail memory = 16540053504 (15773 MB)
Event timer "LAPIC" quality 400
ACPI APIC Table: <INTEL  S5000XVN>
FreeBSD/SMP: Multiprocessor System Detected: 8 CPUs
FreeBSD/SMP: 2 package(s) x 4 core(s)
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
cpu2 (AP): APIC ID:  2
cpu3 (AP): APIC ID:  3
cpu4 (AP): APIC ID:  4
cpu5 (AP): APIC ID:  5
cpu6 (AP): APIC ID:  6
cpu7 (AP): APIC ID:  7
random: <Software, Yarrow> initialized
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ioapic1 <Version 2.0> irqs 24-47 on motherboard
lapic0: Forcing LINT1 to edge trigger
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: No AESNI support.
padlock0: No ACE support.
acpi0: <INTEL S5000XVN> on motherboard
acpi0: Power Button (fixed)
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
cpu4: <ACPI CPU> on acpi0
cpu5: <ACPI CPU> on acpi0
cpu6: <ACPI CPU> on acpi0
cpu7: <ACPI CPU> on acpi0
atrtc0: <AT realtime clock> port 0x70-0x71,0x74-0x77 irq 8 on acpi0
Event timer "RTC" frequency 32768 Hz quality 0
attimer0: <AT timer> port 0x40-0x43,0x50-0x53 irq 0 on acpi0
Timecounter "i8254" frequency 1193182 Hz quality 0
Event timer "i8254" frequency 1193182 Hz quality 100
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 350
Event timer "HPET1" frequency 14318180 Hz quality 340
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
acpi_button0: <Sleep Button> on acpi0
acpi_button1: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pcib1: <ACPI PCI-PCI bridge> at device 2.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> irq 16 at device 0.0 on pci2
pci3: <ACPI PCI bus> on pcib3
pcib4: <ACPI PCI-PCI bridge> irq 18 at device 2.0 on pci2
pci4: <ACPI PCI bus> on pcib4
em0: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0x3020-0x303f mem 0xb1$
em0: Using an MSI interrupt
em0: Ethernet address: 00:15:17:e1:ee:7c
em1: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0x3000-0x301f mem 0xb1$
em1: Using an MSI interrupt
em1: Ethernet address: 00:15:17:e1:ee:7d
pcib5: <ACPI PCI-PCI bridge> at device 0.3 on pci1
pci5: <ACPI PCI bus> on pcib5
vgapci0: <VGA-compatible display> port 0x2000-0x20ff mem 0xb0000000-0xb0ffffff,$
vgapci0: Boot video device
pcib6: <PCI-PCI bridge> at device 3.0 on pci0
pci6: <PCI bus> on pcib6
pcib7: <ACPI PCI-PCI bridge> at device 4.0 on pci0
pci7: <ACPI PCI bus> on pcib7
em2: <Intel(R) PRO/1000 Network Connection 7.6.1-k> port 0x1000-0x101f mem 0xb1$
em2: Using an MSI interrupt
em2: Ethernet address: 00:15:17:3a:20:ec
pcib8: <ACPI PCI-PCI bridge> at device 5.0 on pci0
pci8: <ACPI PCI bus> on pcib8
pcib9: <ACPI PCI-PCI bridge> at device 6.0 on pci0
pci9: <ACPI PCI bus> on pcib9
pcib10: <PCI-PCI bridge> at device 7.0 on pci0
pci10: <PCI bus> on pcib10
pci0: <multimedia, HDA> at device 27.0 (no driver attached)
pcib11: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci11: <ACPI PCI bus> on pcib11
uhci0: <Intel 631XESB/632XESB/3100 USB controller USB-1> port 0x40a0-0x40bf irq$
uhci0: LegSup = 0x2f00
usbus0 on uhci0
uhci1: <Intel 631XESB/632XESB/3100 USB controller USB-2> port 0x4080-0x409f irq$
uhci1: LegSup = 0x2f00
usbus1 on uhci1
uhci2: <Intel 631XESB/632XESB/3100 USB controller USB-3> port 0x4060-0x407f irq$
uhci2: LegSup = 0x2f00
usbus2 on uhci2
uhci3: <Intel 631XESB/632XESB/3100 USB controller USB-4> port 0x4040-0x405f irq$
uhci3: LegSup = 0x2f00
usbus3 on uhci3
ehci0: <Intel 63XXESB USB 2.0 controller> mem 0xb1f04400-0xb1f047ff irq 23 at d$
usbus4: EHCI version 1.0
usbus4 on ehci0
pcib12: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pci12: <ACPI PCI bus> on pcib12
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
ahci0: <Intel ESB2 AHCI SATA controller> port 0x40c8-0x40cf,0x40d4-0x40d7,0x40c$
ahci0: AHCI v1.10 with 6 3Gbps ports, Port Multiplier supported
ahcich0: <AHCI channel> at channel 0 on ahci0
ahcich1: <AHCI channel> at channel 1 on ahci0
ahcich2: <AHCI channel> at channel 2 on ahci0
ahcich3: <AHCI channel> at channel 3 on ahci0
ahcich4: <AHCI channel> at channel 4 on ahci0
ahcich5: <AHCI channel> at channel 5 on ahci0
atkbdc0: <Keyboard controller (i8042)> port 0x60,0x64 irq 1 on acpi0
atkbd0: <AT Keyboard> irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
ichwd0: <Intel 63XXESB watchdog timer> on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
ichwd0: <Intel 63XXESB watchdog timer> at port 0x430-0x437,0x460-0x47f on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff,0xc9000-0xc9ff$
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
coretemp2: <CPU On-Die Thermal Sensors> on cpu2
est2: <Enhanced SpeedStep Frequency Control> on cpu2
coretemp3: <CPU On-Die Thermal Sensors> on cpu3
est3: <Enhanced SpeedStep Frequency Control> on cpu3
coretemp4: <CPU On-Die Thermal Sensors> on cpu4
est4: <Enhanced SpeedStep Frequency Control> on cpu4
coretemp5: <CPU On-Die Thermal Sensors> on cpu5
est5: <Enhanced SpeedStep Frequency Control> on cpu5
coretemp6: <CPU On-Die Thermal Sensors> on cpu6
est6: <Enhanced SpeedStep Frequency Control> on cpu6
coretemp7: <CPU On-Die Thermal Sensors> on cpu7
est7: <Enhanced SpeedStep Frequency Control> on cpu7
ZFS filesystem version: 5
ZFS storage pool version: features support (5000)
Timecounters tick every 1.000 msec
ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logg$
random: unblocking device.
usbus0: 12Mbps Full Speed USB v1.0
usbus1: 12Mbps Full Speed USB v1.0
usbus2: 12Mbps Full Speed USB v1.0
usbus3: 12Mbps Full Speed USB v1.0
usbus4: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus0
ugen4.1: <Intel> at usbus4
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus4
ugen3.1: <Intel> at usbus3
uhub2: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus3
ugen2.1: <Intel> at usbus2
uhub3: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus2
ugen1.1: <Intel> at usbus1
uhub4: <Intel UHCI root HUB, class 9/0, rev 1.00/1.00, addr 1> on usbus1
uhub2: 2 ports with 2 removable, self powered
uhub3: 2 ports with 2 removable, self powered
uhub4: 2 ports with 2 removable, self powered
uhub0: 2 ports with 2 removable, self powered
uhub1: 8 ports with 8 removable, self powered
ugen4.2: <SanDisk> at usbus4
umass0: <SanDisk Ultra Fit, class 0/0, rev 2.10/1.00, addr 2> on usbus4
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:7:0:-1: Attached to scbus7
ugen4.3: <SanDisk> at usbus4
umass1: <SanDisk Ultra Fit, class 0/0, rev 2.10/1.00, addr 3> on usbus4
umass1:  SCSI over Bulk-Only; quirks = 0x8100
umass1:8:1:-1: Attached to scbus8
ahcich1: AHCI reset: device not ready after 31000ms (tfd = 00000080)
ahcich1: Poll timeout on slot 1 port 15
ahcich1: is 00000000 cs 00000002 ss 00000000 rs 00000002 tfd 80 serr 00000000 c$
(aprobe1:ahcich1:0:15:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00
(aprobe1:ahcich1:0:15:0): CAM status: Command timeout
(aprobe1:ahcich1:0:15:0): Error 5, Retries exhausted
run_interrupt_driven_hooks: still waiting after 60 seconds for xpt_config
ahcich1: Poll timeout on slot 2 port 15
ahcich1: is 00000000 cs 00000004 ss 00000000 rs 00000004 tfd 80 serr 00000000 c$
(aprobe1:ahcich1:0:15:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00
(aprobe1:ahcich1:0:15:0): CAM status: Command timeout
(aprobe1:ahcich1:0:15:0): Error 5, Retries exhausted
ahcich1: Poll timeout on slot 3 port 0
ahcich1: is 00000000 cs 00000008 ss 00000000 rs 00000008 tfd 80 serr 00000000 c$
(aprobe0:ahcich1:0:0:0): SOFT_RESET. ACB: 00 00 00 00 00 00 00 00 00 00 00 00
(aprobe0:ahcich1:0:0:0): CAM status: Command timeout
(aprobe0:ahcich1:0:0:0): Error 5, Retries exhausted
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <Corsair Force LS SSD S9FM02.0> ACS-3 ATA SATA 3.x device
ada0: Serial Number 1522811100010247002E
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 57241MB (117231408 512 byte sectors)
ada0: Previously was known as ad4
ada1 at ahcich2 bus 0 scbus2 target 0 lun 0
ada1: <ST4000VN000-1H4168 SC46> ACS-2 ATA SATA 3.x device
ada1: Serial Number S301EFQP
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 3815447MB (7814037168 512 byte sectors)
ada1: Previously was known as ad8
ada2 at ahcich3 bus 0 scbus3 target 0 lun 0
ada2: <ST4000VN000-1H4168 SC46> ACS-2 ATA SATA 3.x device
ada2: Serial Number S301FWR9
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 3815447MB (7814037168 512 byte sectors)
ada2: Previously was known as ad10
da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
da1 at umass-sim1 bus 1 scbus8 target 0 lun 0
da1: <SanDisk Ultra Fit 1.00> Removable Direct Access SPC-4 SCSI device
da1: Serial Number 4C530001280909113480
da1: 40.000MB/s transfers
da1: 14832MB (30375936 512 byte sectors)
da1: quirks=0x2<NO_6_BYTE>
da0: <SanDisk Ultra Fit 1.00> Removable Direct Access SPC-4 SCSI device
da0: Serial Number 4C531001500909113484
da0: 40.000MB/s transfers
da0: 14832MB (30375936 512 byte sectors)
da0: quirks=0x2<NO_6_BYTE>
lapic7: Forcing LINT1 to edge trigger
SMP: AP CPU #7 Launched!
lapic6: Forcing LINT1 to edge trigger
SMP: AP CPU #6 Launched!
lapic5: Forcing LINT1 to edge trigger
SMP: AP CPU #5 Launched!
lapic4: Forcing LINT1 to edge trigger
SMP: AP CPU #4 Launched!
lapic1: Forcing LINT1 to edge trigger
SMP: AP CPU #1 Launched!
lapic3: Forcing LINT1 to edge trigger
SMP: AP CPU #3 Launched!
lapic2: Forcing LINT1 to edge trigger
SMP: AP CPU #2 Launched!
Trying to mount root from zfs:freenas-boot/ROOT/9.10-MASTER-201604171730 []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
em2: link state changed to UP
ipmi0: <IPMI System Interface> port 0xca2,0xca3 on acpi0
ipmi0: KCS mode found at io 0xca2 on acpi
ipmi0: IPMI device rev. 1, firmware rev. 0.66, version 2.0

ipmi0: Number of channels 5
ipmi0: Attached watchdog
ichwd0: <Intel 63XXESB watchdog timer> at port 0x430-0x437,0x460-0x47f on isa0
ichwd0: ICH WDT present but disabled in BIOS or hardware
device_attach: ichwd0 attach returned 6
hwpmc: SOFT/16/64/0x67<INT,USR,SYS,REA,WRI> TSC/1/64/0x20<REA> IAP/2/40/0x3ff<I$
em2: link state changed to DOWN
em2: link state changed to UP
vboxdrv: fAsync=0 offMin=0x44b offMax=0x6874
GEOM_ELI: Device ada0p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: software
GEOM_ELI: Device ada1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: software
GEOM_ELI: Device ada2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 128
GEOM_ELI:     Crypto: software

 

[jgreco]

Well, when you booted the system, the system couldn't attach to ahcich1, which is presumably the second SSD.

That tends to suggest that the thing's flaking out. Can you power cycle and repeat? No need to post dmesg again, it's fine just to inspect it yourself.

 

[alexhore]

OK so looks like the latest update means im unable to shutdown, it restarts instead even via cli. Someone else had the same problem I dont care too much its always on I held the botton for a hard power down after the boad beeped during reset.

Both drives running latest firmware,

Code:

ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <Corsair Force LS SSD S9FM02.0> ACS-3 ATA SATA 3.x device
ada0: Serial Number 1522811100010247002E
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 57241MB (117231408 512 byte sectors)
ada0: Previously was known as ad4
ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
ada1: <Corsair Force LS SSD S9FM02.0> ACS-3 ATA SATA 3.x device
ada1: Serial Number 1522811100010247002F
ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada1: Command Queueing enabled
ada1: 57241MB (117231408 512 byte sectors)
ada1: Previously was known as ad6
ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
ada2: <ST4000VN000-1H4168 SC46> ACS-2 ATA SATA 3.x device
ada2: Serial Number S301EFQP
ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada2: Command Queueing enabled
ada2: 3815447MB (7814037168 512 byte sectors)
ada2: Previously was known as ad8
ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
ada3: <ST4000VN000-1H4168 SC46> ACS-2 ATA SATA 3.x device
ada3: Serial Number S301FWR9
ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada3: Command Queueing enabled
ada3: 3815447MB (7814037168 512 byte sectors)
ada3: Previously was known as ad10

Checked the smart status on both:

This one rarly drops out:

Code:

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   050    Pre-fail  Always       -       0/0
  5 Retired_Block_Count     0x0013   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours_and_Msec 0x0012   100   100   000    Old_age   Always       -       2674h+00m+00.000s
12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       108
162 Unknown_SandForce_Attr  0x0003   075   075   000    Pre-fail  Always       -       49
170 Reserve_Block_Count     0x0002   100   100   000    Old_age   Always       -       77
172 Erase_Fail_Count        0x0012   100   100   000    Old_age   Always       -       0
173 Unknown_SandForce_Attr  0x0000   100   100   000    Old_age   Offline      -       8585937
174 Unexpect_Power_Loss_Ct  0x0012   100   100   000    Old_age   Always       -       20
181 Program_Fail_Count      0x0012   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0012   100   100   000    Old_age   Always       -       3
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       20
194 Temperature_Celsius     0x0023   070   070   000    Pre-fail  Always       -       30
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
218 Unknown_SandForce_Attr  0x0000   100   100   000    Old_age   Offline      -       0
231 SSD_Life_Left           0x0013   100   100   000    Pre-fail  Always       -       95
241 Lifetime_Writes_GiB     0x0012   100   100   000    Old_age   Always       -       2312
242 Lifetime_Reads_GiB      0x0012   100   100   000    Old_age   Always       -       124
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 0
Note: revision number not 1 implies that no selective self-test has ever been run
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.

Nerly always this one that drops out:

Code:

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   050    Pre-fail  Always       -       0/0
  5 Retired_Block_Count     0x0013   100   100   050    Pre-fail  Always       -       0
  9 Power_On_Hours_and_Msec 0x0012   100   100   000    Old_age   Always       -       2088h+00m+00.000s
12 Power_Cycle_Count       0x0012   100   100   000    Old_age   Always       -       108
162 Unknown_SandForce_Attr  0x0003   075   075   000    Pre-fail  Always       -       49
170 Reserve_Block_Count     0x0002   100   100   000    Old_age   Always       -       77
172 Erase_Fail_Count        0x0012   100   100   000    Old_age   Always       -       0
173 Unknown_SandForce_Attr  0x0000   100   100   000    Old_age   Offline      -       6685249
174 Unexpect_Power_Loss_Ct  0x0012   100   100   000    Old_age   Always       -       23
181 Program_Fail_Count      0x0012   100   100   000    Old_age   Always       -       0
187 Reported_Uncorrect      0x0012   100   100   000    Old_age   Always       -       0
192 Power-Off_Retract_Count 0x0012   100   100   000    Old_age   Always       -       23
194 Temperature_Celsius     0x0023   070   070   000    Pre-fail  Always       -       30
196 Reallocated_Event_Count 0x0000   100   100   000    Old_age   Offline      -       0
218 Unknown_SandForce_Attr  0x0000   100   100   000    Old_age   Offline      -       0
231 SSD_Life_Left           0x0013   100   100   000    Pre-fail  Always       -       96
241 Lifetime_Writes_GiB     0x0012   100   100   000    Old_age   Always       -       1880
242 Lifetime_Reads_GiB      0x0012   100   100   000    Old_age   Always       -       152
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 0
Note: revision number not 1 implies that no selective self-test has ever been run
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.

Unexpected power loss is.... excpected we had a week or so of power trouble.

Lifetime Writes is insaine is this something to do with SystemDataset?

Just ran two long smart tests smartctl -t long and no problems there.

 

[MrToddsFriends]

Lifetime Writes is insaine is this something to do with SystemDataset?

On my "system dataset pool" consisting of two mirrored SanDisk X300s SSDs (64GByte) I see a data rate of 15 GBytes writes / week per device in FreeNAS 9.10 as reported from the FreeNAS GUI (which translates to 0.09 GBytes writes / hour).

Edit: Syslog checked, Reporting Database unchecked.

Nothing to worry about for me as that would translate into a lifetime of 2700 weeks (more than 50 years) on the basis of 40TBW. In FreeNAS 9.3.1 the data rate written to the system data set was roughly twice as high.

The numbers you are showing indicate a write rate in the range of 1 GByte / hour, which is ten times as much of what I see in FreeNAS 9.10. BUT: You are showing S.M.A.R.T numbers while I'm reading FreeNAS GUI numbers (presumably caught from ZFS logs). Did you already do some other write intensive stuff or tests outside of FreeNAS?

May I ask which version of FreeNAS/smartmontools you used to produce the output shown (and how the exact smartctl command looked like)? I'm seeing totally different attributes when using 'smartctl -a' or 'smartctl -x' and especially nothing like Lifetime_Writes_GiB in FreeNAS 9.10.

 

[alexhore]

I have resilvered and I'm waiting for it to drop again. Once I get a notification through I'm going to check what was going on when it dropped. I'll post back the commands I was using.


Sent from my iPhone using Tapatalk

 

[alexhore]

May I ask which version of FreeNAS/smartmontools you used to produce the output shown (and how the exact smartctl command looked like)? I'm seeing totally different attributes when using 'smartctl -a' or 'smartctl -x' and especially nothing like Lifetime_Writes_GiB in FreeNAS 9.10.

FreeNAS-9.10-Nightlies
smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.3-RELEASE amd64] (local build)
smartctl --scan
smartctl -i -a -d atacam ada0

 

[styno]

OK so looks like the latest update means im unable to shutdown, it restarts instead even via cli. Someone else had the same problem I dont care too much its always on I held the botton for a hard power down after the boad beeped during reset.

Fwiw: I am experiencing the same issue on an old Intel 5000 based board as well (Asus DSBV-D). I don't really care as it is just a test system but it should have something to do with powersave settings/WOL/Wake On [whatever]/....

As for your SSD issue: just don't trust the intel ESB with SSD drives. The aforementioned DSBV-D used to be my workstation with dual SSD's on the ESB's fakeraid (raid1) kicking out drives and resyncing the raid on a bi-weekly basis no matter what driverversions or OS I used.

 

[MrToddsFriends]

FreeNAS-9.10-Nightlies
smartctl 6.4 2015-06-04 r4109 [FreeBSD 10.3-RELEASE amd64] (local build)
smartctl --scan
smartctl -i -a -d atacam ada0

Thanks for your feedback. The smartctl version in FreeNAS-9.10-STABLE-201604261518 is identical, so the differences in reported attributes most likely are a consequence of different controller types (Phison PS3108 in your Corsair Force LS, Marvell 88SS9188 in my SanDisk X300s) and/or firmware stuff.

 

[alexhore]

As for your SSD issue: just don't trust the intel ESB with SSD drives. The aforementioned DSBV-D used to be my workstation with dual SSD's on the ESB's fakeraid (raid1) kicking out drives and resyncing the raid on a bi-weekly basis no matter what driverversions or OS I used.

Thanks for this, you prompted a fresh google session and I found a few people had issues with the ESB chipset with SSD regardless of using raid or not. It was only resolved with bios updates something intel on an old board wont be doing so its time for a new controller. On the upside i'm probably capping out the SSDs on that SATA2 controller anyway.

Ordered a card crossflashable to SAS2008 and ill hook that up to the 16x connector so its running direct to the s5000 chip skipping the ESB alltogether.

The 16x connector on the board only has 8 lanes and the are pcie 1.0 so the 8 lanes will run at half the potential speed of the card but thats still 2GBs theoretical.

The only decision I have left to make is leave the 2 spinners connected to the mainboard or move them onto this card with the SSDs input welcome, nothing wrong with them at present and they seem to perform OK giveing me 105MB per second. Edit just dropped a 4gb file both ways 115MB per second. Ill try it in the card for kicks.

 

[styno]

There is another option, but heavily depending on how brave/lucky/drunk you are: there are guides that describe how to break a BIOS update file into separate parts, update the raid controllers fw only and reassemble into a new BIOS update that you then can flash onto the board. I didn't feel dumb enough yet to try this ;). Your plan of attack seems the right thing to do...
Btw. If you happen to find a solution for the halt/reboot issue let me know.