SUSE / openSUSEThis Forum is for the discussion of Suse Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
When I boot my computer, all goes well until it attempts to load grub 1.5 when the error 16 msg comes up. If I try to reboot the same result. If I go away for 15-20 minutes I get a successful boot. I am running amd64 3500, 160g hard drive mounted in 'databridge' removable rack using suse 10.3. The history of the drive is that it was used as the master drive in conjunction with another racked hd to dual boot windows xp. It all fell over when I tried vmware to boot windows from within linux. I have dispensed with the windows disk and the suse disk is now stand alone (re-installed)
I really do not want to guess what the problem is if you can shut it down and restart and it will boot. The first thing I would try would be to use your Suse disk and do a repair or recovery. I would think this should get you fixed up.
Grub Error 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 or bugs in the code handling it in GRUB.
Setting up vmware may have changed something in the filesystem structure that was necessary fro vmware vitrualization, but is significantly different from a stand-alone system.
You could try booting a liveCD and running fsck on your partitions. Beyond that, if you have a backup that pre-dates the vmware installation, you could restore that to see if you can return the system to a sane state.
Thanks for the suggestions. When I attempted to do a repair from the suse disk, I ended up with a red screen that said 'failed to load'.
When I had vmware loaded on the disk, the OS was ubuntu. After various attempts to resurrect the disk, I retrieved the information via a live install disk, and then loaded suse. In this process, I deleted all partitions and had suse re-partition the disk in the install process. As a result I do not have a backup copy of the disk prior to running vmware. What still puzzles me is that the disk loads after some period of 'warm up'
Turned out to be a hardware problem - nothing to do with the OS or the HDD, but the cable between the motherboard and the harddisk had developed a problem. Replaced the cable and now live happily ever after!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.