Re: Automatic upgrades stalls on the last kernel release
On 28/07/14 15:48:56, Henrique de Moraes Holschuh wrote: Thanks for your reply, Henrique. I don't really know if that was the problem. I thought I'd try the upgrades again, and noticed that it was slowly upgrading - reducing the upgrade queue. after a couple of repeated attempts running the upgrade it cleared the queue and there were no more updates to apply. Hurrah! But then, since there was a new kernel in the upgrades I rebooted, to find the system wouldn't boot. Fortunately, I could still read the disk partitions with user data. I have now just finished installing on a new bigger disk and transferring all the user files, mail system, web pages etc, to the new disk. 1. I'm wondering if it's a disk space issue. Or lack of free inodes issue. Run df -i to check. ___ News is what somebody somewhere wants to suppress; all the rest is just advertising. Lord Northcliffe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1406637806.5908.0@Kingston2
Automatic upgrades stalls on the last kernel release
I seem to have a problem with automatic updates on my system. The AU system has been unable to function normally for some time and I now have something like 61 updates waiting in the queue. When I try to process the updates, it seems to choke on the Linux 3.2 for 64 bit PCs entry, which is linux-image-3.2.0-4-amd64-3.2.60-1 +deb7u1 (64bit) reported as 23.4MBs. The error is Failed to process request. and more details are - 'cannot copy extracted data for '.lib/modules/3.2.0-4amd64/kernel/ drivers/net/wireless/rt2x00/rt61pci.ko' to '/lib/modules/3.2.0-4-amd64/ kernel/drivers/net/wireless/rt2x00/rt61pci.ko.dpkg-new'. If I manually copy the file and rerun the update, it just produces a similar error message with a different file name. df returns the following; test:# df Filesystem 1K-blocksUsed Available Use% Mounted on rootfs329233 270345 41890 87% / udev 10240 0 10240 0% /dev tmpfs 4060201892404128 1% /run /dev/mapper/test-root329233 270345 41890 87% / tmpfs 5120 4 5116 1% /run/lock tmpfs 812020 148811872 1% /run/shm /dev/sdb1 233191 18789201961 9% /boot /dev/mapper/test-home 39502452 5852096 31643728 16% /home /dev/mapper/test-tmp 376807 10303347048 3% /tmp /dev/mapper/test-usr8647944 4809964 3398684 59% /usr /dev/mapper/test-var2882592 971236 1764924 36% /var test# 1. I'm wondering if it's a disk space issue. Can I purge all the update queue and try to update the kernel on its own then the remaining updates. Guiadance would be appreciated, ___ People of the same trade seldom meet together, even for merriment and diversion, but the conversation ends in a conspiracy against the public -- Adam Smith -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/1406559412.20573.1@Kingston2
Re: Automatic upgrades stalls on the last kernel release
On Mon, 28 Jul 2014, Paul Lewis wrote: 'cannot copy extracted data for '.lib/modules/3.2.0-4amd64/kernel/ drivers/net/wireless/rt2x00/rt61pci.ko' to '/lib/modules/3.2.0-4-amd64/ kernel/drivers/net/wireless/rt2x00/rt61pci.ko.dpkg-new'. 1. I'm wondering if it's a disk space issue. Or lack of free inodes issue. Run df -i to check. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140728144856.ga9...@khazad-dum.debian.net
Re: Automatic upgrades stalls on the last kernel release
On Mon, 28 Jul 2014 15:56:52 +0100 Paul Lewis apfle...@gmail.com wrote: I seem to have a problem with automatic updates on my system. The AU system has been unable to function normally for some time and I now have something like 61 updates waiting in the queue. When I try to process the updates, it seems to choke on the Linux 3.2 for 64 bit PCs entry, which is linux-image-3.2.0-4-amd64-3.2.60-1 +deb7u1 (64bit) reported as 23.4MBs. The error is Failed to process request. and more details are - 'cannot copy extracted data for '.lib/modules/3.2.0-4amd64/kernel/ drivers/net/wireless/rt2x00/rt61pci.ko' to '/lib/modules/3.2.0-4-amd64/ kernel/drivers/net/wireless/rt2x00/rt61pci.ko.dpkg-new'. If I manually copy the file and rerun the update, it just produces a similar error message with a different file name. df returns the following; test:# df Filesystem 1K-blocksUsed Available Use% Mounted on rootfs329233 270345 41890 87% / udev 10240 0 10240 0% /dev tmpfs 4060201892404128 1% /run /dev/mapper/test-root329233 270345 41890 87% / tmpfs 5120 4 5116 1% /run/lock tmpfs 812020 148811872 1% /run/shm /dev/sdb1 233191 18789201961 9% /boot /dev/mapper/test-home 39502452 5852096 31643728 16% /home /dev/mapper/test-tmp 376807 10303347048 3% /tmp /dev/mapper/test-usr8647944 4809964 3398684 59% /usr /dev/mapper/test-var2882592 971236 1764924 36% /var test# 1. I'm wondering if it's a disk space issue. Almost certainly. Kernels aren't that big, but the /lib/modules/* that match them are now 100MB-ish. When you install a new kernel, you need that space, but an upgrade of the same kernel release should work in less. Can I purge all the update queue and try to update the kernel on its own then the remaining updates. You have run out of space for something kernel-sized. Do you have an old kernel you can get rid of? 270MB on / with separate /var and /usr looks like two kernels-worth. I've run into this one on my server, and will have to reorganise disc space before the next upgrade. 300MB used to be more than enough for /, but isn't now. I keep a spare kernel, and will have to lose it before I upgrade to another release, though that shouldn't be a problem as I think I would have seen any problems with the running kernel by now. Also, a separate /usr, which has been routine until recently, is now a bad idea, as some of it may be needed at boot time. Not yet a show-stopper, but one day it will be. From your kernel, you are presumably running stable, and the next stable will use systemd, with a lot of re-jigged software. You can nudge things around a bit without too much trouble on LVM to get some more space on / (but it still isn't quite a trivial job, depending on physical location and whether there is unused space or you have to shrink something else). In the very long term, you will need to merge / and /usr, but the trouble is that /usr must be put into /, not the other way round, so there's a fair bit of messing about involved if you need to minimise downtime. You can't pull /lib/modules out into another partition, as that is very definitely required at boot time. If you don't have an old kernel in there, you're looking at some LVM shifting, and if your drive is four or five years old, it might be time to consider replacement, which makes things much easier. My main workstation drive is now five years old, and I'm waiting for its replacement to arrive. I'll probably also replace the server drive when I need to upgrade stable on that. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140728191458.010da...@jretrading.com
