Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Updating error on Debian 7.11 (wheezy)

Ask for help with issues regarding the Installations of the Debian O/S.
Post Reply
Message
Author
G33RT
Posts: 9
Joined: 2018-01-25 23:20
Location: Belgium

Updating error on Debian 7.11 (wheezy)

#1 Post by G33RT »

Hi to all,

I alsways receive an error message when I try to upgrade Debian 7.11 (wheezy).

Code: Select all

root@server:~# lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 7.11 (wheezy)
Release:        7.11
Codename:       wheezy
root@server:~#

These commands where used:

Code: Select all

apt-get update
apt-get upgrade
This is the output before the error occurs:

Code: Select all

Fetched 53.9 MB in 7s (6,990 kB/s)
Reading changelogs... Done
Extracting templates from packages: 100%
Preconfiguring packages ...
Setting up sensible-utils (0.0.7+deb7u1) ...
(Reading database ... 39591 files and directories currently installed.)
Preparing to replace linux-image-3.2.0-4-amd64 3.2.82-1 (using .../linux-image-3.2.0-4-amd64_3.2.96-2_amd64.deb) ...
Unpacking replacement linux-image-3.2.0-4-amd64 ...
dpkg: error processing /var/cache/apt/archives/linux-image-3.2.0-4-amd64_3.2.96-2_amd64.deb (--unpack):
 cannot copy extracted data for './lib/modules/3.2.0-4-amd64/kernel/drivers/hwmon/pc87360.ko' to '/lib/modules/3.2.0-4-amd64/kernel/drivers/hwmon/pc87360.ko.dpkg-new': failed to write (No space left on device)
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-4-amd64 /boot/vmlinuz-3.2.0-4-amd64
Preparing to replace multiarch-support 2.13-38+deb7u11 (using .../multiarch-support_2.13-38+deb7u12_amd64.deb) ...
Unpacking replacement multiarch-support ...
Errors were encountered while processing:
 /var/cache/apt/archives/linux-image-3.2.0-4-amd64_3.2.96-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@server:~#
Seems like complaing about available space.
The OS is installed on a small 16gb SSD and mabe I can resize a partition (need advice on this one).

This is my usage and free space:

Code: Select all

root@server:~# fdisk -l

Disk /dev/sda: 16.0 GB, 16013942784 bytes
255 heads, 63 sectors/track, 1946 cylinders, total 31277232 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006bc6f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      684031      340992   83  Linux
/dev/sda2          686078    31277055    15295489    5  Extended
/dev/sda5          686080    11765759     5539840   83  Linux
/dev/sda6        11767808    17088511     2660352   83  Linux
/dev/sda7        17090560    18853887      881664   82  Linux swap / Solaris
/dev/sda8        18855936    19634175      389120   83  Linux
/dev/sda9        19636224    31277055     5820416   83  Linux
root@server:~#

Code: Select all

root@server:~# df -h
Filesystem                                              Size  Used Avail Use% Mounted on
rootfs                                                  323M  238M   69M  78% /
udev                                                     10M     0   10M   0% /dev
tmpfs                                                   395M  288K  395M   1% /run
/dev/disk/by-uuid/bf584f21-fe6b-4281-a3ee-35252d7b733c  323M  238M   69M  78% /
tmpfs                                                   5.0M     0  5.0M   0% /run/lock
tmpfs                                                   963M     0  963M   0% /run/shm
/dev/sda9                                               5.5G  140M  5.1G   3% /home
/dev/sda8                                               368M   11M  339M   3% /tmp
/dev/sda5                                               5.3G  968M  4.0G  20% /usr
/dev/sda6                                               2.5G  489M  1.9G  21% /var
root@server:~#
Does someone knows how to fix this problem?
Last edited by G33RT on 2018-01-28 19:58, edited 1 time in total.
Best regards, Geert

User avatar
stevepusser
Posts: 12930
Joined: 2009-10-06 05:53
Has thanked: 41 times
Been thanked: 71 times

Re: Updating error on Debian 7.11 (wheezy)

#2 Post by stevepusser »

Try

Code: Select all

apt-get clean
to clean out the package cache. This means that you will need to redownload the kernel update packages. Since you have a tiny rootfs, you may need to clean it out between upgrades of large packages like the kernel.
MX Linux packager and developer

G33RT
Posts: 9
Joined: 2018-01-25 23:20
Location: Belgium

Re: Updating error on Debian 7.11 (wheezy)

#3 Post by G33RT »

Hi,

I already did apt-get clean but this makes no difference.

Any other thoughts?
Mabe resizing the rootfs would help?
Best regards, Geert

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Updating error on Debian 7.11 (wheezy)

#4 Post by debiman »

G33RT wrote:

Code: Select all

cannot copy extracted data for './lib/modules/3.2.0-4-amd64/kernel/drivers/hwmon/pc87360.ko' to '/lib/modules/3.2.0-4-amd64/kernel/drivers/hwmon/pc87360.ko.dpkg-new': failed to write (No space left on device)

G33RT
Posts: 9
Joined: 2018-01-25 23:20
Location: Belgium

Re: Updating error on Debian 7.11 (wheezy)

#5 Post by G33RT »

Can someone advice me which partition to resize to expand the root ?
Gparted don't let me resize as they all are locked.

Code: Select all

sudo fdisk -l -u

Disk /dev/sda: 16.0 GB, 16013942784 bytes
255 heads, 63 sectors/track, 1946 cylinders, total 31277232 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0006bc6f

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048      684031      340992   83  Linux
/dev/sda2          686078    31277055    15295489    5  Extended
/dev/sda5          686080    11765759     5539840   83  Linux
/dev/sda6        11767808    17088511     2660352   83  Linux
/dev/sda7        17090560    18853887      881664   82  Linux swap / Solaris
/dev/sda8        18855936    19634175      389120   83  Linux
/dev/sda9        19636224    31277055     5820416   83  Linux

Code: Select all

sudo parted /dev/sda unit s print

Model: ATA KingSpec KSD-SA1 (scsi)
Disk /dev/sda: 31277232s
Sector size (logical/physical): 512B/512B
Partition Table: msdos

Number  Start      End        Size       Type      File system     Flags
 1      2048s      684031s    681984s    primary   ext4            boot
 2      686078s    31277055s  30590978s  extended
 5      686080s    11765759s  11079680s  logical   ext4
 6      11767808s  17088511s  5320704s   logical   ext4
 7      17090560s  18853887s  1763328s   logical   linux-swap(v1)
 8      18855936s  19634175s  778240s    logical   ext4
 9      19636224s  31277055s  11640832s  logical   ext4
Would it possible to shrink sda5 about 500mb and expand sda1 with 500mb ?
Any help is welcome ;-)
Best regards, Geert

User avatar
Thorny
Posts: 542
Joined: 2011-02-27 13:40

Re: Updating error on Debian 7.11 (wheezy)

#6 Post by Thorny »

G33RT wrote:Any help is welcome ;-)
Possible, yes.
Is it difficult and dangerous and are you likely to make a mistake and mess your system up, yes.

I hope you have everything you consider mission-critical important backed up.

You wouldn't be able to do this while those partitions are mounted.

This would be a very risky procedure to try for a release that reaches end of life in four months. Wheezy support ends at the end of May.

If I was in your situation, I would boot up a live disk and copy my /home directory somewhere
so I was sure I had a current copy of my /home.

Then install a release that will be supported for longer than four months and copy your /home to it. In the case of Debian stable that would be Jessie or Stretch. A simpler partition scheme would probably be a good idea, perhaps just a separate /home and swap if this is your desktop system. Or maybe on such a small drive, not even a separate /home but you still could fill that up and not be able to boot unless you were careful.

Maybe someone would be willing to try to walk you through it step by step with parted or gparted from a live disk, I am not, it would be a lot harder than reinstalling and a mistake could mean you had to install anyway. This might be marginally easier with a GUI, gparted, while you had a live system booted up but it would still be risky.

Good luck.

[edit] I looked back over the thread. I see you tried clean but how many old kernels do you have, have you tried

Code: Select all

apt-get autoremove 
to clear out some old, no longer needed files?

User avatar
dotlj
Posts: 646
Joined: 2009-12-25 17:21

Re: Updating error on Debian 7.11 (wheezy)

#7 Post by dotlj »

Can someone advice me which partition to resize to expand the root ?
Gparted don't let me resize as they all are locked.

Code: Select all

cat /etc/fstab  
will show what is mounted where, it may include UUIDs but should show what device partition has /

User avatar
Thorny
Posts: 542
Joined: 2011-02-27 13:40

Re: Updating error on Debian 7.11 (wheezy)

#8 Post by Thorny »

dotlj wrote:...will show what is mounted where, it may include UUIDs but should show what device partition has /
@ dotlj It looks like you are volunteering to walk G33RT through this, that is good of you, so.

It is not my business to answer for the G33RT so I should probably shut up but there is a df -h listing in the OP.

In order to take space from 5 in the extended partition it would be necessary to slide what is currently in 5, /usr down and then move the space out of the extended and add it to 1.

G33RT
Posts: 9
Joined: 2018-01-25 23:20
Location: Belgium

Re: Updating error on Debian 7.11 (wheezy)

#9 Post by G33RT »

dotlj wrote:
Can someone advice me which partition to resize to expand the root ?
Gparted don't let me resize as they all are locked.

Code: Select all

cat /etc/fstab  

will show what is mounted where, it may include UUIDs but should show what device partition has /
Hi dotlj,
This is the output you asked me:

Code: Select all

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/sda1 during installation
UUID=bf584f21-fe6b-4281-a3ee-35252d7b733c /               ext4    errors=remount-ro 0       1
# /home was on /dev/sda9 during installation
UUID=f73ffc47-d715-415e-961a-1614908f13c4 /home           ext4    defaults        0       2
# /tmp was on /dev/sda8 during installation
UUID=1800ecb2-4167-42e9-9831-22d084234764 /tmp            ext4    defaults        0       2
# /usr was on /dev/sda5 during installation
UUID=d24e73c1-11ed-4beb-a9a9-91b55e669172 /usr            ext4    defaults        0       2
# /var was on /dev/sda6 during installation
UUID=cefd42c3-637d-4c2b-9bcb-5935f514659a /var            ext4    defaults        0       2
# swap was on /dev/sda7 during installation
UUID=cd5bf38a-af01-4158-bca2-7b17135005f5 none            swap    sw              0       0
/dev/sr0        /media/cdrom0   udf,iso9660 user,noauto     0       0
Best regards, Geert

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Updating error on Debian 7.11 (wheezy)

#10 Post by debiman »

G33RT wrote:

Code: Select all

# / was on /dev/sda1 during installation
UUID=bf584f21-fe6b-4281-a3ee-35252d7b733c /               ext4    errors=remount-ro 0       1

G33RT
Posts: 9
Joined: 2018-01-25 23:20
Location: Belgium

Re: Updating error on Debian 7.11 (wheezy)

#11 Post by G33RT »

debiman wrote:
G33RT wrote:

Code: Select all

# / was on /dev/sda1 during installation
UUID=bf584f21-fe6b-4281-a3ee-35252d7b733c /               ext4    errors=remount-ro 0       1
Why did you quote this, can you explain a little more please?
Best regards, Geert

steve_v
df -h | grep > 20TiB
df -h | grep > 20TiB
Posts: 1400
Joined: 2012-10-06 05:31
Location: /dev/chair
Has thanked: 79 times
Been thanked: 175 times

Re: Updating error on Debian 7.11 (wheezy)

#12 Post by steve_v »

G33RT wrote:

Code: Select all

/dev/disk/by-uuid/bf584f21-fe6b-4281-a3ee-35252d7b733c  323M  238M   69M  78% /
Wait, your root partition is 320 Megabytes. Really? Is this some kind of embedded system?
Such a minuscule root partiton is going to cause you no end of pain.

With the current price of SSDs, I suggest you seriously consider a bigger disk.
Otherwise, fire up a livecd (gparted live or partedmagic) and resize that partition. I'd suggest 1GB as a bare minimum. Back up your stuff first.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

User avatar
debiman
Posts: 3063
Joined: 2013-03-12 07:18

Re: Updating error on Debian 7.11 (wheezy)

#13 Post by debiman »

G33RT wrote:
debiman wrote:
G33RT wrote:

Code: Select all

# / was on /dev/sda1 during installation
UUID=bf584f21-fe6b-4281-a3ee-35252d7b733c /               ext4    errors=remount-ro 0       1
Why did you quote this, can you explain a little more please?
it is the answer to your question:
G33RT wrote:Can someone advice me which partition to resize to expand the root ?

G33RT
Posts: 9
Joined: 2018-01-25 23:20
Location: Belgium

Re: Updating error on Debian 7.11 (wheezy)

#14 Post by G33RT »

steve_v wrote:
G33RT wrote:

Code: Select all

/dev/disk/by-uuid/bf584f21-fe6b-4281-a3ee-35252d7b733c  323M  238M   69M  78% /
Wait, your root partition is 320 Megabytes. Really? Is this some kind of embedded system?
Such a minuscule root partiton is going to cause you no end of pain.

With the current price of SSDs, I suggest you seriously consider a bigger disk.
Otherwise, fire up a livecd (gparted live or partedmagic) and resize that partition. I'd suggest 1GB as a bare minimum. Back up your stuff first.
No it's not an embedded system, It is running on a Atom CPU (mini-ITX)
Yesterday I ordered a 64gb SSD for just 21.60 Euro's :-)

So what's the best thing to do now, making a copy with Clonezilla Live CD and than restore to the new SSD?
Would it also be possible to create induvidual partitions boot/usr/home/ etc, ect... and extract each partition to it?

This way I can create each partition size as I like, would love to hear some recommendations to this.
Best regards, Geert

steve_v
df -h | grep > 20TiB
df -h | grep > 20TiB
Posts: 1400
Joined: 2012-10-06 05:31
Location: /dev/chair
Has thanked: 79 times
Been thanked: 175 times

Re: Updating error on Debian 7.11 (wheezy)

#15 Post by steve_v »

The easiest option is probably a full-disk backup / restore with clonezilla, followed by rearranging the partitions with gparted.
Alternatively, install (a current Debian release?) fresh and copy any important data over from the old drive.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

User avatar
dotlj
Posts: 646
Joined: 2009-12-25 17:21

Re: Updating error on Debian 7.11 (wheezy)

#16 Post by dotlj »

For an Atom processor, 16 GB is probably enough. I've seen a number of firewalls with Intel 64 bit processors running on 16GB SSDs with most of it used as cache.
Ordering a 64GB SSD will give you a lot more space.
I have a 500GB SSD and root is taking 5.2GB.

I'm not quite certain about your /boot partition, it seems to be part of /.
From the size of the partitions
sda9 5.5GB /home
sda8 365MB /tmp
sda7 ?MB swap
sda6 2.5GB /var
sda5 5.3GB /usr
sda1 ?GB /

Before resizing I'd like to be clear about how much free space and if /dev/sda2 is required or can be reclaimed.

/ can't be very big and the error seems to be not enough space. I suggest checking how many images you have installed

Code: Select all

ls -l /boot/
Usually you can keep two or three but you don't have enough space, so if you have more than two, apt-get remove the linux-image of the oldest installed kernel to make space for the update.
If you can reclaim /dev/sda2 to increase /, then you can do that. From my experience, partitioning a small disk is more likely to lead to this sort of disk space problem.

An easier way would probably be to backup your data, do a fresh install on the 64GB disk, think carefully about the partitioning before you do the installation, then restore your data.
Try Debian Stretch.

steve_v
df -h | grep > 20TiB
df -h | grep > 20TiB
Posts: 1400
Joined: 2012-10-06 05:31
Location: /dev/chair
Has thanked: 79 times
Been thanked: 175 times

Re: Updating error on Debian 7.11 (wheezy)

#17 Post by steve_v »

I suggest forgetting about the separate partitions for /usr /var /tmp etc. Perhaps keep /home on it's own partition for ease of upgrading, but the rest just make life difficult - it's a lot easier to move files about than resize partitions when you discover your initial space guestimates were incorrect.
I'm not sure a separate /usr is even officially supported these days, and I can't see a valid reason for it unless you're booting from floppy disks.
Once is happenstance. Twice is coincidence. Three times is enemy action. Four times is Official GNOME Policy.

User avatar
dotlj
Posts: 646
Joined: 2009-12-25 17:21

Re: Updating error on Debian 7.11 (wheezy)

#18 Post by dotlj »

steve_v wrote:I suggest forgetting about the separate partitions for /usr /var /tmp etc. Perhaps keep /home on it's own partition for ease of upgrading, but the rest just make life difficult - it's a lot easier to move files about than resize partitions when you discover your initial space guestimates were incorrect.
I'm not sure a separate /usr is even officially supported these days, and I can't see a valid reason for it unless you're booting from floppy disks.
Agree 100%. You can get away with that if your disk is big, but with 16GB, you don't really have much free space on any partition.

Post Reply