ad14 had disapeared as shown by the following in /var/log/messages: Dec 29 01:57:21 zfsserver kernel: ad14: FAILURE - device detached Dec 29 01:57:21 zfsserver kernel: subdisk14: detached Dec 29 01:57:21 zfsserver kernel: ad14: detached Dec 29 01:57:22 zfsserver root: ZFS: vdev failure, zpool=data type=vdev.open_failed I tried doing an atacontrol reinit ata7 to rediscover the drive, but that didn't find it, so I rebooted to bring it back. Then I ran a zpool scrub to check that the data was all happy. A couple minutes into it the kernel paniced. ad14 is connected to "Promise SATAII150 518 (tm) IDE Controller" Last few lines from /var/log/messages: Dec 29 02:24:08 zfsserver kernel: ad14: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Dec 29 02:24:12 zfsserver kernel: ad14: WARNING - SETFEATURES SET TRANSFER MODE taskqueue timeout - completing request directly Dec 29 02:24:16 zfsserver kernel: ad14: WARNING - SETFEATURES ENABLE RCACHE taskqueue timeout - completing request directly Dec 29 02:24:20 zfsserver kernel: ad14: WARNING - SETFEATURES ENABLE WCACHE taskqueue timeout - completing request directly Dec 29 02:24:24 zfsserver kernel: ad14: WARNING - SET_MULTI taskqueue timeout - completing request directly Dec 29 02:24:24 zfsserver kernel: ad14: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=482801523 Dec 29 02:24:24 zfsserver kernel: ad14: WARNING - READ_DMA48 UDMA ICRC error (retrying request) LBA=482801523 Dec 29 02:24:24 zfsserver root: ZFS: checksum mismatch, zpool=data path=/dev/ad14 offset=247190218240 size=32768 Dec 29 02:24:29 zfsserver kernel: ad14: TIMEOUT - READ_DMA48 retrying (1 retry left) LBA=482801651 # kgdb /boot/kernel/kernel.symbols /var/crash/vmcore.25 [GDB will not be able to debug user-mode threads: /usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"] GNU gdb 6.1.1 [FreeBSD] Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-marcel-freebsd". Unread portion of the kernel message buffer: ad14: FAILURE - device detached subdisk14: detached ad14: detached Fatal trap 12: page fault while in kernel mode cpuid = 0; apic id = 00 fault virtual address = 0x2c fault code = supervisor write, page not present instruction pointer = 0x20:0xc0632e75 stack pointer = 0x28:0xef33bc5c frame pointer = 0x28:0xef33bc70 code segment = base rx0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 3 (g_up) trap number = 12 panic: page fault cpuid = 0 KDB: stack backtrace: db_trace_self_wrapper(c0984eeb,ef33baf8,c063f33f,c09a366c,0,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c09a366c,0,c09649c3,ef33bb04,0,...) at kdb_backtrace+0x29 panic(c09649c3,c09a4913,c3f544d0,1,1,...) at panic+0x10f trap_fatal(c0a65020,0,2,8,dd313180,...) at trap_fatal+0x333 trap_pfault(c0a64ac8,ef33bb90,c066d3dd,ef33bbb4,c,...) at trap_pfault+0x250 trap(ef33bc1c) at trap+0x3c6 calltrap() at calltrap+0x6 --- trap 0xc, eip = 0xc0632e75, esp = 0xef33bc5c, ebp = 0xef33bc70 --- _mtx_lock_flags(1c,0,c0bf6e0d,1d8,c0bec2a0,...) at _mtx_lock_flags+0x15 vdev_geom_io_intr(c4e4f7bc,c0a17e04,0,0,0) at vdev_geom_io_intr+0x44 biodone(c4e4f7bc,c0a64a28,24c,c097d445,64,...) at biodone+0xad g_io_schedule_up(c3f0dc60,4c,c097e119,5b,0,...) at g_io_schedule_up+0x7f g_up_procbody(0,ef33bd38,0,ffffffff,ffffffff,...) at g_up_procbody+0x6c fork_exit(c05eea20,0,ef33bd38) at fork_exit+0x97 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xef33bd70, ebp = 0 --- Uptime: 8m0s Physical memory: 1011 MB Dumping 258 MB: 243 227 211 195 179 163 147 131 115 99 83 67 51 35 19 3 I'm not sure what else to report. Fix: unknown How-To-Repeat: I can't reproduce it. :-(
Responsible Changed From-To: freebsd-bugs->sos Hi Soren this might be something for you..
Responsible Changed From-To: sos->freebsd-bugs sos@ is not actively working on ATA-related PRs.
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped
Keyword: crash – in lieu of summary line prefix: [panic] * bulk change for the keyword * summary lines may be edited manually (not in bulk). Keyword descriptions and search interface: <https://bugs.freebsd.org/bugzilla/describekeywords.cgi>