Watch out for todays upgrade......

[Guest]

Re: Watch out for todays upgrade......

Fintan, it could be as simple as your PATH settings being screwed up. What happens when you

echo $PATH

from the command line? If you get a blank line, try

export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"

and then see if bash can find apt, etc.

[Fintan]

Re: Watch out for todays upgrade......

Okay I'll give that a roll

[MepisReign]

Re: Watch out for todays upgrade......

After the upgrade my system did BOOT with no problems except for some broken dependencies on KDM and JAVA plugin, the adept notifier remained on the taskbar. After that I typed on the Konsole "sudo --configure -a" in order to install the pending packages (that ones that actually were downloaded without problems).
So far the system is booting fine, I will wait for that issues to be solved before take any "drastic" :P actions

[Fintan]

Re: Watch out for todays upgrade......

Fintan, it could be as simple as your PATH settings being screwed up. What happens when you

echo $PATH

from the command line? If you get a blank line, try

export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games"

and then see if bash can find apt, etc.

Okay did that, tried to reboot and got two messages that told me something about a bad usb cable. I didn't have any devices pluged in so I gave up and did a clean install. I am downloading the updtaes/-grades now and hope for the best.

I could have delt with broken depencies but not this.

Any way thank you all for your support.

Cheers
Fintan

[MepisReign]

Re: Watch out for todays upgrade......

Humm, sorry to hear that man, hopefully the clean install will solve the issues that the system may have, in any case those are the problems that as Beta users we are exposed to suffer

Take Care and Good Luck

[Fintan]

Re: Watch out for todays upgrade.[sort of solved]

Yeah I know, and I'm not gripping. The clean install is still stable and I am going to stay away from updates/-grades for a while, although I don't know if I can control myself

It would be a nice improvement to see a real system rescue in the alt cd instead of the one offered. Maybe something like the one suse and some other distros have.

Again thanks for the help and support

Cheers
Fintan

[dibl]

Re: Watch out for todays upgrade......

Bummer, Fintan -- sorry.

Here's a little p.s., for whatever it is worth. I'm completely current as of 1600 hours, 4 APR, Eastern U.S. time -- neither Adept Notifier nor the Adept Manager shows anything "pending" after I run updates and upgrades and dist-upgrades.

HOWEVER, upon reviewing the packages listed in the Adept Manager, I see the linux-2.6.20-14-generic packages. I'm running 2.6.20-13-generic. Isn't that odd -- they are sitting there -- theoretically I could select them for installation, but the dist-upgrade command returns nothing available.

I think I'll sit tight with a system that is working really well, for a day or two -- I'm suspicious of the situation with the -14 packages.

[Detonate]

Re: Watch out for todays upgrade......

Saw this thread early this morning, and decided to wait before updating. Just ran update, upgrade, and dist-upgrade with aptitude, rebooted with no problems. But it did reboot to -13, -14 was not listed in the grub menu. 1630 hrs, mdt, usa.

[nejode]

Re: Watch out for todays upgrade......

Well, just for the record, I upgraded 88 packages (158 mb) as of 15:00 local (Venezuela, GMT-4 hours), just read this post, rebooted to kernel -13 (as dibl said, -14 kernel is in the repos but there was no kernel upgrade) and found no problems whatsoever.

Usually, with a regular release, I'll wait for a couple of days before upgrading anything that has to do with kernels, xorg, apt, etc, and that saved me from the xorg-xserver upgrade chaos and the KDE 3.5.4 mess a few months ago... but with these beta's, upgrades come out so quickly that if you wait 2 days, maybe you'll have to deal with a 200+ mb download!

[dibl]

Re: Watch out for todays upgrade......

Fintan, I reproduced your failure! But, you did not say that you added or modified disk partitions on another drive, so maybe I got the same result via a different causal factor.

I decided to give the 64-bit Feisty Beta a trial run, since I have a Core 2 Duo with the EM64T architecture. To make a place for it, I removed a large partition on a hard drive and split it into two pieces, one for / and one for /home. The experiment went great -- of course a new Grub menu was written and the new OS promoted itself to the top of the list, etc. etc. The new OS runs great, but a benchmark test that I use revealed that it doesn't run my app any faster than the -generic OS.

However, when I rebooted and picked my previous OS from the bottom of the Grub list, it failed to boot in EXACTLY the manner that you reported. FSCK went perfectly, then it reported that it would not mount "UUID-e7960f07-be4a ......... -- no such device"! Then came the same errors you saw -- no apt-get, no job control, no groups, no bash commands ... blah blah blah, just as you said. Left me at the root login, with barely the ability to shut it down.

I worked on the problem a little while and figured out that the change of partitioning on the second drive resulted in a wrong fstab file on the first drive (the original OS). When the original OS was trying to mount the drives in /media, the fstab map was no longer true to the actual partitions out there, due to the change I had made. I recovered by editing the fstab file in the original Feisty installation and changed "UUID=xxxxxxx" to "'/dev/sdc2" and then I needed to add the additional partition that I had created as /dev/sdc3, and VOILA I was back in business.

So, there is a way to cause the problem and a way to fix it, should it ever happen again.

[shadowfx78]

Re: Watch out for todays upgrade......

in synaptic click on the edit menu and look for the fix broken packages option.

[penguin.ch]

Re: Watch out for todays upgrade......

changed "UUID=xxxxxxx" to "/dev/sdc2"

In additition to that, I'd recommend to replace all (so-called) UUIDs by the original devices nodes (in /etc/fstab as well as /boot/grub/menu.lst), at least to eliminate this well-known source of trouble ...

[Fintan]

Re: Watch out for todays upgrade......

@dibl Thanks and of course you are right. I did delete a partition at the END of my disk so I didn't think that would change anything with the partitions in front of it. Well I suppose it did. Stupid me for not changing fstab and grub like i did in edgy (as mentioned by unicorn).
I will do that know.

Thanks again.

Well now I have another problem. After reinstalling and rebooting twice without a problem I now get this message: hub 4-0:1,0: Cannot enable port2. Maybe the USB cable is bad?

I connected my scanner this morning because I wanted to test it. It worked fine before the updates.

I can access the feisty partition from edgy.

Any Ideas?

I'll move this to a different post.

[gregconquest]

Re: Watch out for todays upgrade......

I also got the "apt-get" is not installed. I haven't changed any partitions since this version of kubuntu was working. I can refresh my kubuntu image (backup from BootIt NG), have no problems, run "sudo apt-get update" click on the update icon, run through the update, and at reboot, I get the errors mentioned every time.

I also can't update successfully anymore. Some packages never complete no matter how many I select. I'm running through one now. I'll refresh my image, re-try the whole process, and edit this post with the notes . . .

Is there anything in particular I should be looking for? kernel version? apt-get update?

I did have a problem with fstab a few days ago as well. The offending partition was commented out -- perhaps before the install I'm refreshing now.

Greg

Update: my earliest image has some of the same problems. I'm going to re-install fresh.

[gregconquest]

Re: Watch out for todays upgrade......

This is no good. I have all the same problems even from a fresh install:

- I rearrange my partitions (to eliminate post-install partition change variable)
- reinstall kubuntu-7.04-beta-alternate-i386
(from April 1 -- do these CD images change
daily -- or will it stay the same till beta2?)
- grub installed to root (sda4), BootIt NG is in mbr
- reboot
[704ku001.img made]
- boot into 2.6.20-generic
- 49000 days since check -- fixed (1st sign of problems?)
- oem login
- sudo oem-config-prepare
- reboot
[704ku002.img made]
File System Check Failed (the erros are all the same from here)
A log is being saved in /var/log/fsck/checkfs if that location is writeable. Please repair the file system manually.
* A maintenance shell will now be started. CONTROL-D will terminate
bash: no job control in this shell
bash: groups: command not found
sh: groups: not found
("lesspipe" and "The" also not found)
The program apt-get is currently not installed. You can install it by typing: apt-get install apt
- I type EXIT and hit return
- boots into 1st login, my username and all accepted
- KDE launches, login
- adept_updater is waiting -- flashing an update.
- launch updater
install 8, upgrade 255 (incl. adept, adept-batch -common -installer -notifier -updater,
linux generic from 2.6.20.12.8 to 2.6.20.14.12)
- apply updates
- Bluetooth - failed to connect to the SDP server
- Could not commit changes - Adept Updater
Now I'm back to where I was before. No updates will complete.

Greg