[resolved] Update killed file system

[dibl]

Re: Update killed file system

The filesystem gets mounted read-only when there is a problem from fsck.

Can you run fsck from your Jaunty system on it (while unmounted, of course)?

[doctordruidphd]

Re: Update killed file system

yes.

greenman@Wolfenstein:~$ sudo fsck /dev/sda3
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
Experimental: clean, 867278/6406144 files, 7270423/25599577 blocks

greenman@Wolfenstein:~$ sudo fsck -f /dev/sda3
fsck 1.41.4 (27-Jan-2009)
e2fsck 1.41.4 (27-Jan-2009)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Experimental: 867278/6406144 files (0.3% non-contiguous), 7270423/25599577 blocks

[dibl]

Re: Update killed file system

Yep. It look OK when you fsck it from the other system.

Does mando hacker's suggestion help:

http://kubuntuforums.net/forums/inde...6353#msg196353

[doctordruidphd]

Re: Update killed file system

I can get the system partially running with the following, when it boots into the "maintenance shell":

mount -o remount /
start dbus
start hal
start network-manager
init 5

kde then starts up, but things are missing on the desktop, and audio (alsa) is completely dead.
the 'dpkg --configure -a' and 'apt-get install -f' did nothing. There were a few more updates that went through, including one mentioning init scripts, but this didn't fix the boot problem. I also tried 'sudo dpkg-reconfigure bash', from some other message that mentioned this might fix the scripts, but it didn't.

So, the system is bootable, but not really useable.

Edit: funny thing, through all this, the video driver still works!

Edit again: As mando_hacker states, the problem is the startup scripts. I checked the symlink in /bin/sh, and it is there, pointing to dash. I tried changing it o bash, but that didn't help (changed it back). I found the initscript package in /var/cache/apt/archives and reinstalled it, but no help. So we are basically in limbo with not startup script. I did get sound working again with 'udev start', but other things. like wine, still don't work. So to fix this, we need to get the startup scripts working. That's where things are hanging at the moment.

[doctordruidphd]

Re: Update killed file system

Furthermore:

Investigating the /etc/rcS.d directory, in my working pre-update karmic system, we have:

greenman@Wolfenstein:/media/sda3/etc/rcS.d$ ls /media/sda1/etc/rcS.d
README               S15module-init-tools S35mountall.sh      S44nfs-common
S01mountkernfs.sh          S17procps       S35quota         S45mountnfs.sh
S01readahead            S20checkroot.sh    S36mountall-bootclean.sh S46mountnfs-bootclean.sh
S02hostname.sh           S22mtab.sh      S37apparmor        S46setserial
S03splashy             S25brltty       S37mountoverflowtmp    S47lm-sensors
S06keyboard-setup          S26cryptdisks-early  S37udev-finish      S49console-setup
S07linux-restricted-modules-common S26cryptmount-early  S39readahead-desktop   S55bootmisc.sh
S10udev               S28cryptdisks     S39ufw          S55urandom
S11mountdevsubfs.sh         S30checkfs.sh     S40networking       S70screen-cleanup
S13pcmciautils           S30etc-setserial   S43portmap        S70x11-common

Whereas in the broken system, we have:

greenman@Wolfenstein:/media/sda3/etc/rcS.d$ ls
README               S13pcmciautils    S30etc-setserial   S43portmap    S55urandom
S01readahead            S25brltty      S35quota       S44nfs-common   S70screen-cleanup
S03splashy             S26cryptdisks-early S37apparmor      S46setserial   S70x11-common
S06keyboard-setup          S26cryptmount-early S39readahead-desktop S47lm-sensors
S07linux-restricted-modules-common S28cryptdisks    S39ufw        S49console-setup

That don't look right to me, ma.

[GreyGeek]

Re: Update killed file system

...
Does mando hacker's suggestion help:

http://kubuntuforums.net/forums/inde...6353#msg196353

Yes, eventually. The command "dpkg --configure -a" didn't appear to do anything for me. It just immediately returned the prompt. I have used that command before, when testing Jaunty's alpha, so I know what it usually does. It didn't do anything. However, I plugged in an ethernet cable from the back of my wireless (even wicd wouldn't connect) and then ran "sudo aptitude -if install" a couple times and it seemed to fix some things. Then, for grins and giggles, I did the three apt-get commands and some more things got fixed. I repeated them until they returned nothing. THen I rebooted and low and behold! I got the KDE 4.3.1 desktop! So far, everything is checking out.

[doctordruidphd]

Re: Update killed file system

The most recent set of updates includes an update to upstart, which seems to have helped.
I can now get to kde without typing in anything, though it is pulling several errors that mention udev rules. We'll wait and see what tomorrow's updates bring before marking this [solved].

[GreyGeek]

Re: Update killed file system

The most recent set of updates includes an update to upstart, which seems to have helped.
I can now get to kde without typing in anything, though it is pulling several errors that mention udev rules. We'll wait and see what tomorrow's updates bring before marking this [solved].

I, too, noticed those udev rule errors. Something about "MNAME="%K%" something something breaks kernel name usage... and several others. They fly by so fast I can barely tell what they are. However, I have scoured all the logs and find no mention of udev rule breakages during boot. There was another 47MB pile of updates this morning, including a new header for 2.6.31-10-generic kernel.

[dibl]

Re: Update killed file system

Did you guys see this?:

http://ubuntuforums.org/showthread.php?t=1267657

[doctordruidphd]

Re: Update killed file system

Did you guys see this?:

http://ubuntuforums.org/showthread.php?t=1267657

Interesting, but wouldn't have helped me much yesterday, as I couldn't get that far. It was choking on the transition between initramfs and /. That's where it's supposed to start the initialization scripts, which evidently weren't there.

What did get me up and running from the "maintenance shell" is this, for the record:

mount -o remount /
start dbus
start hal
start udev
start network-manager
start kdm

Somehow, through all this,. the video driver survived. But alsa didn't. After a series of 'sudo apt-get update' and 'apt-get dist-upgrade', the script problem was fixed, and I could boot. Alsa works, but pulseaudio doesn't (sound is choppy), and I am getting quite a few errors in the bootup process (the udev errors mentioned above, and a few things not being found). Basic functionality has returned, so we'll wait out the audio issues.
Thanks to all who helped. I wish I had seen the "don't update" thread before I had done it

[GreyGeek]

Re: Update killed file system

Did you guys see this?:

http://ubuntuforums.org/showthread.php?t=1267657

That was funny!

Did you notice that the really sharp guys are also funny? (Which probably explains why I have no sense of humor!)

I took the recovery option of the latest kernel and then selected the "root terminal with network connection" while having my ethernet cable from the back of my wireless modem plugged in. Then I did all of the steps he mentioned and that's what got me going again. The "apt-get -f install" pulled down another dozen MB of files, and "apt-get update" and "apt-get upgrade" followed by "apt-get dist-upgrade" pulled in some more. On reboot the KDE4 desktop came up. I still get the wild udev error message during boot-up, however, and they leave no trace in any of the logs.