apt-get upgrade completly blocked

[ChristopheDupriez]

I have the following messages after
apt-get update
apt-get upgrade
and tried many solutions found here and there: nothing works, always the same issue.
I would be very happy if someone is able to help me !

Code: Select all

root@akuino1:/# apt-get upgrade
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances       
Lecture des informations d'état... Fait
Calcul de la mise à jour... Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
  libegl1-mesa-drivers libopenvg1-mesa libwayland-egl1-mesa
Veuillez utiliser « apt-get autoremove » pour les supprimer.
Fait
Les paquets suivants ont été conservés :
  libgl1-mesa-dri xserver-xorg-core xserver-xorg-input-evdev
  xserver-xorg-input-synaptics xserver-xorg-video-fbdev
Les paquets suivants seront mis à jour :
  apt-transport-https apt-utils ca-certificates cpio curl file fuse iceweasel
  krb5-locales libapt-inst1.5 libcurl3 libcurl3-gnutls libdrm-freedreno1
  libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libegl1-mesa-drivers
  libfm-data libfm-extra4 libfm-gtk-data libfm-gtk4 libfm-modules libfm4
  libfuse2 libgbm1 libgcrypt20 libgl1-mesa-glx libglapi-mesa libgraphite2-3
  libgssapi-krb5-2 libgudev-1.0-0 libk5crypto3 libkrb5-3 libkrb5support0
  libmagic1 libpam-modules libpam-modules-bin libpam-runtime libpam0g libpq5
  libraspberrypi-bin libraspberrypi-dev libraspberrypi-doc libraspberrypi0
  libtiff5 libvdpau1 libwayland-egl1-mesa locales multiarch-support passwd
  pcmanfm raspberrypi-bootloader raspi-config rsyslog tzdata xserver-common
57 mis à jour, 0 nouvellement installés, 0 à enlever et 5 non mis à jour.
1 partiellement installés ou enlevés.
Il est nécessaire de prendre 0 o/117 Mo dans les archives.
Après cette opération, 8.521 ko d'espace disque seront libérés.
Souhaitez-vous continuer ? [O/n] 
Extraction des modèles depuis les paquets : 100%
Préconfiguration des paquets...
Paramétrage de udev (215-17+deb8u3) ...
update-initramfs: deferring update (trigger activated)
/sbin/insserv: 1: /sbin/insserv: Syntax error: word unexpected (expecting ")")
update-rc.d: error: insserv rejected the script header
dpkg: erreur de traitement du paquet udev (--configure) :
 le sous-processus script post-installation installé a retourné une erreur de sortie d'état 2
Traitement des actions différées (« triggers ») pour initramfs-tools (0.120) ...
Des erreurs ont été rencontrées pendant l'exécution :
 udev
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@akuino1:/# 

[GTR2Fan]

Is this a new install of Raspbian? Have you expanded the filesystem to use your entire SD card?

[ChristopheDupriez]

I should have mentionned this. Yes but I created a "/home" partition for data too:

Code: Select all

root@akuino1:/# df
Sys. de fichiers blocs de 1K Utilisé Disponible Uti% Monté sur
/dev/root            3937492 2255216    1494408  61% /
devtmpfs              469760       0     469760   0% /dev
tmpfs                 474076       0     474076   0% /dev/shm
tmpfs                 474076    6512     467564   2% /run
tmpfs                   5120       4       5116   1% /run/lock
tmpfs                 474076       0     474076   0% /sys/fs/cgroup
/dev/mmcblk0p1         61384   20248      41136  33% /boot
/dev/mmcblk0p5       3561892   60764    3316860   2% /home
tmpfs                  94816       4      94812   1% /run/user/1000
root@akuino1:/# 

[buja]

Add up the percentages under Uti% (you don't need a calculator) and you will see what the problem is.
Which leads to GTR2Fan's question again (and the answer is probably no).

[rpdom]

Add up the percentages under Uti% (you don't need a calculator)

What is that supposed to show? That the percentages just happen to add up to 100%?

From that report, I can see that the root file system is 61% full with plenty of space. So that isn't the problem.

Maybe a bad card?

[stderr]

I have the following messages after
apt-get update
apt-get upgrade
and tried many solutions found here and there: nothing works, always the same issue.

Always the same issue with the same card and the same burn of the OS image file? It isn't actually bad that when you do exactly the same things, you get exactly the same results. I would find another sdcard, put the latest version of the OS on it and try again. This will immediately give you a strong indication of where to look further with this card/OS instance.

[ChristopheDupriez]

Searching Internet, it seems to be issues when upgrading initramfs-tools. As suggested, I will have a try with another card but not exactly the same setup...

If it is the SD card (recent Kingston 8Gb from a reputed source), it means RPi is no good for Real Time data collection even using RRD and 10 seconds intervals in sensors polling... Hard to believe for me but may be I should then hack a NAS rather than a Pi...

[ChristopheDupriez]

There are files corrupted on the SD card.

Thanks for pointing this issue.

For me, it makes the "basic Pi" rather unsuitable for sensor data storage as the SD when corrupt after only two months of service !

[fruitoftheloom]

There are files corrupted on the SD card.

Thanks for pointing this issue.

For me, it makes the "basic Pi" rather unsuitable for sensor data storage as the SD when corrupt after only two months of service !

Many users boot up the RPi on the SD Card, but Raspbian is launched on a USB Drive, this solves SD Card corruption as all Flash Media has a read/write life..

[GTR2Fan]

Many users boot up the RPi on the SD Card, but Raspbian is launched on a USB Drive, this solves SD Card corruption as all Flash Media has a read/write life..

Hopefully you're not talking about USB memory sticks when using the term 'USB Drive'.

That limited read/write life applies just as much to USB memory drives as it does to microSD cards unless one supports wear-levelling and the other one doesn't, and buying a decent microSD card in the first place is usually no more expensive than investing in cheap examples of both. In over 3 years of running one Pi or another nearly 24/7 (so probably around 25,000 hours of uptime in total) with the OS on a decent microSD card, the total failure/corruption rate here has been zero. I find it hard to believe that that's just down to luck.

[kusti8]

I use a read only SD card so it will always startup. Any data can go into a USB stick, so the data may be corrupt, but the Pi will always boot. That's the best way.

[fruitoftheloom]

Many users boot up the RPi on the SD Card, but Raspbian is launched on a USB Drive, this solves SD Card corruption as all Flash Media has a read/write life..

Hopefully you're not talking about USB memory sticks when using the term 'USB Drive'.

I would of said Flash Drive or Flash Media but yes should of stated USB 2.5" Hard Disk Drive