Error 16 Inconsistent Filesystem Structure Zfs
Contents |
filesystem. Upon the next reboot i was greeted with this error error 16 inconsistent filesystem structure windows 7 message; Error 16 : Inconsistent filesystem structure For me it
Boot Error 16 Inconsistent Filesystem Structure
was a show stopper and i had to go into recovery. So i've learnt my lesson - Not to touch the rpool zpool. I was lucky enough to have put my data within a zfs filesystem (rpool/virtual) i created within the default rpool zpool. I use this spot for my VirtualBox virtual machines. Recovery for my rpool/virtual zfs filesystem; Boot the live cd open terminal, type SU, enter default password as of 2008.11 "opensolaris" zpool import rpool - brings rpool and associated zfs filesystems back online type nautalis &, copy data from rpool/virtual to another drive (i mounted another disk by also importing another zpool - zpool import will list available zpools) zpool export rpool, then re-run the installation program. Note: you need to dismount rpool or the install will fail and stop. Worked for me, usual disclaimer though. Most Guys Want To Get Bigger Muscles, how to get bigger muscles Tags: opensolaris, zfs Leave a Reply Name Mail (will not be published) Website 001100 010010 011110 100001 101101 110011 Categories Apple Drone Home PC Linux Networking Solaris Express Storage Virtual Windows Tagsboot cifs cisco console dhcp disk dns driver esx esxi etherchannel express firewall hdd hp install iscsi Linux memory MPIO network nfs opensolaris performance proxy router samba script server share smb snapshots solaris squid ssh transparent ubuntu Virtual virtualbox vlan vmware vsphere Windows zfs zpool © 2007 Daz's bits and bobs - StudioPress Theme Full RSS - Comments RSS
times and finally decided to logit since I've spend 2 days configuring my "OpenSolaris 2008.11 snv_101b_rc2X86" and after installing the SUNWsmbfskr package I ended up in the grub> menu.The package contains a necessary module for CIFS. After pkg installSUNWsmbfskr, I rebooted the box. There was no grub menu anymore but only thegrub prompt. I managed to boot it manually using another BE. I was unable touse the original BE getting this error message during the manual boot:bootfs rpool/ROOT/rp01OKkernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFSOKmodule$ /platform/i86pc/$ISADIR/boot_archiveafter this command I got the error: Error 16: Inconsistent filesystemstructure.I had to use a different BE to boot up the system.I've http://sigtar.com/2009/02/02/zfs-error-16-inconsistent-filesystem-structure/ tried to repair boot_archive from the rp01 BE but unsuccessfully everytime ending up in the grub menu forced to manually boot the system using adifferent BE.My unsuccessful method to rebuild boot_archive:# mkdir /a# bootadm mount rp01 /a# rm /a/platform/i86pc/boot_archive# bootadm update-archive -f -R /aCreating boot_archive for /aupdating /a/platform/i86pc/amd64/boot_archiveupdating /a/platform/i86pc/boot_archive# beadm unmount rp01# reboot***@panda:~$ beadm listBE Active Mountpoint Space Policy Created-- ------ ---------- ----- ------ -------opensolaris - - 8.23M http://zfs-discuss.opensolaris.narkive.com/9xmOEzjh/error-16-inconsistent-filesystem-structure-after-a-change-in-the-system static 2008-12-16 21:04opensolaris-1 - - 121.78M static 2008-12-20 12:40opensolaris-2 - - 8.21M static 2008-12-21 01:57opensolaris-3 - - 67.31M static 2008-12-21 15:12opensolaris-4 - - 306.0K static 2008-12-21 20:46opensolaris-5 - - 165.07M static 2008-12-21 20:49rp01 - - 140.59M static 2008-12-22 21:38rp02 NR / 3.48G static 2008-12-23 00:06update - - 13.59M static 2008-12-20 12:25To reproduce the bug on my system is very simple just change/install/un-installanything in the kernel directory or try to create, activate a new BE using thebeadm command and you will end up in the grub prompt (no grub menu available).To rescue from this stage only a manual boot or an Osol2008.11 Live CD.Could you please provide me with a method to recover the rp01 BE. I've spend tomuch time configuring it and don't want to loose the changes. But the methodmust be different then the one I provided above as the above one doesn't work.Also trying to create a new BE from the rp01 BE doesn't work:***@panda:~$ pfexec su -Sun Microsystems Inc. SunOS 5.11 snv_101b November 2008You have new mail.***@panda:~# export BE_PRINT_ERR=true***@panda:~# beadm create -e rp01 rp03be_copy: failed to snapshot BE (rpool/ROOT/***@rp03): dataset is busyUnable to create rp03.Mount busy.***@panda:~#As you can see the rp01 BE suppose to be a non-active BE name
a change in the system From: Rafal Pratnicki Date: Sat, 03 Jan 2009 12:11:39 PST I recovered the system and created the opensolaris-12 BE. The system was http://www.archivum.info/zfs-discuss@opensolaris.org/2009-01/00738/Re-(zfs-discuss)-Error-16-Inconsistent-filesystem-structure-after-a-change-in-the-system.html working fine. I had the grub menu, it was fully recovered. At this stage I decided to create a new BE but leave the opensolaris-12 BE as an active BE and manually boot to the opensolaris-13 BE. So the situation looked like this: beadm list opensolaris-12 R / 3.73G static 2009-01-03 14:44 error 16 opensolaris-13 N - 120.74M static 2009-01-03 14:51 Running the opensolaris-13 BE I installed 2 packages: SUNWsmbs SUNWsmbskr responsible for the solaris CIFS service. I reboot the box and it still was fine. I had the grub menu and the boot_archive wasn't corrupted. After the reboot I configured the solaris CIFS service and exchanged error 16 inconsistent some data between the opensolaris and a laptop via a network. I've been doing this for 3h. Then I decided to reboot the box again to see if it's still OK. I used init 6, but this time I ended up in the grub> menu. When I manually wanted to boot it looked like this: bootfs rpool/ROOT/opensolaris-13 OK kernel$ /platform/i86pc/kernel/$ISADIR/unix -B $ZFS-BOOTFS Error 16: Inconsistent filesystem structure I had to use rpool/ROOT/opensolaris-12 and it was fine. I didn't even get to load the boot_archive module. Usually it breaks during the boot_archive module load. I'm unable to use the opensolaris-13 BE and I've lost the CIFS configuration as I can't boot the BE. Can someone wise help me to narrow down this bug. Thanks in advance Rafal -- This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list [emailprotected] http://mail.opensolaris.org/mailman/listinfo/zfs-discuss [Morewiththissubject...]