Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 22/11/2024, à 18:30

Fraise c’est moi aussi

Redémarrage impossible no recovery

/dev/num01p2: clean, 489347/62480384 files, 249298443/249919744 blocks

Bonjour, jusqu’à hier tout allait bien et après avoir voulu redémarrer mon lenovo  sous Ubuntu 22.04.3 ( je crois) écran avec ce message. En recovery, soit une liste interminable qui défile, soit une liste interminable qui ne défile pas, soit un message que je n’ai pas eu le temps de voir suivi d’une longue liste de GRUB juste eu le temps de voir failed to start gnome display manager  à l’un des reallumage.Pas de menu pour redémarrer . De l’aide serai bienvenue. Je n’ai aucune action sur les touches. Frede

Hors ligne

#2 Le 22/11/2024, à 18:45

geole

Re : Redémarrage impossible no recovery

Bonjour.

Le message que tu signales indique que la partition  est en excellent état.

Pourrais-tu booter avec le support d'installation ( live-usb)
Choisir "essayer ubuntu avant de l'installer"
Installer et lancer  boot-info
Publier l'URL qu'il aura générée.


As-tu essayé de booter avec un ancien noyau? Eventuellement en recovery.

Dernière modification par geole (Le 22/11/2024, à 23:06)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#3 Le 22/11/2024, à 18:54

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Hello.je n’ai pas de proposition de reboot en recovery. Et pas de clef d’installation. Tu suggères que je télécharge Ubuntu sur une clef et que j’essaie de lancer ?

Hors ligne

#4 Le 22/11/2024, à 20:16

geole

Re : Redémarrage impossible no recovery

Tu avais pourtant dit que tu avais fait du recovery.
( En recovery, soit une liste interminable )


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#5 Le 22/11/2024, à 22:19

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Oui, j’ai rallumé et maintenu soit esc soit maj, et j’ai eu ces listes, mais aucun écran avec les propositions de boot avec les anciens noyaux. Le mode recovery n’a pas fonctionné

Hors ligne

#6 Le 23/11/2024, à 13:30

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Toujours pas avancé sur le problème. Je n’obtiens pas de menu de récup, et selon  les tentatives, parfois ces listes, parfois la ligne citée plus haut, parfois la même ligne augmentée

 /dev/num01p2: clean, 489347/62480384 files, 249298443/249919744 blocks                                              [   2.034210] ov8856 i2c-OVTI8856:00: failed to get HW configuration: -22

je n’ai rien de mieux, et les touches ne sont pas actives.   Qu’est-ce que c’est ce binz?

Hors ligne

#7 Le 23/11/2024, à 14:27

geole

Re : Redémarrage impossible no recovery

Bonjour
Avec un autre ordinateur, fabrique un support d’installation et fait le boot-info. On pourra peut-être y voir des anomalies.
Au pire, cela te permettra de réinstaller.


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#8 Le 23/11/2024, à 15:02

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Ok, je vais chercher ça ( pas d’ordi en état de marche sous la main) merci merci

Hors ligne

#9 Le 27/11/2024, à 20:19

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Juste pour être sûre. Si j’ai ma clef bootable, Ubuntu 24.04, et je la lance, est-ce que cela ne va pas tout dégager? Je vois qu’a partir de 24.04, l’option de formatage est automatique?

Hors ligne

#10 Le 27/11/2024, à 20:46

geole

Re : Redémarrage impossible no recovery

Bonjour.
Pour l'instant, l'important est de faire un boot-info.
Tu pourras ajouter la sauvegarde de tes données.
Il faut d'abord décider de réinstaller dans une partition pour que les données de cette partition soient détruites.

Dernière modification par geole (Le 27/11/2024, à 20:48)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#11 Le 27/11/2024, à 22:38

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Bon ben ça se complique. Pas moyen d’accéder au forum depuis l’ordinateur. Je suis avec le téléphone, je n’ai aucune idée de ce que je peux faire. La page de connexion refuse d’admettre mon nom et mot de passe, changé 2 fois au cas où mais rien à faire. Je ne sais pas comment transmettre l’info du boot.

Hors ligne

#12 Le 27/11/2024, à 22:46

geole

Re : Redémarrage impossible no recovery

Vérifie que l'ordinateur ne cause pas qwerty au lieu de azerty en frappant le caractère a dans une zone lisible.

Dernière modification par geole (Le 27/11/2024, à 22:47)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#13 Le 27/11/2024, à 23:12

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Non, le problème n’est pas là, j’ai vérifié plusieurs fois je suis en QWERTY, ça c’est ok… sinon en relançant la commande du boot- info cette fois ci j’ai obtenu la possibilité de partager en ligne et  l‘lURL du rapport: https://paste.ubuntu.com/p/Hdr/7PcRkWg/

Hors ligne

#14 Le 27/11/2024, à 23:44

nany

Re : Redémarrage impossible no recovery

Bonjour,



Fraise c’est moi aussi a écrit :

et  l‘lURL du rapport: https://paste.ubuntu.com/p/Hdr/7PcRkWg/

L’URL exacte serait plutôt https://paste.ubuntu.com/p/Hdr7PcRkWg/.
Et comme la durée de vie sur paste.ubuntu.com est limitée, je colle ici le contenu du rapport pour la pérennité :

boot-info-4ppa2081                                              [20241127_2047]

============================== Boot Info Summary ===============================

 => No boot loader is installed in the MBR of /dev/nvme0n1.

nvme0n1p1: _____________________________________________________________________

    File system:       vfat
    Boot sector type:  FAT32
    Boot sector info:  No errors found in the Boot Parameter Block.
    Operating System:  
    Boot files:        /efi/BOOT/fbx64.efi /efi/BOOT/mmx64.efi 
                       /efi/ubuntu/grubx64.efi /efi/ubuntu/mmx64.efi 
                       /efi/ubuntu/shimx64.efi /efi/ubuntu/grub.cfg

nvme0n1p2: _____________________________________________________________________

    File system:       ext4
    Boot sector type:  -
    Boot sector info: 
    Operating System:  Ubuntu 22.04.5 LTS
    Boot files:        /boot/grub/grub.cfg /etc/fstab /etc/default/grub

sda: ___________________________________________________________________________

    File system:       iso9660
    Boot sector type:  Grub2 (v1.99-2.00)
    Boot sector info:  Grub2 (v1.99-2.00) is installed in the boot sector of 
                       sda and looks at sector 0 of the same hard drive for 
                       core.img, but core.img can not be found at this 
                       location.
    Mounting failed:   mount: /mnt/BootInfo/FD/sda: /dev/sda already mounted or mount point busy.
       dmesg(1) may have more information after failed mount system call.


================================ 1 OS detected =================================

OS#1 (linux):   Ubuntu 22.04.5 LTS on nvme0n1p2

================================ Host/Hardware =================================

CPU architecture: 64-bit
Video: Iris Plus Graphics G1 (Ice Lake) simpledrmdrmfb from Intel Corporation
Live-session OS is Ubuntu 64-bit (Ubuntu 24.04.1 LTS, noble, x86_64)

===================================== UEFI =====================================

BIOS/UEFI firmware: CUCN19WW(V1.08)(1.19) from LENOVO
The firmware is EFI-compatible, and is set in EFI-mode for this live-session.
SecureBoot disabled (confirmed by mokutil).
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0001,0000,2001,2002,2003
Boot0000* Linpus lite	HD(2,GPT,eed3de8a-acd3-4541-ba17-9014c007d874,0xb8b5a0,0x27a0)/File(\EFI\Boot\grubx64.efi)RC
Boot0001* ubuntu	HD(1,GPT,028caff2-e6d5-47c0-864e-c6a00c380971,0x800,0x100000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* EFI USB Device (TSSTcorpCDDVDW SE-208GB)	PciRoot(0x0)/Pci(0x14,0x0)/USB(0,0)/CDROM(1,0x5a8,0xb40)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot2003* EFI Network	RC

1d43d986c265d8c455d020e4a1f28c52   nvme0n1p1/BOOT/fbx64.efi
1d260ff1255f189ab621209796ee2fed   nvme0n1p1/BOOT/mmx64.efi
a1da253696a304dce6b4668b70151c0e   nvme0n1p1/ubuntu/grubx64.efi
1d260ff1255f189ab621209796ee2fed   nvme0n1p1/ubuntu/mmx64.efi
07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/ubuntu/shimx64.efi
07e25dcaf57c776875f78fa36827c58e   nvme0n1p1/BOOT/BOOTX64.efi

============================= Drive/Partition Info =============================

Disks info: ____________________________________________________________________

nvme0n1	: is-GPT,	no-BIOSboot,	has---ESP, 	not-usb,	not-mmc, has-os,	no-wind,	2048 sectors * 512 bytes

Partitions info (1/3): _________________________________________________________

nvme0n1p1	: no-os,	64, nopakmgr,	no-docgrub,	nogrub,	nogrubinstall,	no-grubenv,	noupdategrub,	not-far
nvme0n1p2	: is-os,	64, apt-get,	signed grub-pc grub-efi ,	grub2,	grub-install,	grubenv-ok,	update-grub,	end-after-100GB

Partitions info (2/3): _________________________________________________________

nvme0n1p1	: is---ESP,	part-has-no-fstab,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, vfat
nvme0n1p2	: isnotESP,	fstab-has-goodEFI,	no-nt,	no-winload,	no-recov-nor-hid,	no-bmgr,	notwinboot, ext4

Partitions info (3/3): _________________________________________________________

nvme0n1p1	: not--sepboot,	no---boot,	part-has-no-fstab,	not-sep-usr,	no---usr,	part-has-no-fstab,	no--grub.d,	nvme0n1
nvme0n1p2	: not--sepboot,	with-boot,	fstab-without-boot,	not-sep-usr,	with--usr,	fstab-without-usr,	std-grub.d,	nvme0n1

fdisk -l (filtered): ___________________________________________________________

Disk nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk identifier: 0C1EC5C0-9162-4B6D-B67C-93D933FF88ED
           Start        End    Sectors   Size Type
nvme0n1p1    2048    1050623    1048576   512M EFI System
nvme0n1p2 1050624 2000408575 1999357952 953.4G Linux filesystem
Disk sda: 14.32 GiB, 15376318464 bytes, 30031872 sectors
Disk identifier: EED3DE8A-ACD3-4541-BA15-9014C007D874
        Start      End  Sectors  Size Type
sda1        64 12105119 12105056  5.8G Microsoft basic data
sda2  12105120 12115263    10144    5M EFI System
sda3  12115264 12115863      600  300K Microsoft basic data
sda4  12115968 30029823 17913856  8.5G Linux filesystem

parted -lm (filtered): _________________________________________________________

sda:15.4GB:scsi:512:512:gpt:SanDisk Cruzer Blade:;
1:32.8kB:6198MB:6198MB::ISO9660:hidden, msftdata;
2:6198MB:6203MB:5194kB::Appended2:boot, esp;
3:6203MB:6203MB:307kB::Gap1:hidden, msftdata;
4:6203MB:15.4GB:9172MB:ext4::;
nvme0n1:1024GB:nvme:512:512:gpt:SAMSUNG MZVLB1T0HBLR-000L2:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
2:538MB:1024GB:1024GB:ext4::;

blkid (filtered): ______________________________________________________________

NAME        FSTYPE   UUID                                 PARTUUID                             LABEL                    PARTLABEL
sda         iso9660  2024-08-27-16-23-26-00                                                    Ubuntu 24.04.1 LTS amd64 
├─sda1      iso9660  2024-08-27-16-23-26-00               eed3de8a-acd3-4541-ba14-9014c007d874 Ubuntu 24.04.1 LTS amd64 ISO9660
├─sda2      vfat     3C53-CAEB                            eed3de8a-acd3-4541-ba17-9014c007d874 ESP                      Appended2
├─sda3                                                    eed3de8a-acd3-4541-ba16-9014c007d874                          Gap1
└─sda4      ext4     e5a9564c-06d7-4e2f-a5bb-dd60ac38b497 bc02f5cf-b64f-4715-9aa6-0a3890dea7ac writable                 
nvme0n1                                                                                                                 
├─nvme0n1p1 vfat     698F-30EC                            028caff2-e6d5-47c0-864e-c6a00c380971                          EFI System Partition
└─nvme0n1p2 ext4     1c9be0a4-9f69-4913-a0b6-4ecfa51f214c a38548c7-61da-4071-9aa2-92e6bb785603                          

Mount points (filtered): _______________________________________________________

                                                               Avail Use% Mounted on
/dev/nvme0n1p1                                                504.9M   1% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p2                                                     0 100% /mnt/boot-sav/nvme0n1p2
/dev/sda1                                                          0 100% /cdrom
efivarfs                                                         18K  87% /sys/firmware/efi/efivars

Mount options (filtered): ______________________________________________________

/dev/nvme0n1p1                                                vfat            rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro
/dev/nvme0n1p2                                                ext4            rw,relatime
/dev/sda1                                                     iso9660         ro,noatime,nojoliet,check=s,map=n,blocksize=2048,iocharset=utf8

=================== nvme0n1p1/efi/ubuntu/grub.cfg (filtered) ===================

search.fs_uuid 1c9be0a4-9f69-4913-a0b6-4ecfa51f214c root 
set prefix=($root)'/boot/grub'
configfile $prefix/grub.cfg

=================== nvme0n1p2/boot/grub/grub.cfg (filtered) ====================

Ubuntu   1c9be0a4-9f69-4913-a0b6-4ecfa51f214c
### END /etc/grub.d/30_os-prober ###
UEFI Firmware Settings   uefi-firmware
### END /etc/grub.d/30_uefi-firmware ###

======================== nvme0n1p2/etc/fstab (filtered) ========================

# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=1c9be0a4-9f69-4913-a0b6-4ecfa51f214c /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=698F-30EC  /boot/efi       vfat    umask=0077      0       1
/swapfile                                 none            swap    sw              0       0
/dev/disk/by-id/usb-_USB_DISK_2.0_0701061EAC49A597-0:0-part2 /mnt/usb-_USB_DISK_2.0_0701061EAC49A597-0:0-part2 auto nosuid,nodev,nofail,noauto,x-gvfs-show 0 0

==================== nvme0n1p2/etc/default/grub (filtered) =====================

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

================= nvme0n1p2: Location of files loaded by Grub ==================

           GiB - GB             File                                 Fragment(s)
 473.757026672 = 508.692733952  boot/grub/grub.cfg                             1
 945.711910248 = 1015.450431488 boot/vmlinuz                                   2
  62.800945282 = 67.432001536   boot/vmlinuz-5.15.0-125-generic                2
 581.163303375 = 624.019345408  boot/vmlinuz-6.8.0-48-generic                  1
 945.711910248 = 1015.450431488 boot/vmlinuz-6.8.0-49-generic                  2
  62.800945282 = 67.432001536   boot/vmlinuz.old                               2
 581.591484070 = 624.479100928  boot/initrd.img                                1
 417.312950134 = 448.086368256  boot/initrd.img-5.15.0-125-generic             1
  68.935253143 = 74.018664448   boot/initrd.img-6.8.0-48-generic               2
 581.591484070 = 624.479100928  boot/initrd.img-6.8.0-49-generic               1
 417.312950134 = 448.086368256  boot/initrd.img.old                            1

=================== nvme0n1p2: ls -l /etc/grub.d/ (filtered) ===================

-rwxr-xr-x 1 root root 18683 Dec 18  2022 10_linux
-rwxr-xr-x 1 root root 43031 Dec 18  2022 10_linux_zfs
-rwxr-xr-x 1 root root 14387 Dec 18  2022 20_linux_xen
-rwxr-xr-x 1 root root 13369 Dec 18  2022 30_os-prober
-rwxr-xr-x 1 root root  1372 Dec 18  2022 30_uefi-firmware
-rwxr-xr-x 1 root root   700 Feb 21  2022 35_fwupd
-rwxr-xr-x 1 root root   214 Apr 15  2020 40_custom
-rwxr-xr-x 1 root root   215 Dec 18  2022 41_custom



Suggested repair: ______________________________________________________________

The default repair of the Boot-Repair utility would reinstall the grub-efi of
nvme0n1p2,
using the following options:  nvme0n1p1/boot/efi
Additional repair would be performed: unhide-bootmenu-10s use-standard-efi-file

Final advice in case of suggested repair: ______________________________________

Please do not forget to make your UEFI firmware boot on the Ubuntu 22.04.5 LTS entry (nvme0n1p1/efi/****/grub****.efi (**** will be updated in the final message) file) !

On peut y voir que la patition système est remplie à 100% :

Mount points (filtered): _______________________________________________________

                                                               Avail Use% Mounted on
/dev/nvme0n1p1                                                504.9M   1% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p2                                                     0 100% /mnt/boot-sav/nvme0n1p2
/dev/sda1                                                          0 100% /cdrom
efivarfs                                                         18K  87% /sys/firmware/efi/efivars

Il faudrait donc trouver le moyen de faire du ménage dans cette partition.

Dernière modification par nany (Le 27/11/2024, à 23:45)

Hors ligne

#15 Le 28/11/2024, à 00:01

geole

Re : Redémarrage impossible no recovery

En premier, booter en mode recovery
et choisir clean.
Puis rebooter.
si cela ne suffit pas....c'est ici
Puis, plus tard, pour savoir s'il n'y a pas un problème de fonctionnement.

journalctl --no-pager -b -p err -n 400 

Dernière modification par geole (Le 28/11/2024, à 00:26)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#16 Le 28/11/2024, à 00:33

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Ok ok, je vais tenter tout ça demain. Merci beaucoup Nany et Geole!

Hors ligne

#17 Le 28/11/2024, à 00:36

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Une dernière petite question:? Si je boot depuis la clef, je peux faire le mode recovery? Parce que sans la clef, je ne peux pas y accéder. Sinon je pensais mettre sur une clef mon home pour sauvegarder et tout désinstaller et réinstaller.

Hors ligne

#18 Le 28/11/2024, à 11:02

geole

Re : Redémarrage impossible no recovery

Bonjour
Le recovery se fait obligatoirement depuis le ubuntu installé.
Sinon depuis la clé USB, l'épuration se fera avec d'autres commandes après avoir monté la partition nvme.
1) Booter avec le support d'installation.
2) Choisir "essayer avant d'installer".
3) Monter la partition racine.

sudo mount -v /dev/nvme0n1p2 /mnt

4) Publier les erreurs de la dernière session.

journalctl --no-pager -D /mnt/var/log/journal -b -p err -n 100

5) Faire un état rapide des occupations disques.

sudo du /mnt -haxd1 | sort -h | tail -15
sudo du /mnt/var -haxd2 | sort -h | tail -21
sudo du /mnt/home -haxd3 | sort -h | tail -21

6) Faire une épuration rapide des journaux en double.

 sudo rm -v /tmp/var/log/syslog*
 sudo rm -v /tmp/var/log/kern*

7) Vérifier si au moins 1 Go est devenu disponible.

df -htext4

Si  oui, tenter de rebooter.
Si pas le cas, faire des épurations dans le répertoire téléchargements.
8)  Identifier l'utilisateur.

sudo ls -l /mnt/home

9) Se mettre sous la structure de l'utilisateur. Penser à remplacer XXXXX par le nom trouvé.

cd /mnt/home/XXXX

10 Identifier les gros fichiers téléchargés.

 ls -lsSrh Téléchargements

En supprimer quelques-uns pour un total  de 1 Go. Penser à remplacer XXXXX par des noms trouvés.

rm -v   XXXXXXXXXXX

11) Rebooter.

Dernière modification par geole (Le 28/11/2024, à 11:05)


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#19 Le 28/11/2024, à 16:03

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Je ne sais pas comment faire parvenir les infos, refus obstiné de connexion depuis l’ordinateur. Pas moyen d’accéder à mon compte. Ce n’est pas un problème de clavier. Mot de passe et nom d’utilisateur identiques à ceux que j’utilise avec le téléphone, changé plusieurs fois au cas où, déconnecté pour ouvrir avec l’ordi, rien ne fonctionne.

Hors ligne

#20 Le 28/11/2024, à 16:05

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Est-ce qu’il y à un moyen quelconque de publier l’info?

Hors ligne

#21 Le 28/11/2024, à 16:21

geole

Re : Redémarrage impossible no recovery

Bonjour
Pas facile de comprendre ce qui se passe avec ton support d'installation si tu parles bien du support d'installation.


Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
Je défie QUICONQUE de trouver une discussion où j'aurais suggéré de remplacer un SSD par un disque dur.
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248

Hors ligne

#22 Le 28/11/2024, à 16:52

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

 ubuntu@ubuntu:~$ journalctl --no-pager -D /mnt/var/log/journal -b -p err -n 100
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]

Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]

Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]

Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]

Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]

Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: action 'action-2-builtin:omfile' (module 'builtin:omfile') message lost, could not be processed. Check for additional error messages before this one. [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:47 frede-Lenovo-IdeaPad-C340-15IIL rsyslogd[924]: file '/var/log/syslog'[7] write error - see https://www.rsyslog.com/solving-rsyslog-write-errors/ for help OS error: No space left on device [v8.2112.0 try https://www.rsyslog.com/e/2027 ]
Nov 27 19:40:49 frede-Lenovo-IdeaPad-C340-15IIL kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_TZ.ETMD], AE_NOT_FOUND (20230628/psargs-330)
Nov 27 19:40:49 frede-Lenovo-IdeaPad-C340-15IIL kernel: ACPI Error: Aborting method \ _SB.IETM._OSC due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL canonical-livepatch.canonical- livepatchd[989]: Task "refresh" returned an error: livepatch check failed: POST request to "https://livepatch.canonical.com/v1/client/188a28a4ff454d6abdc90dcdbc6a88c9/updates" failed, retrying in 1m0s.
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL livepatchd[989]: daemon shutting down
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL graveyard IO source: Stale file handle
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL graveyard IO source: Stale file handle
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL graveyard IO source: Stale file handle
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL graveyard IO source: Stale file handle
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL graveyard IO source: Stale file handle
Nov 27 19:40:52 frede-Lenovo-IdeaPad-C340-15IIL hostname reply: Transport endpoint is not connected ubuntu@ubuntu:~$
canonical-livepatch.canonical- systemd-resolved[755]: Failed systemd-resolved[755]: Failed systemd-resolved[755]: Failed systemd-resolved[755]: Failed systemd-resolved[755]: Failed systemd-resolved[755]: Failed
to create to create to create to create to create to send

Hors ligne

#23 Le 28/11/2024, à 16:55

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

Réponse au 4). Je fais la suite et je l’envoie (c’est pas très réactif, je dois passer par une clef et un mail sur un autre ordi qui n’ a pas non plus droit à la connexion au forum…?)

Hors ligne

#24 Le 28/11/2024, à 16:56

xubu1957

Re : Redémarrage impossible no recovery


Conseils pour les nouveaux demandeurs et pas qu'eux
Important : Pensez à passer vos sujets en [Réso|u] lorsque ceux-ci le sont, au début du titre en cliquant sur Modifier sous le premier message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.                   Membre de Linux-Azur

Hors ligne

#25 Le 28/11/2024, à 17:51

Fraise c’est moi aussi

Re : Redémarrage impossible no recovery

5a)

 ubuntu@ubuntu:~$ sudo du /mnt -haxd1 | sort -h | tail -15 8.0K /mnt/media
16K /mnt/dev
16K /mnt/lost+found
60K /mnt/tmp 104K /mnt/run 368K /mnt/snap 20M /mnt/etc
23M /mnt/root 273M /mnt/boot 467M /mnt/opt 2.1G /mnt/swapfile 7.9G /mnt/usr
30G /mnt/home 896G /mnt/var 935G /mnt

Hors ligne