Nexenta Error 16
Contents |
bug affects 1 person Affects Status Importance Assigned to Milestone grub Edit Unknown Unknown savannah #17957 You need to log in to change this bug's status. Launchpad doesn't support importing bugs from Savane bug trackers. (what does error 16 inconsistent filesystem structure windows 7 this mean?) Affecting: grub Filed here by: Daniel Hahler When: 2007-03-16 Target Distribution Baltix how to fix error 16 inconsistent filesystem structure BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu boot error 16 inconsistent filesystem structure RTM Package (Find…) Project (Find…) Status Importance Unknown Unknown Assigned to unknown Remote Watch None, the status of the bug is updated manually. None, the status of the bug is updated manually. GNU Savannah Bug error 16 inconsistent filesystem structure redhat Tracker #17957 URL: The information about this bug in Launchpad is automatically pulled daily from the remote bug. This information was last pulled 21 hours ago. Comment on this change (optional) Email me about changes to this bug report grub (Ubuntu) Edit Won't Fix Low Unassigned Edit You need to log in to change this bug's status. Affecting: grub (Ubuntu) Filed here by: Daniel Hahler When: 2006-10-09 Completed: 2012-06-02
Error 16 Inconsistent Filesystem Structure Centos
Target Distribution Baltix BOSS Juju Charms Collection Elbuntu Guadalinex Guadalinex Edu Kiwi Linux nUbuntu PLD Linux Tilix tuXlab Ubuntu Ubuntu Linaro Evaluation Build Ubuntu RTM Package (Find…) Project (Find…) Status Importance Won't Fix Low Assigned to Nobody Me Comment on this change (optional) Email me about changes to this bug report Also affects project (?) Also affects distribution/package Nominate for series Bug Description While I was testing hibernation on my system, I sometimes got the error "GRUB Error 16: Inconsistent filesystem structure" when trying to boot the default kernel. I also got the same error during rebooting normally, after I've resumed from hibernation. This problem can be quite easily be fixed by using the "recovery" kernel provided in grub menu: the ReiserFS transaction logs then get replayed then. After having hibernated before, the system will even resume normally, but when it happens after a "normal" reboot, I get the recovery root prompt only (though "init 2" should work from there). Grub Error 16 is described as: """ 16 : Inconsistent filesystem structure This error is returned by the filesystem code to denote an internal error caused by the sanity checks of the filesystem structure on disk not matching what it expects. This is usually caused by a corrupt filesystem
— No Comments ↓ Oh no. I've managed to get this error before. And it was right after i
Error 16 Inconsistent Filesystem Structure Solaris
applied compression to the rpool zfs filesystem. Upon the next reboot i error 16 inconsistent filesystem structure vmware was greeted with this error message; Error 16 : Inconsistent filesystem structure For me it was a grub error 16 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 https://bugs.launchpad.net/bugs/64928 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 http://sigtar.com/2009/02/02/zfs-error-16-inconsistent-filesystem-structure/ 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 This entry was posted in Solaris Express and tagged opensolaris, zfs by Daz. Bookmark the permalink. Leave a Reply Cancel reply Your email address will not be published.Comment Name Email Primary Sidebar Widget Area 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 Copyright © 2016 Daz's bits and bobs. All Rights Reserved.Theme: Catch Box by Catch Themes Go to Header Section Plugins WordpressThemes Word
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more http://serverfault.com/questions/258506/booting-nexenta-root-mirror-results-in-grub-error-filesystem-type-unknown-part about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Booting Nexenta root mirror results in GRUB error “Filesystem type unknown, partition type 0xbf” error 16 up vote 4 down vote favorite 2 I have a Nexenta system that's been running fine for the last few years. Recently one of the system disks failed --- the syspool was part of a ZFS mirror. If I configure the system's BIOS to boot from the working drive, the text GRUB ("GRUB" followed by a space) appears on the screen, and the system doesn't respond. If I boot from a Nexenta installation CDROM and try to set error 16 inconsistent the root as follows: root (hd1,0,a) ...I get the following message from GRUB: Filesystem type unknown, partition type 0xbf However if I were to issue the above root command on a fresh Nexenta installation, I would see: Filesystem type zfs, partition type 0xbf How can I get GRUB to recognize the surviving root mirror disk, so I can boot from it? And, in the future, what procedure should I follow when a device in a root mirror fails, so that I can properly recover (and boot from any drive in the mirror pool)? zfs opensolaris grub nexenta share|improve this question edited Apr 12 '11 at 4:03 asked Apr 11 '11 at 22:47 smokris 3902825 Seems that dd:ing start of the disk (1GB), making new partition table, new label and creating new pool doesn't make the ZFS visible to grub. There must be some fishy bits somewhere on the end of the disk? –jkj May 17 '11 at 11:35 add a comment| 1 Answer 1 active oldest votes up vote 3 down vote This sounds a lot like a similar issue I experienced on my Nexenta installation. I had recently done a ZFS version upgrade across both the syspool and my other pools, but failed to re-install grub afterwards. The result was that the next power outage left grub unable to read the ZFS filesystem and the system was un