Ubuntu Installation :: Inconsistent Filesystem Structure After Kernel Upgrade
Nov 20, 2010
I can't boot the 2.6.35-22 kernel, since I get the "Error 16: Inconsistent filesystem structure" every time. However, the previous kernel I have installed, 2.6.32-25, is booting without a problem, so I'm forced to use that until this problem is solved. What can I do?
I have two computers, a HP DX2250 with dual SATA drives and a HP D530 with 1 EIDE drive and 1 SATA drive. On each computer Windows XP Pro is installed on the first drive and Fedora is installed on the second drive. I have had no problems installing and running Fedora 15 on the the DX2250.
My persistent problem lies with the D530. I have installed Fedora 15 on the SATA drive several times. I used the Fedora live cd and I have used PreUpgrade. Every install results in the Error 16: message occurring during boot and ending with a Grub prompt. I have even unplugged the EIDE drive during Fedora boot and still get the problem. I might also add: the machine hard drive boot is controlled via F10 and changing the drive controller order. I have installed and used Fedora on both machines from Fedora 11 thru Fedora 14 with no problems. This error is new with Fedora 15. My next attempt is to install Fedora 15 on the SATA drive with the EIDE drive unplugged. All ideas or SWAG guesses are welcome.
Error 16: Inconsistent filesystem structure I was making my first system update yesterday, and had to restart after 6 hours of downloading, while the indication bar was about 60%.
Today, I was booting into Centos 5.1 and GRUB gave me this screen: root (hd0.0) Filesystem type is ext2fs, partition type is 0x83 kernel /vmlinuz-2.6 18-53.e15 ro root=/dev/VolGroup00/LogVol00 rhgb quite crash kernel=128M@16M
I installed Ubuntu two ways, both by partitioning the hard drive and installing Ubuntu in its own partition, and also where the "run within Windows" option was available. I then upgraded both to Ubuntu 11.04. When I start Ubuntu in the "own partition" installation, Unity runs without complaint. When I start Ubuntu in the "run within Windows" installation, Unity baulks, giving an error message that I don't have some (unspecified) of the hardware it needs to run, and I am kicked back to the classic Ubuntu control screen setup. Obviously the two ways to install Ubuntu don't result in it having the same behavior. Alternately, since the version installed to "run within Windows" seems to do no such thing, and also gobbled up almost all the free space in my Windows-7 partition without prior warning, any clue how to uninstall that version cleanly?
So, after the upgrade to 10.10, my bluetooth devices keep cutting in and out, and my Jabra bt125 won't connect to this computer. The Jabra won't even show up on btscanner or bluewho, but it will connect to my phone. The phone connects, but quickly disconnects. When left alone, the two will connect again! A friend's other headset connected, but had the same problems as the phone. That was an LG HBM-210. The signal was good for up to a minute, then down for at least a minute, over and over. Before the upgrade everything worked perfectly. What happened, or what did I forget to do? Might I have removed something critical when I switched Maverick 64-bit to the lubuntu package, and tried to remove some redundancies?
I want to upgrade kernel to 2.6..36 from 2.6.18 of CentOS 5.5. The make process is successful but prompt "could not find filesystem /dev/boot " after reboot.
Some articles suggest to edit file .config and set CONFIG_SYSFS_DEPRECATED_V2 to 'y' and re-make kernel. However, the problem still stand there after reboot again.
I was using 9.04 for a while because it was working for me, I decided to upgrade yesterday using the Upgrade button on synaptic to 9.10. Now when I boot I get an error message: Code: chroot: cannot execute /etc/apparmor/initramfs: No such file or directory Mount of filesystem failed. A maintenance shell will now be started. CONTROL-D will terminate this shell and re-try I want to try to fix the problem so I do not have to do fresh installation.
I tried upgrading to 11.04 this morning and after rebooting grub left me at the grub rescue> prompt with the message 'error: unknown filesystem'. I've tried purging and reinstalling grub using a live-cd but no joy.
Let me know what additional information to provide. EDIT: Here is the output from the Boot Info Script
I upgraded 9.10 to 10.04 via the web. The program announced it would take several hours, and when I came back to check, computer was off (kids?). Anyway, machine boots and 10.04 starts, but then blinks a few times and goes to a prompt. What should I tell it?
I have a 10.04 disc too, but it won't run from that either (Cannot mount dev/loop0 on filesystem.squashfs failed). Same message when I tried to start a nearby Windows machine with it. Disc "verified" when I made it. What's with that?
Is that possible, I mean when I upgrade F10 to F11 with yum upgrade is there a way to 'upgrade' the filesystem to ext4 for example (with the exception of boot partition)? Or I have to reinstall fedora like new?
While changing the filesystem can I do it by parts? what I mean is for example: I have 2 partitions like '/' and '/home' with ext3, so I backup data in '/home', change '/' to ext4 then mv files from '/home' to '/' and change '/home' to ext4 and finally mv those files from '/' to '/home'. Is that possible?
I cannot seem to get past the "creating File System.." window on a laptop upgrade
Setup: Thinkpad T23 (dual boot) upgrade from fc10 using DVD iso.checked with checksum and burnt by K3b.
History/actions taken:
Burnt iso to DVD and install/upgrade froze "creating File System " froze after approximately 10 minutes. (completely froze and had to use the power button!)
Checked disk OK on laptop, tried again, same fault.
Bought another DVD.(different die) and tried again, same fault.
Tried another laptop HD, (full install not dual boot) , same fault.
Removed partitions with fdisk, but still no luck.
Tried disk on a spare HD on my PC and it works, I get into the window allowing software selection!
Tried a "Linux Format" fc 10 disk and that works, also tried a PCLinux LXF disk which also worked.
The laptop does not report any problems at bootup and I do not not what else to try
telling the exact macro name and location, by which I can gain control over the following kernel base level structure
1. strct super_block of Virtual File System, for super block object. 2. strct inode for inode ofject of VFS. 3 file structure for file object of VFS.
in addition to these if you know location to access other kernel structure.Please let me know.My main objective is to get the access to the structure pointer of these structure by which i can have access over the individual fields o these structure.
I recently upgraded from 10.10 to 11.04. I'm on a Dell XPS Studio 1640 and have Ubuntu installed in Virtual Box.A lot of the time when I log in the main menu goes to an old grey theme and windows are the same when opened. I think the Gnome theme is not been loaded correctly?Sometimes it is fine and has the nice default Ubuntu-Default-Dark icons.
We all know linux kernel base layer is made up of structures, in which every object of kernel is well defined. Structure members correspond to object properties required to define object behavior.
For example if we take case of File system.It composed of four objects , superblock objects, inode objects, file objects and dentry object.Each having well defined structure which is being operated by system call handler and by system call service routine in the kernel mode.
Now my question is even in kernel mode we do not have some mechanism by which we can get access to pointer of these structures.We have some macro.
If I want to manipulate structure on my on way, or performing some more operation defined by me.For example after the crash of Hard Disk Drive, having ext2/3 file system, If i want to know all the inode pointers, and block details.
Can I have some way out to do desired operation ??
mechanism to operate on these base label structures, even in kernel mode ..
I'm running 10.10 with an NVIDIA card which has a customised xconfig file (to allow use of an EDID file). This was working OK until I ran a set of security updates which included a kernel upgrade. Now when I try to boot the machine, it goes straight to terminal mode and will not run the GUI.
I recall seeing something about this before, but can't find the thread. It's a fairly simple fix to get the graphics running again, but I can't remember what the solution is.
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies. linux-headers-generic-lts-backport-maverick: Depends: linux-headers-2.6.35-30-generic but it is not going to be installed E: Broken packages
I'm running the 64 bit version of Ubuntu 9.10 on an AMD64 dual core platform with all the most recent upgrades installed. After the most recent Kernel upgrade version 2.6.31.20 the computer failed to boot correctly. Extremely slow getting to the desktop and a general failure to preload any programs that I load on boot. I had to uninstall and revert back to the previous Linux headers which solved the problem. If it makes any difference I have the machine setup as an apache2 server along with my standard desktop environment.
I performed an upgrade via the Update Manager from 9.10 to 10.04 LTS and it seemed to go flawlessly. However, now I cannot seem to be able to remove the old Kernel from 9.10 in the package manager. It does not even show 2.6.32-21 as installed but it still shows the old Kernel in Grub. I did a sudo update-grub but it was to no avail.
I wonder if others have upgraded their Lucid kernel using the deb [URL]..repository. I have been using the repository for some time now without any apparent problems, and have gone from 2.6.36-1, through 2.6.37-10, and am now on 2.6.37-12.
All of these seem to work with no problems at all, but I am just wondering if other users can also report success, or if there are any trip-ups that might occur. I still keep updating the "standard" kernel from the main repos, ie 2.6.32-27, so I have that as a backup, but I'm just very curious about other people's findings.
I read recently about security flaws in the ubuntu kernel, and when I checked my kernel, it is 2.6.32-29-generic. I looked in synaptic, and I have the linux-generic meta-package - which should ensure upgrade to the latest kernel, and yet this is not being updated when I run update manager. There is a linux-image-2.6.35-25-generic, but the advice is not to install this directly (to avoid breaking dependencies, etc.), but to install the meta-package instead. Yet, the meta-package doesn't seem to be doing what is should do.
It seems that i am stuck using the 2.6.38-9 kernel, since no matter what i try, i can't update. I have had this problem since 2.6.38-10, but figured that the problem probably would solve itself after the next kernel update, sadly that was not the case.
I have had some worrying error-massages from dpkg about broken packages, which i believe might be the source of this problem, as it reported that the package "linux-image-generic" was broken. I removed the postinstall script from /var/lib/dpkg/info and updated both dpkg and aptitude.
I am not getting any more error messages, and if i look in the synaptic package manager, i can see that kernel 2.6.38-11 is indeed installed, yet i can't select it at bootup, even though i have tried to manually update grub.
I successfully installed Ubuntu 9.10 Netbook Remix on an Asus EeePC in a dual boot mode with Windows XP. Because the computer has no CD drive, I used a USB stick to download the files for installation. Twice now, after upgrading to a new kernel (2.6.31-17 and 2.6.31-19 I think), when rebooting after the upgrade and selecting Ubuntu from the operating system menu, I get a message:
sh:grub>
along with a notice about limited shell commands being available. The ls command results in:
(loop0) (hd0,3) (hd0,2) (hd0,1)
In trying some of the other commands, I get a message that a linux kernel isn't loaded. The computer still runs Windows fine - or at least as fine as Windows ever runs. I'd like to recover Ubuntu without doing another full installation.