Re: [vox-tech] boot failure with KDE
Thanks to all for trying to help. I gave up trying to trouble shoot the problem and reinstalled Lucid. Since I wasn't in danger of losing any data, this seemed like a more efficient option. Thomas On Mon, Jun 14, 2010 at 1:32 PM, Bill Kendrick wrote: > On Sun, Jun 13, 2010 at 09:38:45PM -0700, Thomas Johnston wrote: >> I am running Kubuntu 10.04 and I am no longer able to boot up as >> normal. I make it to the login screen without any indication of a >> problem. After typing in my user name and password, it continues to >> boot. > > Just to be pedantic (it helps to use the right terminology when > asking for help, is all), at this point you aren't "booting" any more. > Once the login screen is up, your computer is completed booted-up. > At this point, you're logging in to your KDE X-Window session. > > (So it's not really a "can't boot", but a "can't login" problem) > > -bill! > ___ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On Sun, Jun 13, 2010 at 09:38:45PM -0700, Thomas Johnston wrote: > I am running Kubuntu 10.04 and I am no longer able to boot up as > normal. I make it to the login screen without any indication of a > problem. After typing in my user name and password, it continues to > boot. Just to be pedantic (it helps to use the right terminology when asking for help, is all), at this point you aren't "booting" any more. Once the login screen is up, your computer is completed booted-up. At this point, you're logging in to your KDE X-Window session. (So it's not really a "can't boot", but a "can't login" problem) -bill! ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On Sun, 2010-06-13 at 21:38 -0700, Thomas Johnston wrote: > I am running Kubuntu 10.04 and I am no longer able to boot up as > normal. I make it to the login screen without any indication of a > problem. After typing in my user name and password, it continues to > boot. Normally the remaining boot sequence shows several icons > appearing in the center of the screen; however, after the first icon > appears the system now hangs. After several minutes an error message > pops up reading: > > "The following installation problem was detected while trying to start KDE: > No write access to $HOME directory (/home/thomas). > KDE is unable to start." I see you've tried fscking the drive to look for drive errors, but have you tried looking to see whether an indiscriminate typo caused you to change permissions on your home directory? ls -l /home and see whether you have write permission on /home/thomas ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On Sun, 2010-06-13 at 23:51 -0700, Tony Cratz wrote: > On 06/13/2010 11:47 PM, Thomas Johnston wrote: > > after typing fsck /dev/sda1 I get the following: > > > > "WARNING!!! The filesystem is mounted. If you continue you ***WILL*** > > cause ***SEVERE*** filesystem damage. > > Do you really want to continue (y/n)? > > > > so I aborted. > > > umount /dev/sda1 > fsck /dev/sda1 replace that umount command with umount -a ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On Sun, 2010-06-13 at 23:20 -0700, Thomas Johnston wrote: > update: I tried the failsafeX mode I mentioned in my last email and > get the following error messages: > > "Ubuntu is running in low-graphics mode. The following error was > encountered. You may need to update your configuration to solve this. > (EE) [drm] failed to open device > (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) > (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not > found)" Do you get an actual graphics screen when you do that? I think that this is the expected behavior when running in this mode, and I wouldn't worry about it. --Ken ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On 06/14/2010 02:54 AM, Thomas Johnston wrote: > I still can't boot normally. I tried uninstalling (sudo aptitude > remove nvidia-current) and reinstalling the nvidia drivers. That > didn't change anything. I tried purging nvidia. That didn't work. I > even tried uninstalling and reinstalling xorg to no avail. In fact, > the problem is a little worse now. I can boot to the login screen and > if I try to login it almost immediately takes me back to the same > login screen. The only way to get to a terminal now is to boot into > recovery mode from GRUB. Well not being in front of the system I can't say why it is not working for you. It should have. At this point it sound like you might need to do a clean install. You can do it without losing your home directory (assuming that /home is on it's own partition). Before you do a fresh install, back up all key data and configure file. But you might try to get someone closer to where you live to work with you on trying to figure out what is wrong before you do a fresh install. Tony ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
I still can't boot normally. I tried uninstalling (sudo aptitude remove nvidia-current) and reinstalling the nvidia drivers. That didn't change anything. I tried purging nvidia. That didn't work. I even tried uninstalling and reinstalling xorg to no avail. In fact, the problem is a little worse now. I can boot to the login screen and if I try to login it almost immediately takes me back to the same login screen. The only way to get to a terminal now is to boot into recovery mode from GRUB. thomas On Mon, Jun 14, 2010 at 12:42 AM, Tony Cratz wrote: > On 06/14/2010 12:20 AM, Thomas Johnston wrote: >> I noticed in yesterday's instructions to Hai someone mentioned using a >> Live CD. I downloaded and burned Lucid 64 bit from Kubuntu.org and >> booted from the Live CD. I opened konsole and typed: >> >> sudo e2fsck -C0 -p -f -v /dev/sda1 and it gives the following: >> 430625 inodes used (2.94%) >> 615 non-contiguous files (0.1%) >> 452 non-contiguous directories (0.1%) >> # of inodes with ind/dind/tind blocks: 0/0/0 >> Extent depth histogram: 410276/301 >> 46160360 blocks used (78.82%) >> 0 bad blocks >> 5 large files >> >> 359758 regular files >> 45444 directories >> 60 character device files >> 26 block device files >> 0 fifos >> 607 links >> 25327 symbolic links (19951 fast symbolic links) >> 1 socket >> ___ >> 431223 files > > > Good, the partition should now be clean. You should be able > to boot up normally if this was the only problem. Otherwise > you may have issues where you might need to install the > missing driver. This can be done from the failsafe login. > > > Tony > ___ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On 06/14/2010 12:20 AM, Thomas Johnston wrote: > I noticed in yesterday's instructions to Hai someone mentioned using a > Live CD. I downloaded and burned Lucid 64 bit from Kubuntu.org and > booted from the Live CD. I opened konsole and typed: > > sudo e2fsck -C0 -p -f -v /dev/sda1 and it gives the following: > 430625 inodes used (2.94%) > 615 non-contiguous files (0.1%) > 452 non-contiguous directories (0.1%) > # of inodes with ind/dind/tind blocks: 0/0/0 > Extent depth histogram: 410276/301 > 46160360 blocks used (78.82%) > 0 bad blocks > 5 large files > > 359758 regular files > 45444 directories > 60 character device files > 26 block device files > 0 fifos > 607 links > 25327 symbolic links (19951 fast symbolic links) > 1 socket > ___ > 431223 files Good, the partition should now be clean. You should be able to boot up normally if this was the only problem. Otherwise you may have issues where you might need to install the missing driver. This can be done from the failsafe login. Tony ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
I noticed in yesterday's instructions to Hai someone mentioned using a Live CD. I downloaded and burned Lucid 64 bit from Kubuntu.org and booted from the Live CD. I opened konsole and typed: sudo e2fsck -C0 -p -f -v /dev/sda1 and it gives the following: 430625 inodes used (2.94%) 615 non-contiguous files (0.1%) 452 non-contiguous directories (0.1%) # of inodes with ind/dind/tind blocks: 0/0/0 Extent depth histogram: 410276/301 46160360 blocks used (78.82%) 0 bad blocks 5 large files 359758 regular files 45444 directories 60 character device files 26 block device files 0 fifos 607 links 25327 symbolic links (19951 fast symbolic links) 1 socket ___ 431223 files thomas On Sun, Jun 13, 2010 at 11:54 PM, Thomas Johnston wrote: > device is busy. (In some cases useful info about processes that use > the device is found by lsof(8) or fuser(1)) > > > On Sun, Jun 13, 2010 at 11:51 PM, Tony Cratz wrote: >> On 06/13/2010 11:47 PM, Thomas Johnston wrote: >>> after typing fsck /dev/sda1 I get the following: >>> >>> "WARNING!!! The filesystem is mounted. If you continue you ***WILL*** >>> cause ***SEVERE*** filesystem damage. >>> Do you really want to continue (y/n)? >>> >>> so I aborted. >> >> >> umount /dev/sda1 >> fsck /dev/sda1 >> >> >> Tony >> ___ >> vox-tech mailing list >> vox-tech@lists.lugod.org >> http://lists.lugod.org/mailman/listinfo/vox-tech >> > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
device is busy. (In some cases useful info about processes that use the device is found by lsof(8) or fuser(1)) On Sun, Jun 13, 2010 at 11:51 PM, Tony Cratz wrote: > On 06/13/2010 11:47 PM, Thomas Johnston wrote: >> after typing fsck /dev/sda1 I get the following: >> >> "WARNING!!! The filesystem is mounted. If you continue you ***WILL*** >> cause ***SEVERE*** filesystem damage. >> Do you really want to continue (y/n)? >> >> so I aborted. > > > umount /dev/sda1 > fsck /dev/sda1 > > > Tony > ___ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On 06/13/2010 11:47 PM, Thomas Johnston wrote: > after typing fsck /dev/sda1 I get the following: > > "WARNING!!! The filesystem is mounted. If you continue you ***WILL*** > cause ***SEVERE*** filesystem damage. > Do you really want to continue (y/n)? > > so I aborted. umount /dev/sda1 fsck /dev/sda1 Tony ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
after typing fsck /dev/sda1 I get the following: "WARNING!!! The filesystem is mounted. If you continue you ***WILL*** cause ***SEVERE*** filesystem damage. Do you really want to continue (y/n)? so I aborted. thomas On Sun, Jun 13, 2010 at 11:44 PM, Tony Cratz wrote: > On 06/13/2010 11:42 PM, Thomas Johnston wrote: >> Just to be painfully clear as to what I am doing: >> (1) power on, hold down shift key >> (2) highlight boot option, "Ubuntu, with Linux 2.6.32-22-generic >> (recovery mode)" and press 'e' to edit the commands >> (3) from the recovery menu, choose 'root' drop to root shell prompt >> (4) I enter my root password and then run fsck /home, which gives the >> following output: >> # fsck /home >> fsck from util-linux-ng 2.17.2 >> e2fsck 1.41.11 (14-Mar-2010) >> fsck.ext2: Is a directory while trying to open /home >> >> The superblock could not be read or does not describe a correct ext2 >> filesystem. If the device is valid and it really contains an ext2 >> filesystem (and not swap or ufs or something else), then the >> superblock is corrupt, and you might try running e2fsck with an >> alternate superblock: e2fsck –b 8193 >> >> >> I am not sure that this is relevant, but my /dev/sda1 is type ext4 > > > try fsck /dev/sda1 > > > > Tony > ___ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On 06/13/2010 11:42 PM, Thomas Johnston wrote: > Just to be painfully clear as to what I am doing: > (1) power on, hold down shift key > (2) highlight boot option, "Ubuntu, with Linux 2.6.32-22-generic > (recovery mode)" and press 'e' to edit the commands > (3) from the recovery menu, choose 'root' drop to root shell prompt > (4) I enter my root password and then run fsck /home, which gives the > following output: > # fsck /home > fsck from util-linux-ng 2.17.2 > e2fsck 1.41.11 (14-Mar-2010) > fsck.ext2: Is a directory while trying to open /home > > The superblock could not be read or does not describe a correct ext2 > filesystem. If the device is valid and it really contains an ext2 > filesystem (and not swap or ufs or something else), then the > superblock is corrupt, and you might try running e2fsck with an > alternate superblock: e2fsck –b 8193 > > > I am not sure that this is relevant, but my /dev/sda1 is type ext4 try fsck /dev/sda1 Tony ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
Just to be painfully clear as to what I am doing: (1) power on, hold down shift key (2) highlight boot option, "Ubuntu, with Linux 2.6.32-22-generic (recovery mode)" and press 'e' to edit the commands (3) from the recovery menu, choose 'root' drop to root shell prompt (4) I enter my root password and then run fsck /home, which gives the following output: # fsck /home fsck from util-linux-ng 2.17.2 e2fsck 1.41.11 (14-Mar-2010) fsck.ext2: Is a directory while trying to open /home The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck –b 8193 I am not sure that this is relevant, but my /dev/sda1 is type ext4 thomas On Sun, Jun 13, 2010 at 11:20 PM, Tony Cratz wrote: > On 06/13/2010 11:14 PM, Thomas Johnston wrote: >> Tony, >> >> Thanks for the reply. I'm sorry, but I am not a very sophisticated >> Linux user. Could you be a little detailed with your answers? >> >> I have tried to Google how to boot in single user mode without much >> luck. So far I have found two things: >> (1) one website calls changing the run level to 1 entering 'single user' mode >> (2) a second says to hold down the "shift" key at beginning of the >> boot sequence. I tried this and was presented with the option to boot >> several different kernels (and each kernel had a recovery mode >> option). At the bottom of the screen it sasy: "Press enter to boot >> the selected OS, 'e' to edit the commands before booting or 'c' for a >> command-line." If I highlight the latest kernel (Ubuntu, with Linux >> 2.6.32-22-generic (recovery mode) and press 'e', I get several more >> options, one of which is: linux /boot/vmlinuz-2.6.32.-22-generic >> root=UUID=long alpha-numeric string ro single. I highlighted this >> option and pressed "ctrl-x" to boot it. I then get a recovery menu >> which has various options: resume, clean, dpkg, failsafeX, grub, >> netroot, root >> >> I am in the ballpark of what you were suggesting I do? > > > Yes you are in the ball park. Please see yesterday E-mail to Hai > Yi about going into Grub and then 'drop to root shell'. > > > With most versions of *nix you can get into the single user > mode during the boot up procedure. *buntu has made it easy > with Grub and the 'Recover' mode. > > Once you are in single user mode (root) then you should do > an 'fsck /home' to insure the partition is clean. Once it is > it should then be able to be mounted as read/write (which is > the error you where having). > > > Tony > ___ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
update: I tried the failsafeX mode I mentioned in my last email and get the following error messages: "Ubuntu is running in low-graphics mode. The following error was encountered. You may need to update your configuration to solve this. (EE) [drm] failed to open device (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found) (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)" thomas On Sun, Jun 13, 2010 at 11:14 PM, Thomas Johnston wrote: > Tony, > > Thanks for the reply. I'm sorry, but I am not a very sophisticated > Linux user. Could you be a little detailed with your answers? > > I have tried to Google how to boot in single user mode without much > luck. So far I have found two things: > (1) one website calls changing the run level to 1 entering 'single user' mode > (2) a second says to hold down the "shift" key at beginning of the > boot sequence. I tried this and was presented with the option to boot > several different kernels (and each kernel had a recovery mode > option). At the bottom of the screen it sasy: "Press enter to boot > the selected OS, 'e' to edit the commands before booting or 'c' for a > command-line." If I highlight the latest kernel (Ubuntu, with Linux > 2.6.32-22-generic (recovery mode) and press 'e', I get several more > options, one of which is: linux /boot/vmlinuz-2.6.32.-22-generic > root=UUID=long alpha-numeric string ro single. I highlighted this > option and pressed "ctrl-x" to boot it. I then get a recovery menu > which has various options: resume, clean, dpkg, failsafeX, grub, > netroot, root > > I am in the ballpark of what you were suggesting I do? > > thanks again, > > thomas > > > > > On Sun, Jun 13, 2010 at 9:55 PM, Tony Cratz wrote: >> On 06/13/2010 09:38 PM, Thomas Johnston wrote: >>> "The following installation problem was detected while trying to start KDE: >>> No write access to $HOME directory (/home/thomas). >>> KDE is unable to start." >> >> Have you tried to come up as single user via Grub? If not >> try it. You may find that fsck has failed on /home. Run it >> by hand. Then try rebooting. >> >> >> >> Tony >> ___ >> vox-tech mailing list >> vox-tech@lists.lugod.org >> http://lists.lugod.org/mailman/listinfo/vox-tech >> > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On 06/13/2010 11:14 PM, Thomas Johnston wrote: > Tony, > > Thanks for the reply. I'm sorry, but I am not a very sophisticated > Linux user. Could you be a little detailed with your answers? > > I have tried to Google how to boot in single user mode without much > luck. So far I have found two things: > (1) one website calls changing the run level to 1 entering 'single user' mode > (2) a second says to hold down the "shift" key at beginning of the > boot sequence. I tried this and was presented with the option to boot > several different kernels (and each kernel had a recovery mode > option). At the bottom of the screen it sasy: "Press enter to boot > the selected OS, 'e' to edit the commands before booting or 'c' for a > command-line." If I highlight the latest kernel (Ubuntu, with Linux > 2.6.32-22-generic (recovery mode) and press 'e', I get several more > options, one of which is: linux /boot/vmlinuz-2.6.32.-22-generic > root=UUID=long alpha-numeric string ro single. I highlighted this > option and pressed "ctrl-x" to boot it. I then get a recovery menu > which has various options: resume, clean, dpkg, failsafeX, grub, > netroot, root > > I am in the ballpark of what you were suggesting I do? Yes you are in the ball park. Please see yesterday E-mail to Hai Yi about going into Grub and then 'drop to root shell'. With most versions of *nix you can get into the single user mode during the boot up procedure. *buntu has made it easy with Grub and the 'Recover' mode. Once you are in single user mode (root) then you should do an 'fsck /home' to insure the partition is clean. Once it is it should then be able to be mounted as read/write (which is the error you where having). Tony ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
Tony, Thanks for the reply. I'm sorry, but I am not a very sophisticated Linux user. Could you be a little detailed with your answers? I have tried to Google how to boot in single user mode without much luck. So far I have found two things: (1) one website calls changing the run level to 1 entering 'single user' mode (2) a second says to hold down the "shift" key at beginning of the boot sequence. I tried this and was presented with the option to boot several different kernels (and each kernel had a recovery mode option). At the bottom of the screen it sasy: "Press enter to boot the selected OS, 'e' to edit the commands before booting or 'c' for a command-line." If I highlight the latest kernel (Ubuntu, with Linux 2.6.32-22-generic (recovery mode) and press 'e', I get several more options, one of which is: linux /boot/vmlinuz-2.6.32.-22-generic root=UUID=long alpha-numeric string ro single. I highlighted this option and pressed "ctrl-x" to boot it. I then get a recovery menu which has various options: resume, clean, dpkg, failsafeX, grub, netroot, root I am in the ballpark of what you were suggesting I do? thanks again, thomas On Sun, Jun 13, 2010 at 9:55 PM, Tony Cratz wrote: > On 06/13/2010 09:38 PM, Thomas Johnston wrote: >> "The following installation problem was detected while trying to start KDE: >> No write access to $HOME directory (/home/thomas). >> KDE is unable to start." > > Have you tried to come up as single user via Grub? If not > try it. You may find that fsck has failed on /home. Run it > by hand. Then try rebooting. > > > > Tony > ___ > vox-tech mailing list > vox-tech@lists.lugod.org > http://lists.lugod.org/mailman/listinfo/vox-tech > ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
Re: [vox-tech] boot failure with KDE
On 06/13/2010 09:38 PM, Thomas Johnston wrote: > "The following installation problem was detected while trying to start KDE: > No write access to $HOME directory (/home/thomas). > KDE is unable to start." Have you tried to come up as single user via Grub? If not try it. You may find that fsck has failed on /home. Run it by hand. Then try rebooting. Tony ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
[vox-tech] boot failure with KDE
I am running Kubuntu 10.04 and I am no longer able to boot up as normal. I make it to the login screen without any indication of a problem. After typing in my user name and password, it continues to boot. Normally the remaining boot sequence shows several icons appearing in the center of the screen; however, after the first icon appears the system now hangs. After several minutes an error message pops up reading: "The following installation problem was detected while trying to start KDE: No write access to $HOME directory (/home/thomas). KDE is unable to start." After clicking "OK" to close the error message, a second message appears reading: " Could not start ksmserver. Check your installation." Clicking "Okay" on this messages returns me to the login screen. A couple of notes: (1) I am still able to get in via the "Console login". (I think it is a virtual terminal) (2) I don't know exactly what caused this sudden failure to boot properly. Besides email and browsing the web, the last thing I attempted to do was install veetle (a P2P TV program). I didn't notice any error messages during the install. Any ideas? Thanks in advance, Thomas ___ vox-tech mailing list vox-tech@lists.lugod.org http://lists.lugod.org/mailman/listinfo/vox-tech
