Disks failed to attach when auto importing and decrypting ZFS disks

Status
Not open for further replies.

Dainis Berzins

Dabbler
Joined
Aug 29, 2014
Messages
29
I was running FreeNAS 9.1 and started getting smartd errors occasionally on a disk that was one of three Western Digital Green 2TB disks in a ZFS volume, but FreeNAS ran well for several months. Then, after a reboot, FreeNAS failed to start. The boot failed early on with a disk-related message, ("Primary GEOM is corrupted" or something similar). My assumption was that the disk had failed and for some reason FreeNAS had not been able to handle the disk failure.

I installed FreeNAS-9.2.1.6-RELEASE-x86 on the same USB drive and can now boot and log in. I then tried to auto import the ZFS volume that I had on the 3 disks, selecting the 3 disks, browsing to the recovery key and entering the passphrase. When I click OK I get an error message saying:

Code:
The following disks failed to attach: gptid/582e2578-11bb-11e3-a71d-0018f32de2e9, gptid/57920bea-11bb-11e3-a71d-0018f32de2e9, gptid/56d22023-11bb-11e3-a71d-0018f32de2e9


I tried removing the suspect disk and attempting to auto-import, but I get the same message, although referring to only 2 disks, of course.

I had removed the disks, so I can't be certain that I have connected the drives to the same ports on the motherboard, in case that could be relevant.

My hardware:
  • HP dc7800 small form factor motherboard.
  • Intel Core 2 Duo
  • 2 GB RAM (yes, I know it would be good to have more, but it worked well for several months)
Any suggestions for how I can manage to install the old ZFS volume?

I attach the full console output from reboot to after the attempt to auto import:

Code:
Aug 29 12:07:55 freenas newsyslog[1794]: logfile first created
Aug 29 12:07:55 freenas syslogd: kernel boot file is /boot/kernel/kernel
Aug 29 12:07:55 freenas kernel: Waiting (max 60 seconds) for system process `vnlru' to stop...done
Aug 29 12:07:55 freenas kernel: Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
Aug 29 12:07:55 freenas kernel:
Aug 29 12:07:55 freenas kernel: Waiting (max 60 seconds) for system process `syncer' to stop...Syncing disks, vnodes remaining...0 0 done
Aug 29 12:07:55 freenas kernel: All buffers synced.
Aug 29 12:07:55 freenas kernel: Copyright (c) 1992-2013 The FreeBSD Project.
Aug 29 12:07:55 freenas kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Aug 29 12:07:55 freenas kernel: The Regents of the University of California. All rights reserved.
Aug 29 12:07:55 freenas kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Aug 29 12:07:55 freenas kernel: FreeBSD 9.2-RELEASE-p9 #0 r262572+cc525fe: Thu Jul  3 16:13:16 PDT 2014
Aug 29 12:07:55 freenas kernel: root@build3.ixsystems.com:/fusion/jenkins/9.2.1.6-RELEASE/os-base/i386/i386.i386/fusion/jenkins/9.2.1.6-RELEASE/FreeBSD/src/sys/FREENAS.i386 i386
Aug 29 12:07:55 freenas kernel: gcc version 4.2.1 20070831 patched [FreeBSD]
Aug 29 12:07:55 freenas kernel: CPU: Intel(R) Core(TM)2 Duo CPU  E8400  @ 3.00GHz (2992.56-MHz 686-class CPU)
Aug 29 12:07:55 freenas kernel: Origin = "GenuineIntel"  Id = 0x1067a  Family = 0x6  Model = 0x17  Stepping = 10
Aug 29 12:07:55 freenas kernel: Features=0xbfebfbff
Aug 29 12:07:55 freenas kernel: Features2=0x408e3fd
Aug 29 12:07:55 freenas kernel: AMD Features=0x20100000
Aug 29 12:07:55 freenas kernel: AMD Features2=0x1
Aug 29 12:07:55 freenas kernel: TSC: P-state invariant, performance statistics
Aug 29 12:07:55 freenas kernel: real memory  = 2151677952 (2052 MB)
Aug 29 12:07:55 freenas kernel: avail memory = 2036047872 (1941 MB)
Aug 29 12:07:55 freenas kernel: Event timer "LAPIC" quality 400
Aug 29 12:07:55 freenas kernel: ACPI APIC Table:
Aug 29 12:07:55 freenas kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Aug 29 12:07:55 freenas kernel: FreeBSD/SMP: 1 package(s) x 2 core(s)
Aug 29 12:07:55 freenas kernel: cpu0 (BSP): APIC ID:  0
Aug 29 12:07:55 freenas kernel: cpu1 (AP): APIC ID:  1
Aug 29 12:07:55 freenas kernel: WARNING: VIMAGE (virtualized network stack) is a highly experimental feature.
Aug 29 12:07:55 freenas kernel: ioapic0: Changing APIC ID to 1
Aug 29 12:07:55 freenas kernel: ioapic0 irqs 0-23 on motherboard
Aug 29 12:07:55 freenas kernel: kbd1 at kbdmux0
Aug 29 12:07:55 freenas kernel: cryptosoft0: on motherboard
Aug 29 12:07:55 freenas kernel: padlock0: No ACE support.
Aug 29 12:07:55 freenas kernel: acpi0: on motherboard
Aug 29 12:07:55 freenas kernel: acpi0: Power Button (fixed)
Aug 29 12:07:55 freenas kernel: acpi0: reservation of 0, a0000 (3) failed
Aug 29 12:07:55 freenas kernel: acpi0: reservation of 100000, 7df00000 (3) failed
Aug 29 12:07:55 freenas kernel: cpu0: on acpi0
Aug 29 12:07:55 freenas kernel: cpu1: on acpi0
Aug 29 12:07:55 freenas kernel: attimer0: port 0x40-0x43 irq 0 on acpi0
Aug 29 12:07:55 freenas kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Aug 29 12:07:55 freenas kernel: Event timer "i8254" frequency 1193182 Hz quality 100
Aug 29 12:07:55 freenas kernel: atrtc0: port 0x70-0x71 irq 8 on acpi0
Aug 29 12:07:55 freenas kernel: Event timer "RTC" frequency 32768 Hz quality 0
Aug 29 12:07:55 freenas kernel: hpet1: iomem 0xfed00000-0xfed003ff on acpi0
Aug 29 12:07:55 freenas kernel: Event timer "HPET" frequency 14318180 Hz quality 450
Aug 29 12:07:55 freenas kernel: Event timer "HPET1" frequency 14318180 Hz quality 440
Aug 29 12:07:55 freenas kernel: Event timer "HPET2" frequency 14318180 Hz quality 440
Aug 29 12:07:55 freenas kernel: Event timer "HPET3" frequency 14318180 Hz quality 440
Aug 29 12:07:55 freenas kernel: hpet0: iomem 0xfed00000-0xfed003ff on acpi0
Aug 29 12:07:55 freenas kernel: device_attach: hpet0 attach returned 12
Aug 29 12:07:55 freenas kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 900
Aug 29 12:07:55 freenas kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0xf808-0xf80b on acpi0
Aug 29 12:07:55 freenas kernel: pcib0: port 0xcf8-0xcff on acpi0
Aug 29 12:07:55 freenas kernel: pci0: on pcib0
Aug 29 12:07:55 freenas kernel: vgapci0: port 0x1230-0x1237 mem 0xf0100000-0xf017ffff,0xe0000000-0xefffffff,0xf0000000-0xf00fffff irq 16 at device 2.0 on pci0
Aug 29 12:07:55 freenas kernel: agp0: on vgapci0
Aug 29 12:07:55 freenas kernel: agp0: aperture size is 256M, detected 6140k stolen memory
Aug 29 12:07:55 freenas kernel: pci0: at device 3.0 (no driver attached)
Aug 29 12:07:55 freenas kernel: atapci0: port 0x1238-0x123f,0x1270-0x1273,0x1240-0x1247,0x1274-0x1277,0x11e0-0x11ef irq 18 at device 3.2 on pci0
Aug 29 12:07:55 freenas kernel: ata2: at channel 0 on atapci0
Aug 29 12:07:55 freenas kernel: ata3: at channel 1 on atapci0
Aug 29 12:07:55 freenas kernel: pci0: at device 3.3 (no driver attached)
Aug 29 12:07:55 freenas kernel: em0: port 0x1100-0x111f mem 0xf0180000-0xf019ffff,0xf01a5000-0xf01a5fff irq 19 at device 25.0 on pci0
Aug 29 12:07:55 freenas kernel: em0: Using an MSI interrupt
Aug 29 12:07:55 freenas kernel: em0: Ethernet address: 00:22:64:15:88:cc
Aug 29 12:07:55 freenas kernel: uhci0: port 0x1120-0x113f irq 20 at device 26.0 on pci0
Aug 29 12:07:55 freenas kernel: usbus0 on uhci0
Aug 29 12:07:55 freenas kernel: uhci1: port 0x1140-0x115f irq 21 at device 26.1 on pci0
Aug 29 12:07:55 freenas kernel: usbus1 on uhci1
Aug 29 12:07:55 freenas kernel: uhci2: port 0x1160-0x117f irq 22 at device 26.2 on pci0
Aug 29 12:07:55 freenas kernel: usbus2 on uhci2
Aug 29 12:07:55 freenas kernel: ehci0: mem 0xf01a6000-0xf01a63ff irq 22 at device 26.7 on pci0
Aug 29 12:07:55 freenas kernel: usbus3: EHCI version 1.0
Aug 29 12:07:55 freenas kernel: usbus3 on ehci0
Aug 29 12:07:55 freenas kernel: pci0: at device 27.0 (no driver attached)
Aug 29 12:07:55 freenas kernel: pcib1: at device 28.0 on pci0
Aug 29 12:07:55 freenas kernel: pci32: on pcib1
Aug 29 12:07:55 freenas kernel: pcib2: irq 21 at device 28.1 on pci0
Aug 29 12:07:55 freenas kernel: pci48: on pcib2
Aug 29 12:07:55 freenas kernel: uhci3: port 0x1180-0x119f irq 20 at device 29.0 on pci0
Aug 29 12:07:55 freenas kernel: usbus4 on uhci3
Aug 29 12:07:55 freenas kernel: uhci4: port 0x11a0-0x11bf irq 21 at device 29.1 on pci0
Aug 29 12:07:55 freenas kernel: usbus5 on uhci4
Aug 29 12:07:55 freenas kernel: ehci1: mem 0xf01a6400-0xf01a67ff irq 20 at device 29.7 on pci0
Aug 29 12:07:55 freenas kernel: usbus6: EHCI version 1.0
Aug 29 12:07:55 freenas kernel: usbus6 on ehci1
Aug 29 12:07:55 freenas kernel: pcib3: at device 30.0 on pci0
Aug 29 12:07:55 freenas kernel: pci7: on pcib3
Aug 29 12:07:55 freenas kernel: isab0: at device 31.0 on pci0
Aug 29 12:07:55 freenas kernel: isa0: on isab0
Aug 29 12:07:55 freenas kernel: atapci1: port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x11f0-0x11ff,0x1200-0x120f irq 18 at device 31.2 on pci0
Aug 29 12:07:55 freenas kernel: ata0: at channel 0 on atapci1
Aug 29 12:07:55 freenas kernel: ata1: at channel 1 on atapci1
Aug 29 12:07:55 freenas kernel: atapci2: port 0x1260-0x1267,0x1280-0x1283,0x1268-0x126f,0x1284-0x1287,0x1210-0x121f,0x1220-0x122f irq 18 at device 31.5 on pci0
Aug 29 12:07:55 freenas kernel: ata4: at channel 0 on atapci2
Aug 29 12:07:55 freenas kernel: ata5: at channel 1 on atapci2
Aug 29 12:07:55 freenas kernel: acpi_button0: on acpi0
Aug 29 12:07:55 freenas kernel: atkbdc0: port 0x60,0x64 irq 1 on acpi0
Aug 29 12:07:55 freenas kernel: atkbd0: irq 1 on atkbdc0
Aug 29 12:07:55 freenas kernel: kbd0 at atkbd0
Aug 29 12:07:55 freenas kernel: atkbd0: [GIANT-LOCKED]
Aug 29 12:07:55 freenas kernel: uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
Aug 29 12:07:55 freenas kernel: fdc0: port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
Aug 29 12:07:55 freenas kernel: ichwd0 on isa0
Aug 29 12:07:55 freenas kernel: ichwd0: resuming after hardware watchdog timeout
Aug 29 12:07:55 freenas kernel: sc0: at flags 0x100 on isa0
Aug 29 12:07:55 freenas kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Aug 29 12:07:55 freenas kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Aug 29 12:07:55 freenas kernel: coretemp0: on cpu0
Aug 29 12:07:55 freenas kernel: est0: on cpu0
Aug 29 12:07:55 freenas kernel: p4tcc0: on cpu0
Aug 29 12:07:55 freenas kernel: coretemp1: on cpu1
Aug 29 12:07:55 freenas kernel: est1: on cpu1
Aug 29 12:07:55 freenas kernel: p4tcc1: on cpu1
Aug 29 12:07:55 freenas kernel: Timecounters tick every 1.000 msec
Aug 29 12:07:55 freenas kernel: ipfw2 (+ipv6) initialized, divert enabled, nat enabled, default to accept, logging disabled
Aug 29 12:07:55 freenas kernel: DUMMYNET 0xc5d7ad60 with IPv6 initialized (100409)
Aug 29 12:07:55 freenas kernel: load_dn_sched dn_sched FIFO loaded
Aug 29 12:07:55 freenas kernel: load_dn_sched dn_sched PRIO loaded
Aug 29 12:07:55 freenas kernel: load_dn_sched dn_sched QFQ loaded
Aug 29 12:07:55 freenas kernel: load_dn_sched dn_sched RR loaded
Aug 29 12:07:55 freenas kernel: load_dn_sched dn_sched WF2Q+ loaded
Aug 29 12:07:55 freenas kernel: usbus0: 12Mbps Full Speed USB v1.0
Aug 29 12:07:55 freenas kernel: usbus1: 12Mbps Full Speed USB v1.0
Aug 29 12:07:55 freenas kernel: usbus2: 12Mbps Full Speed USB v1.0
Aug 29 12:07:55 freenas kernel: usbus3: 480Mbps High Speed USB v2.0
Aug 29 12:07:55 freenas kernel: usbus4: 12Mbps Full Speed USB v1.0
Aug 29 12:07:55 freenas kernel: usbus5: 12Mbps Full Speed USB v1.0
Aug 29 12:07:55 freenas kernel: usbus6: 480Mbps High Speed USB v2.0
Aug 29 12:07:55 freenas kernel: ugen0.1: at usbus0
Aug 29 12:07:55 freenas kernel: uhub0: on usbus0
Aug 29 12:07:55 freenas kernel: ugen1.1: at usbus1
Aug 29 12:07:55 freenas kernel: uhub1: on usbus1
Aug 29 12:07:55 freenas kernel: ugen2.1: at usbus2
Aug 29 12:07:55 freenas kernel: uhub2: on usbus2
Aug 29 12:07:55 freenas kernel: ugen3.1: at usbus3
Aug 29 12:07:55 freenas kernel: uhub3: on usbus3
Aug 29 12:07:55 freenas kernel: ugen4.1: at usbus4
Aug 29 12:07:55 freenas kernel: uhub4: on usbus4
Aug 29 12:07:55 freenas kernel: ugen5.1: at usbus5
Aug 29 12:07:55 freenas kernel: uhub5: on usbus5
Aug 29 12:07:55 freenas kernel: ugen6.1: at usbus6
Aug 29 12:07:55 freenas kernel: uhub6: on usbus6
Aug 29 12:07:55 freenas kernel: uhub0: 2 ports with 2 removable, self powered
Aug 29 12:07:55 freenas kernel: uhub1: 2 ports with 2 removable, self powered
Aug 29 12:07:55 freenas kernel: uhub2: 2 ports with 2 removable, self powered
Aug 29 12:07:55 freenas kernel: uhub4: 2 ports with 2 removable, self powered
Aug 29 12:07:55 freenas kernel: uhub5: 2 ports with 2 removable, self powered
Aug 29 12:07:55 freenas kernel: uhub6: 4 ports with 4 removable, self powered
Aug 29 12:07:55 freenas kernel: uhub3: 6 ports with 6 removable, self powered
Aug 29 12:07:55 freenas kernel: ugen3.2: at usbus3
Aug 29 12:07:55 freenas kernel: umass0: on usbus3
Aug 29 12:07:55 freenas kernel: umass0:  SCSI over Bulk-Only; quirks = 0x4000
Aug 29 12:07:55 freenas kernel: umass0:7:0:-1: Attached to scbus7
Aug 29 12:07:55 freenas kernel: ada0 at ata0 bus 0 scbus2 target 0 lun 0
Aug 29 12:07:55 freenas kernel: ada0: ATA-8 SATA 2.x device
Aug 29 12:07:55 freenas kernel: ada0: Serial Number WD-WMAZA5123535
Aug 29 12:07:55 freenas kernel: ada0: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Aug 29 12:07:55 freenas kernel: ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Aug 29 12:07:55 freenas kernel: ada0: quirks=0x1<4K>
Aug 29 12:07:55 freenas kernel: ada0: Previously was known as ad0
Aug 29 12:07:55 freenas kernel: ada1 at ata1 bus 0 scbus3 target 0 lun 0
Aug 29 12:07:55 freenas kernel: ada1: ATA-8 SATA 2.x device
Aug 29 12:07:55 freenas kernel: ada1: Serial Number WD-WCAZA2531993
Aug 29 12:07:55 freenas kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Aug 29 12:07:55 freenas kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Aug 29 12:07:55 freenas kernel: ada1: quirks=0x1<4K>
Aug 29 12:07:55 freenas kernel: ada1: Previously was known as ad2
Aug 29 12:07:55 freenas kernel: ada2 at ata4 bus 0 scbus4 target 0 lun 0
Aug 29 12:07:55 freenas kernel: ada2: ATA-8 SATA 2.x device
Aug 29 12:07:55 freenas kernel: ada2: Serial Number WD-WMAZA5169250
Aug 29 12:07:55 freenas kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA5, PIO 8192bytes)
Aug 29 12:07:55 freenas kernel: ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Aug 29 12:07:55 freenas kernel: ada2: quirks=0x1<4K>
Aug 29 12:07:55 freenas kernel: ada2: Previously was known as ad8
Aug 29 12:07:55 freenas kernel: da0 at umass-sim0 bus 0 scbus7 target 0 lun 0
Aug 29 12:07:55 freenas kernel: da0: < USB Flash Memory 5.00> Removable Direct Access SCSI-0 device
Aug 29 12:07:55 freenas kernel: da0: Serial Number 09A1747160505952
Aug 29 12:07:55 freenas kernel: da0: 40.000MB/s transfers
Aug 29 12:07:55 freenas kernel: da0: 1967MB (4028416 512 byte sectors: 255H 63S/T 250C)
Aug 29 12:07:55 freenas kernel: da0: quirks=0x2
Aug 29 12:07:55 freenas kernel: SMP: AP CPU #1 Launched!
Aug 29 12:07:55 freenas kernel: Timecounter "TSC-low" frequency 1496278998 Hz quality 1000
Aug 29 12:07:55 freenas kernel: Trying to mount root from ufs:/dev/ufs/FreeNASs1a [ro]...
Aug 29 12:07:55 freenas kernel: GEOM_RAID5: Module loaded, version 1.1.20130907.44 (rev 5c6d2a159411)
Aug 29 12:07:55 freenas kernel: GEOM_ELI: Device ada0p1.eli created.
Aug 29 12:07:55 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Aug 29 12:07:55 freenas kernel: GEOM_ELI:  Crypto: software
Aug 29 12:07:55 freenas kernel: GEOM_ELI: Device ada1p1.eli created.
Aug 29 12:07:55 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Aug 29 12:07:55 freenas kernel: GEOM_ELI:  Crypto: software
Aug 29 12:07:55 freenas kernel: GEOM_ELI: Device ada2p1.eli created.
Aug 29 12:07:55 freenas kernel: GEOM_ELI: Encryption: AES-XTS 256
Aug 29 12:07:55 freenas kernel: GEOM_ELI:  Crypto: software
Aug 29 12:07:55 freenas kernel: ZFS NOTICE: Prefetch is disabled by default on i386 -- to enable,
Aug 29 12:07:55 freenas kernel: add "vfs.zfs.prefetch_disable=0" to /boot/loader.conf.
Aug 29 12:07:55 freenas kernel: ZFS WARNING: Recommended minimum kmem_size is 512MB; expect unstable behavior.
Aug 29 12:07:55 freenas kernel: Consider tuning vm.kmem_size and vm.kmem_size_max
Aug 29 12:07:55 freenas kernel: in /boot/loader.conf.
Aug 29 12:07:55 freenas kernel: ZFS filesystem version: 5
Aug 29 12:07:55 freenas kernel: ZFS storage pool version: features support (5000)
Aug 29 12:07:55 freenas root: /etc/rc: WARNING: failed precmd routine for vmware_guestd
Aug 29 12:07:56 freenas kernel: vboxdrv: fAsync=0 offMin=0x45c offMax=0xdf5
Aug 29 12:07:56 freenas ntpd[1984]: ntpd 4.2.4p5-a (1)
Aug 29 12:07:56 freenas kernel: ..............................
Aug 29 12:07:56 freenas kernel: ............+++
Aug 29 12:07:57 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /sbin/sysctl -n 'kern.maxfilesperproc'
Aug 29 12:07:57 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/pdbedit -d 0 -i smbpasswd:/tmp/tmp6OPZRa -s /usr/local/etc/smb4.conf -e tdbsam:/var/etc/private/passdb.tdb
Aug 29 12:07:57 freenas generate_smb4_conf.py: [common.pipesubr:58] Popen()ing: /usr/local/bin/net groupmap add unixgroup='dainis' ntgroup='dainis'
Aug 29 12:07:57 freenas smartd[2243]: Configuration file /usr/local/etc/smartd.conf parsed but has no entries (like /dev/hda)
Aug 29 12:07:57 freenas root: /etc/rc: WARNING: failed to start smartd
Aug 29 12:08:05 freenas ntpd[1985]: time reset -0.805882 s
Aug 29 12:08:46 freenas manage.py: [middleware.notifier:1362] Failed to geli detach gptid/582e2578-11bb-11e3-a71d-0018f32de2e9: geli: No such device: gptid/582e2578-11bb-11e3-a71d-0018f32de2e9.
Aug 29 12:08:46 freenas manage.py: [middleware.notifier:1362] Failed to geli detach gptid/57920bea-11bb-11e3-a71d-0018f32de2e9: geli: No such device: gptid/57920bea-11bb-11e3-a71d-0018f32de2e9.
Aug 29 12:08:46 freenas manage.py: [middleware.notifier:1362] Failed to geli detach gptid/56d22023-11bb-11e3-a71d-0018f32de2e9: geli: No such device: gptid/56d22023-11bb-11e3-a71d-0018f32de2e9.
 

enemy85

Guru
Joined
Jun 10, 2011
Messages
757
"Stupid" idea: can you try first adding more ram if u have spare ram laying around?
 

Dainis Berzins

Dabbler
Joined
Aug 29, 2014
Messages
29
If I had, I would, but the system ran just fine with the 2 Gb for several months. I am sure the performance would be better, but I doubt the limited RAM is causing this specific issue.
 

enemy85

Guru
Joined
Jun 10, 2011
Messages
757
Was just a try if it was easy to apply. I don't have experience with encripted volumes, but i guess they are more "heavy" to handle by the system
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
If I had, I would, but the system ran just fine with the 2 Gb for several months. I am sure the performance would be better, but I doubt the limited RAM is causing this specific issue.

Sorry, that's a *really* bad reason to argue it will be okay. In fact, there's a distinct chance you've lost your data as a result of this argument.

They aren't significantly heavier to handle, but when you are short on RAM then processes terminate in appropriately and next thing you know disks won't decrypt, your zpools won't create properly, etc and we end up with oddball threads like this that nobody else has ever experienced and the error messages make it look like a hopeless situation.

So I'd upgrade to 8GB before you try to do *anything* else with your pool. Failure to do so could (and it looks like it has) cost you your data.

Of course, this is where I ask if you have backups and hope you answer with "yes"...
 

Dainis Berzins

Dabbler
Joined
Aug 29, 2014
Messages
29
Thanks for the reply. Clearly I will upgrade the RAM asap. And yes, I do have the critical data backed up, thankfully.

But is there any way to get more clarity as to why the decryption / attach failed?

Also if I have attached the drives to different SATA ports than when the encryption was performed, could that make a difference or should FreeNAS be able to deal with this?
 

enemy85

Guru
Joined
Jun 10, 2011
Messages
757
Freenas can handle different sata ports, that's not the problem.
 

Dainis Berzins

Dabbler
Joined
Aug 29, 2014
Messages
29
OK, good to know.

So can anyone suggest any commands I could run to try to learn more about what specifically is causing the decryption / attach to fail?
 

cyberjock

Inactive Account
Joined
Mar 25, 2012
Messages
19,526
If its failing to decrypt with your keys then the keystore on your disks are corrupted or overwritten. Who knows why that would be the case (low RAM comes to mind....) and proving the actual cause will be nearly impossible. However, since this hasn't been a problem with users like myself who *do* use the correct amount of RAM I tend to have a hypothesis...
 
Status
Not open for further replies.
Top