praecorloth
Contributor
- Joined
- Jun 2, 2011
- Messages
- 159
Hey guys.
I've got a FreeNAS box running 8.0.4 64bit. It's got a single ~1TB RAIDZ2. Basically the system kernel panic'd and would continue to kernel panic upon reboot. (Kernel panic details in a moment). The problem was that the FreeNAS install would go through and try to mount the borked volume. Fresh install of FreeNAS would boot properly, go to auto import, kernel panic.
We then did an import from the command line.
And that's where it ends. We've been playing with this a bit and can't figure anything out. We had found a blog by someone who was in a similar issue, and they listed out how they used zdb to fix the problem. Which we tried, though I can't find the page right now to tell you what was tried, but it didn't work anyways. We're pretty stuck here. Any thoughts? I'm attaching a pic of the screen when we got the kernel panic, just in case.
Here is the zdb command we tried.
That took some time to run, but we're still at the same point, unfortunately.
I've got a FreeNAS box running 8.0.4 64bit. It's got a single ~1TB RAIDZ2. Basically the system kernel panic'd and would continue to kernel panic upon reboot. (Kernel panic details in a moment). The problem was that the FreeNAS install would go through and try to mount the borked volume. Fresh install of FreeNAS would boot properly, go to auto import, kernel panic.
We then did an import from the command line.
Code:
# zpool import -f HubZ2 panic: solairs assert: ss == NULL, file: /build/home/jpaetzel/8.2.0/FreeBSD/src/sys/modules/zfs/../../cddl/contrib/opensolaris/ufs/common/fs/zfs/space_map.c, line:109 cpuid = 0 Uptime: 6m43s Physical memory: 4038 MB Dumping 278 MB:
And that's where it ends. We've been playing with this a bit and can't figure anything out. We had found a blog by someone who was in a similar issue, and they listed out how they used zdb to fix the problem. Which we tried, though I can't find the page right now to tell you what was tried, but it didn't work anyways. We're pretty stuck here. Any thoughts? I'm attaching a pic of the screen when we got the kernel panic, just in case.
Here is the zdb command we tried.
Code:
zdb -e -bcsvL HubZ2
That took some time to run, but we're still at the same point, unfortunately.