Support Request - Permanent errors have been detected

Status
Not open for further replies.

darkmarauder99

Dabbler
Joined
Aug 6, 2014
Messages
11
I have been notified via email today that my FreeNAS server has an error.
After checking with zpool status -v I received the following message:-

errors: No known data errors

pool: freenas-boot
state: ONLINE
status: One or more devices has experienced an error resulting in data
corruption. Applications may be affected.
action: Restore the file in question if possible. Otherwise restore the
entire pool from backup.
see: http://illumos.org/msg/ZFS-8000-8A
scan: scrub repaired 0 in 0h1m with 0 errors on Tue Mar 3 03:46:13 2015
config:

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

errors: Permanent errors have been detected in the following files:

freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504100216:/usr/local/lib/libpang
o-1.0.so.0.3400.1
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504100216:/usr/local/lib/libpcre
.so.3


The FreeNAS OS itself is installed on a USB stick, if this helps.
 
Joined
Jan 9, 2015
Messages
430
Looks like the USB stick is starting to fail.

Do you have a backup of your config file?
 

darkmarauder99

Dabbler
Joined
Aug 6, 2014
Messages
11
Hello DifferentStrokes,


Yes I do have a current config backup.
I can also provide an identical USB stick.
 
Joined
Jan 9, 2015
Messages
430
If the problem has gotten too bad you will have to reinstall FreeNAS on the new USB stick. Once up and going you can import the config file and reboot.

As a side note: Consider using two USB drives in a mirror for your boot device. This will allow you to survive this problem still it arise again. Look in my signature for a link on how to do this.
 

darkmarauder99

Dabbler
Joined
Aug 6, 2014
Messages
11
Thank you very much for your replies, I'll start preparations to do the mirrored install. Are you aware of a recommended USB sticks for this usage?
 
Joined
Jan 9, 2015
Messages
430
People have been having good luck with the Sandisk Ultra Fits. 16GB would be a good size.
And...your welcome.
 

ric

Contributor
Joined
Dec 22, 2013
Messages
180
I have same exact situation here..

errors: Permanent errors have been detected in the following files:

freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504100216:/usr/local/lib/lib
o-1.0.so.0.3400.1
freenas-boot/ROOT/FreeNAS-9.3-STABLE-201504100216:/usr/local/lib/lib
.so.3

I don't have any backup of the config file either...

Now, how can I recover all my data (media files) from pool:tank > raidz1

Your help would be greatly appreciated.

Thanks.
 

danb35

Hall of Famer
Joined
Aug 16, 2011
Messages
15,504
If you can boot the USB, boot it and download the config file. If not, try to boot a previous boot environment (obviously, the more recent the better), and download the config file.

Then (whether or not you've been able to download a copy of your config) do a fresh install of the latest 9.3 build to a new USB stick. Boot from that stick. If you have a copy of the config file, upload it. If not, reconfigure your server from scratch, and let this be a lesson to you on why you should back up your config file. In any case, your data should be fine. Use Storage -> Import Volume to reattach your pool. And check out one of the how-to guides here for how to set up automatic backups of your config file.
 

ric

Contributor
Joined
Dec 22, 2013
Messages
180
I was able to recover the config file from the old usb stick, jails are back up and running however my 4x HDDs are not showing up inside Volume Manager anymore and all settings in the BIOS remain intact. All my data (media files) stored inside /mnt/tank directory. Verified all four HDDs are present in the BIOS. I'm so afraid to lost all the data. Please help.
 
Last edited:

ric

Contributor
Joined
Dec 22, 2013
Messages
180
Below is a photo of the Storage>Import volume :
and, below is the error message when I attempted to import the Volume (freenas-boot [zfs,id=12851344349533850630]).


"Error: freenas-boot Failed to import"

FreeNasVolMgr.jpg

As you can see below photo these are the two usb sticks (new & old), but the 4x WD HDD are missing :(
FreeNasVolMgr2.jpg

and, below is the config file info uploaded from the old USB stick . Which is it was successfully imported from 'Storage>Import Volume'
FreeNasDisk2.jpg

Below photo is info about Storage>Volume>View Disks:
FreeNasDisk.jpg


I've use Freenas 9.3 stable version SAME AS BEFORE so that nothing to worry and avoid complication.
 
Last edited:

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
I could be completely wrong, but from the looks of things, I think everything looks like it is working and you aren't missing anything. But you might be confused on a couple of things.

You might know all this but I'll say it anyway (in no particular order), don't take offense if you know all this already.

1. You shouldn't be messing around in the Volume manager unless you are adding new pools etc. (It might be a good time to review the freenas docs in general).

2. You save your configuration file by going to:

SYSTEM >> GENERAL > Save Config Button within general

3. Your system has obviously booted and your pools that are there look healthy.

What is the output of zpool status -v ? either via putty/ssh or the gui shell (but I hate it)
What is the output of the zpool status -v freenas-boot? As that is the one that you said was giving trouble.

4. What is the output of /var/log/dmesg.today?

5. Did you reinstall the latest version of freenas onto a good usb disk and upload the configuration file you saved and then reboot as danb35 mentioned above?

6. if you want to add a mirror to the boot volume goto:
SYSTEM >> Boot > Status
There you can attach another usb disk or replace a bad one.
Don't re-use your usb disk that was throwing errors toss it.

7. You are saying the 4 wd disks that show up in view disks aren't the ones that you are looking for? There are additional disks that aren't there?

8. As a side note make sure you keep a list of serial numbers and what pools they are associated with.

Hop onto #freenas via https://webchat.freenode.net/ You'll get a more dynamic response.
 

ric

Contributor
Joined
Dec 22, 2013
Messages
180
"7. You are saying the 4 wd disks that show up in view disks aren't the ones that you are looking for? There are additional disks that aren't there?"

Yes, it's the right HDDs when you View Disks, but they should also be listed or be viewed these HDDs under Volume Manger, correct? and those HDDs are configured as RAIDz and I've created a directory/dataset within these drives as /mnt/tank/mymedia which is not showing up under Storage>Volumes anymore. In that directory (/mnt/tank/mymedia) where all my data or my Media files ( movies, music, home videos, pictures, etc) are stored here.
 
Last edited:

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
If you review the output of /var/log/dmesg.today you should be able to see if freenas/freebsd actually sees them during boot up.

@ command prompt: cat /var/log/dmesg.today | less

You can dump into here via insert code I believe.

This is where knowing the serial numbers comes into play. You can see which ones it is seeing.
 

ric

Contributor
Joined
Dec 22, 2013
Messages
180
I found out this problem when adding a Library on PlexMedia web interface when I tried to Browse For Media Folder, and by selecting the root /, and then /mnt (folder) nothing came up as it's appeared to be an empty folder now. There should be some subfolders like my media folders under /mnt directory that usually attached to this Dir and once I added that folder and click Add all the media files will start populating right away.

Here's the files output for /var/log/dmesg.today | less

Code:
[root@freenas] ~# cat /var/log/dmesg.today | less
Copyright (c) 1992-2014 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 9.3-RELEASE-p25 #0 r281084+d3a5bf7: Wed Sep  2 15:00:10 PDT 2015
    root@build3.ixsystems.com:/tank/home/jkh/build/FN/objs/os-base/amd64/tank/home/jkh/build/FN/FreeBSD/src/sys/FREENAS.amd64 amd64
gcc version 4.2.1 20070831 patched [FreeBSD]
CPU: Intel(R) Xeon(R) CPU E3-1230 v3 @ 3.30GHz (3292.45-MHz K8-class CPU)
  Origin = "GenuineIntel"  Id = 0x306c3  Family = 0x6  Model = 0x3c  Stepping = 3
  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>
  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>
  AMD Features=0x2c100800<SYSCALL,NX,Page1GB,RDTSCP,LM>
  AMD Features2=0x21<LAHF,ABM>
  Standard Extended Features=0x2fbb<GSFSBASE,TSCADJ,SMEP,ENHMOVSB,INVPCID>
  TSC: P-state invariant, performance statistics
real memory  = 2105856000 (2008 MB)
avail memory = 1997590528 (1905 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <SUPERM SMCI--MB>
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
FreeBSD/SMP: 1 package(s) x 1 core(s) x 2 SMT threads
cpu0 (BSP): APIC ID:  0
cpu1 (AP): APIC ID:  1
WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
ACPI Warning: FADT (revision 5) is longer than ACPI 5.0 version, truncating length 268 to 256 (20111123/tbfadt-325)
ioapic0 <Version 2.0> irqs 0-23 on motherboard
ispfw: registered firmware <isp_1040>
ispfw: registered firmware <isp_1040_it>
ispfw: registered firmware <isp_1080>
ispfw: registered firmware <isp_1080_it>
ispfw: registered firmware <isp_12160>
ispfw: registered firmware <isp_12160_it>
ispfw: registered firmware <isp_2100>
ispfw: registered firmware <isp_2200>
ispfw: registered firmware <isp_2300>
ispfw: registered firmware <isp_2322>
ispfw: registered firmware <isp_2400>
ispfw: registered firmware <isp_2400_multi>
ispfw: registered firmware <isp_2500>
ispfw: registered firmware <isp_2500_multi>
kbd1 at kbdmux0
cryptosoft0: <software crypto> on motherboard
aesni0: <AES-CBC,AES-XTS> on motherboard
padlock0: No ACE support.
acpi0: <SUPERM SMCI--MB> on motherboard
acpi0: Power Button (fixed)
acpi0: reservation of 67, 1 (4) failed
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed00000-0xfed003ff on acpi0
Timecounter "HPET" frequency 14318180 Hz quality 950
Event timer "HPET" frequency 14318180 Hz quality 550
Event timer "HPET1" frequency 14318180 Hz quality 440
Event timer "HPET2" frequency 14318180 Hz quality 440
Event timer "HPET3" frequency 14318180 Hz quality 440
Event timer "HPET4" frequency 14318180 Hz quality 440
Event timer "HPET5" frequency 14318180 Hz quality 440
Event timer "HPET6" frequency 14318180 Hz quality 440
atrtc0: <AT realtime clock> port 0x70-0x77 irq 8 on acpi0
atrtc0: Warning: Couldn't map I/O.
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
Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x1808-0x180b on acpi0
pcib0: <ACPI Host-PCI bridge> port 0xcf8-0xcff on acpi0
pci0: <ACPI PCI bus> on pcib0
pci0: <serial bus, USB> at device 20.0 (no driver attached)
ehci0: <EHCI (generic) USB 2.0 controller> mem 0xf7313000-0xf73133ff irq 16 at device 26.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
pcib1: <ACPI PCI-PCI bridge> irq 16 at device 28.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> at device 0.0 on pci1
pci2: <ACPI PCI bus> on pcib2
vgapci0: <VGA-compatible display> port 0xe000-0xe07f mem 0xf6000000-0xf6ffffff,0xf7000000-0xf701ffff irq 16 at device 0.0 on pci2
vgapci0: Boot video device
pcib3: <ACPI PCI-PCI bridge> irq 18 at device 28.2 on pci0
pci3: <ACPI PCI bus> on pcib3
igb0: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xd000-0xd01f mem 0xf7200000-0xf727ffff,0xf7280000-0xf7283fff irq 18 at device 0.0 on pci3
igb0: Using MSIX interrupts with 3 vectors
igb0: Ethernet address: 0c:c4:7a:00:c5:36
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
pcib4: <ACPI PCI-PCI bridge> irq 19 at device 28.3 on pci0
pci4: <ACPI PCI bus> on pcib4
igb1: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0xc000-0xc01f mem 0xf7100000-0xf717ffff,0xf7180000-0xf7183fff irq 19 at device 0.0 on pci4
igb1: Using MSIX interrupts with 3 vectors
igb1: Ethernet address: 0c:c4:7a:00:c5:37
igb1: Bound queue 0 to cpu 0
igb1: Bound queue 1 to cpu 1
ehci1: <EHCI (generic) USB 2.0 controller> mem 0xf7312000-0xf73123ff irq 23 at device 29.0 on pci0
usbus1: EHCI version 1.0
usbus1 on ehci1
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel Lynx Point SATA300 controller> port 0xf0b0-0xf0b7,0xf0a0-0xf0a3,0xf090-0xf097,0xf080-0xf083,0xf070-0xf07f,0xf060-0xf06f irq 19 at device 31.2 on pci0
ata2: <ATA channel> at channel 0 on atapci0
ata3: <ATA channel> at channel 1 on atapci0
atapci1: <Intel Lynx Point SATA300 controller> port 0xf050-0xf057,0xf040-0xf043,0xf030-0xf037,0xf020-0xf023,0xf010-0xf01f,0xf000-0xf00f irq 19 at device 31.5 on pci0
ata4: <ATA channel> at channel 0 on atapci1
ata5: <ATA channel> at channel 1 on atapci1
acpi_button0: <Power Button> on acpi0
acpi_tz0: <Thermal Zone> on acpi0
acpi_tz1: <Thermal Zone> on acpi0
uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
uart2: <16550 or compatible> port 0x3e8-0x3ef irq 7 on acpi0
orm0: <ISA Option ROMs> at iomem 0xc0000-0xc7fff,0xc8000-0xc8fff on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: CGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0
wbwd0: DevID 0xc3 DevRev 0x33, will not attach, please report this.
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
est0: <Enhanced SpeedStep Frequency Control> on cpu0
coretemp1: <CPU On-Die Thermal Sensors> on cpu1
est1: <Enhanced SpeedStep Frequency Control> on cpu1
ZFS NOTICE: Prefetch is disabled by default if less than 4GB of RAM is present;
            to enable, add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
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, logging disabled
usbus0: 480Mbps High Speed USB v2.0
usbus1: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
ugen1.1: <Intel> at usbus1
uhub1: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus1
uhub0: 2 ports with 2 removable, self powered
uhub1: 2 ports with 2 removable, self powered
ugen0.2: <vendor 0x8087> at usbus0
uhub2: <vendor 0x8087 product 0x8008, class 9/0, rev 2.00/0.05, addr 2> on usbus0
ugen1.2: <vendor 0x8087> at usbus1
uhub3: <vendor 0x8087 product 0x8000, class 9/0, rev 2.00/0.05, addr 2> on usbus1
uhub2: 6 ports with 6 removable, self powered
uhub3: 8 ports with 8 removable, self powered
ugen0.3: <vendor 0x0000> at usbus0
uhub4: <vendor 0x0000 product 0x0001, class 9/0, rev 2.00/0.00, addr 3> on usbus0
uhub4: 4 ports with 3 removable, self powered
ugen1.3: <vendor 0x0409> at usbus1
uhub5: <vendor 0x0409 product 0x005a, class 9/0, rev 2.00/1.00, addr 3> on usbus1
ugen0.4: <vendor 0x0557> at usbus0
ukbd0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
kbd0 at ukbd0
ums0: <vendor 0x0557 product 0x2419, class 0/0, rev 1.10/1.00, addr 4> on usbus0
ums0: 3 buttons and [Z] coordinates ID=0
uhub5: 4 ports with 4 removable, self powered
ugen1.4: <Logitech> at usbus1
ukbd1: <USB Keyboard> on usbus1
kbd2 at ukbd1
uhid0: <USB Keyboard> on usbus1
ugen1.5: <Logitech> at usbus1
ums1: <Logitech USB-PS2 Optical Mouse, class 0/0, rev 2.00/19.00, addr 5> on usbus1
ums1: 4 buttons and [XYZ] coordinates ID=0
ugen1.6: <Corsair> at usbus1
umass0: <Corsair Voyager Mini 3.0, class 0/0, rev 2.10/1.10, addr 6> on usbus1
umass0:  SCSI over Bulk-Only; quirks = 0x8100
umass0:5:0:-1: Attached to scbus5
ada0 at ata2 bus 0 scbus0 target 0 lun 0
da0 at umass-sim0 bus 0 scbus5 target 0 lun 0
da0: <Corsair Voyager Mini 3.0 000D> Removable Direct Access SCSI-6 device
da0: Serial Number 07084495F31B9794
da0: 40.000MB/s transfers
da0: 14786MB (30283008 512 byte sectors: 255H 63S/T 1885C)
da0: quirks=0x2<NO_6_BYTE>
ada0: <Samsung SSD 840 PRO Series DXM05B0Q> ATA-9 SATA 3.x device
ada0: Serial Number S1ANNEAD510589X
ada0: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada0: 122104MB (250069680 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
ada1 at ata2 bus 0 scbus0 target 1 lun 0
ada1: <WDC WD30EFRX-68EUZN0 80.00A80> ATA-9 SATA 3.x device
ada1: Serial Number WD-WMC4N0333692
ada1: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada1: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada1: quirks=0x1<4K>
ada1: Previously was known as ad5
ada2 at ata3 bus 0 scbus1 target 0 lun 0
ada2: <WDC WD30EFRX-68EUZN0 80.00A80> ATA-9 SATA 3.x device
ada2: Serial Number WD-WMC4N0335365
ada2: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada2: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada2: quirks=0x1<4K>
ada2: Previously was known as ad6
ada3 at ata3 bus 0 scbus1 target 1 lun 0
ada3: <INTEL SSDSC2CW480A3 400i> ATA-9 SATA 3.x device
ada3: Serial Number CVCV252207JX480DGN
ada3: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada3: 366290MB (750162470 512 byte sectors: 16H 63S/T 16383C)
ada3: Previously was known as ad7
ada4 at ata4 bus 0 scbus2 target 0 lun 0
ada4: <WDC WD30EFRX-68EUZN0 80.00A80> ATA-9 SATA 3.x device
ada4: Serial Number WD-WCC4N0377785
ada4: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada4: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada4: quirks=0x1<4K>
ada4: Previously was known as ad8
ada5 at ata5 bus 0 scbus3 target 0 lun 0
ada5: <WDC WD30EFRX-68EUZN0 80.00A80> ATA-9 SATA 3.x device
ada5: Serial Number WD-WMC4N0337155
ada5: 600.000MB/s transfers (SATA 3.x, UDMA5, PIO 8192bytes)
ada5: 2861588MB (5860533168 512 byte sectors: 16H 63S/T 16383C)
ada5: quirks=0x1<4K>
ada5: Previously was known as ad10
SMP: AP CPU #1 Launched!
Timecounter "TSC-low" frequency 1646222581 Hz quality 1000
Trying to mount root from zfs:freenas-boot/ROOT/default []...
GEOM_RAID5: Module loaded, version 1.3.20140711.62 (rev f91e28e40bf7)
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. 1.42, version 2.0
ipmi0: Number of channels 2
ipmi0: Attached watchdog
ipmi1: <IPMI System Interface> on isa0
device_attach: ipmi1 attach returned 16
wbwd0: DevID 0xc3 DevRev 0x33, will not attach, please report this.
wbwd0: HEFRAS and EFER do not align: EFER 0x4e DevID 0x00 DevRev 0x00 CR26 0x00
GEOM_ELI: Device ada2p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: hardware
GEOM_ELI: Device ada1p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: hardware
GEOM_ELI: Device ada4p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: hardware
GEOM_ELI: Device ada5p1.eli created.
GEOM_ELI: Encryption: AES-XTS 256
GEOM_ELI:     Crypto: hardware
vboxdrv: fAsync=0 offMin=0x19b offMax=0xba9
bridge0: Ethernet address: 02:d5:c3:86:a0:00
bridge0: link state changed to UP
igb0: promiscuous mode enabled
epair0a: Ethernet address: 02:f5:1b:00:08:0a
epair0b: Ethernet address: 02:f5:1b:00:09:0b
epair0a: link state changed to UP
epair0b: link state changed to UP
igb0: link state changed to DOWN
epair0a: promiscuous mode enabled
ng_ether_ifnet_arrival_event: can't re-name node epair0b
igb0: link state changed to UP
pid 1887 (syslog-ng), uid 0: exited on signal 6 (core dumped)
arp: 192.168.1.133 moved from 02:f5:1b:00:08:0a to 0c:c4:7a:00:c5:36 on epair0b
(END)
 
Last edited:

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
At 1st glance... am I reading right that system has 2GB of memory? If so people are going to jump all over that and tell you to bump it at least to 4, but probably something like 8GB. (but that might not be *the* problem here)

There is an odd set of lines:
ada0: Previously was known as ad4
ada1: Previously was known as ad5
ada2: Previously was known as ad6
ada3: Previously was known as ad7
ada4: Previously was known as ad8
ada5: Previously was known as ad10



What is the hardware that you are running?

Did you change *anything* with the system that might have caused this? bios related? hardware?
You have obviously been using this for a while, how long? Did you recently update the system?

You should go onto the irc channel and ask guys to look at this thread. I think you need more eyes on it.
 

ric

Contributor
Joined
Dec 22, 2013
Messages
180
Freenas 9.3 stable ver.
WD 4x NAS red hdd
Intel Xeon E3-1230 v3 LGA1150 CPU
Supermicro X10SLF-H Server Board

I think I did make a changes on the BIOS settings for 'Hard Disk Drive BBS Priorities' that was it, and Boot Seq. priority on the two USB sticks.

It's has been running flawlessly for more than 2 yrs. No update on the system yet.

irc channel? Please provide me the link.


Thanks.
 

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
You need to post the output of the following, like to did for the dmesg.

zfs list -r
zpool status -v

These should help people understand what is going on.

Also you should have a list of all the serial numbers / disk models and what the corresponding SATA ports they are plugged into.
 

dcevansiii

Dabbler
Joined
Sep 9, 2013
Messages
22
I think I did make a changes on the BIOS settings for 'Hard Disk Drive BBS Priorities' that was it, and Boot Seq. priority on the two USB sticks.

But you made these changes long ago right? Nothing recently that would have influenced things?

So how many physical disks do you actually have connected to your system? Just those 4 wd's?
 
Status
Not open for further replies.
Top