#1 Le 24/02/2018, à 01:24
- bdadvi94
Busybox au démarrage (initramfs)
Bonjour,
Lorsque je démarre mon PC, je tombe sur un des deux écrans suivants, ça dépend:
https://image.noelshack.com/fichiers/20 … c-0173.jpg
https://image.noelshack.com/fichiers/20 … c-0174.jpg
Tout allait très bien jusqu'à aujourd'hui.
De temps en temps le PC restait bloqué sur l'écran de chargement Ubuntu et il suffisait de forcer l'arrêt e' appuyant sur le bouton et de le démarrer à nouveau. Aujourd'hui ça n'a pas marché...
Je précise que lorsque je laisse mon PC, je l'hiberne plutôt que de le mettre en veille, car en veille la batterie se vide tout de même (matériel sûrement mal supporté car mon PC est récent et cela n'arrive pas lorsqu'il est en veille sous Windows)
C'est la première fois que je vois ce genre d'erreur et les divers conseils que j'ai pu trouver ailleurs, comme la commande
fsck /des/sda1n'ont rien donné.
Comment résoudre ce problème et ne plus avoir ce genre de choses à l'avenir ?
Merci bien 
Dernière modification par bdadvi94 (Le 24/02/2018, à 13:12)
Hors ligne
#2 Le 24/02/2018, à 01:40
- bdadvi94
Re : Busybox au démarrage (initramfs)
PS: Lorsque j'essaye de boot sur un live CD Ubuntu ou GParted, mon PC ne détecte pas de périphérique bootable.
Hors ligne
#3 Le 25/02/2018, à 17:49
- bdadvi94
Re : Busybox au démarrage (initramfs)
Personne ? 
Hors ligne
#4 Le 25/02/2018, à 18:01
- lucmars
Re : Busybox au démarrage (initramfs)
De la premiere capture le ACPI semble etre en question, la seconde semble completer la premiere avec en plus :
le pilote video nouveau et l'usb. Mais pourquoi cela déconne depuis peu.
Ta quelle version de distro, aurais tu fait une mise à niveau et enfin c'est quoi ton pc ?
Gaulois Matter !
Hors ligne
#5 Le 25/02/2018, à 18:12
- bdadvi94
Re : Busybox au démarrage (initramfs)
Salut, ma version est la 17.04 LTS mais je n'en suis pas complètement sûr
Mon PC est un HP Omen 15-ax008nf
Je fais des mises à niveau de temps en temps mais la dernière remonte au moins à quelques semaines...
J'ai l'habitude de le mettre en hibernation plutôt qu'en veille, car la batterie se vide en une nuit en mode veille.
Au démarrage, il est resté bloqué sur l'écran de chargement comme cela arrive de temps en temps. J'ai alors éteint le PC avec le bouton power pour le rallumer, comme ce que je fais d'habitude, sauf que ça n'a pas fonctionné pour cette fois.
Hors ligne
#6 Le 25/02/2018, à 18:28
- lucmars
Re : Busybox au démarrage (initramfs)
T'es pas sur, tu veux dire que tu serais passer à la 1710 ?
Gaulois Matter !
Hors ligne
#7 Le 25/02/2018, à 18:36
- bdadvi94
Re : Busybox au démarrage (initramfs)
C'est bien possible, j'ai fait des dist-upgrade ou full-upgrade de temps en temps
Hors ligne
#8 Le 25/02/2018, à 19:55
- lucmars
Re : Busybox au démarrage (initramfs)
Je ne sais si une dist-upgrade conserve le noyau de la version précédente, mais bon.
Après l'écran du bios, appuies sur la touche shift pour faire apparaitre le grub, de là tu choisis "option avancées", t'auras la liste du (des) noyau dispos.
Donnes ici la ou les versions de noyau, de là on saura ta version de distro
Gaulois Matter !
Hors ligne
#9 Le 25/02/2018, à 21:30
- bdadvi94
Re : Busybox au démarrage (initramfs)
Tu parles de cet écran ?
http://image.noelshack.com/fichiers/201 … c-0175.jpg
J'ai déjà essayé de selectionner d'autres noyaux pour démarrer, mais la même erreur se produit
Dernière modification par bdadvi94 (Le 25/02/2018, à 21:54)
Hors ligne
#10 Le 26/02/2018, à 17:32
- lucmars
Re : Busybox au démarrage (initramfs)
Je vois qu'en fait tu es sous 1604 et depuis longtemps.
On a même pas la chance qu'une mise à niveau soit la raison de tes problèmes.
Gaulois Matter !
Hors ligne
#11 Le 27/02/2018, à 13:29
- bdadvi94
Re : Busybox au démarrage (initramfs)
Aucune idée du coup ?
Hors ligne
#12 Le 27/02/2018, à 20:51
- lucmars
Re : Busybox au démarrage (initramfs)
Pour ma part aucune malheureusement, mais si t'avais une clef/dvd avec la 1604 pour booter en mode esssayer et faire un boot-info (voir la doc) et dans la foulée t'installes gsmartcontrol avec quoi tu audites ton DD (tu copie/colle son rapport ici).
Avec cela, je ne te garantie pas des miracles, mais p'tet des pistes.
Gaulois Matter !
Hors ligne
#13 Le 28/02/2018, à 14:36
- bdadvi94
Re : Busybox au démarrage (initramfs)
Bon alors je vais me faire un live USB de la dernière version d'Ubuntu, virer la 16.04 et l'installer à la place, ça devrait régler le problème non ?
Par contre je sens que je vais avoir un peu de mal car je voudrais conserver la configuration actuelle:
-Dual boot Ubuntu / Windows sur SSD
-/home sur HDD
Hors ligne
#14 Le 28/02/2018, à 18:28
- bdadvi94
Re : Busybox au démarrage (initramfs)
Re,
Alors j’ai fait un live USB de Ubuntu 17.10, je cherche a l’installer par dessus Ubuntu 16.04 et voila ce que j’ai :
https://image.noelshack.com/fichiers/20 … -12-33.png
Est-ce que je peux continuer sans risque à ton avis ?
Je souhaite garder la même organisation qu'avant, càd:
-Ubuntu et Windows en dual boot sur le SSD
-/home de Ubuntu sur le HDD
Hors ligne
#15 Le 28/02/2018, à 18:45
- lucmars
Re : Busybox au démarrage (initramfs)
bdadvi94 a écrit :
Bon alors je vais me faire un live USB de la dernière version d'Ubuntu, virer la 16.04 et l'installer à la place, ça devrait régler le problème non ?
Par contre je sens que je vais avoir un peu de mal car je voudrais conserver la configuration actuelle:
-Dual boot Ubuntu / Windows sur SSD
-/home sur HDD
Là tu te lances dans l'opération chirurgicale sans diagnostic préalable.
Avec la 1710 tu risques d'avoir d'autres problèmes, de plus elle sera bientot périmée.
Utilises la 1604, fournis les rapports que je t'ai demandé :
- avec un boot-info on voit mieux ton partitionnement plus d'autres choses
- avec un audit de tes DD, si quelque chose cloche il sera inutile de réinstaller.
Gaulois Matter !
Hors ligne
#16 Le 28/02/2018, à 18:56
- bdadvi94
Re : Busybox au démarrage (initramfs)
Merci de ta réponse
Bon je fais un live USB de la 16.04, je le branche et te donne le boot-info
Hors ligne
#17 Le 28/02/2018, à 19:08
- bdadvi94
Re : Busybox au démarrage (initramfs)
Voilà le boot-info:
Hors ligne
#18 Le 28/02/2018, à 19:22
- lucmars
Re : Busybox au démarrage (initramfs)
Ton boot-info
Boot Info Script 8f991e4 + Boot-Repair extra info [Boot-Info 25oct2017]
============================= Boot Info Summary: ===============================
=> No boot loader is installed in the MBR of /dev/sda.
=> No boot loader is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System:
Boot files:
sdb1: __________________________________________________________________________
File system: vfat
Boot sector type: Windows 8/2012: FAT32
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /boot/grub/grub.cfg /syslinux.cfg /casper/vmlinuz.efi
/EFI/BOOT/grubx64.efi
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 1 1,953,525,167 1,953,525,167 ee GPT
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sda1 2,048 1,953,523,711 1,953,521,664 Data partition (Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
Drive: sdb _____________________________________________________________________
Disk /dev/sdb: 29.3 GiB, 31406948352 bytes, 61341696 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
Disklabel type: gpt
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 1 4,294,967,295 4,294,967,295 ee GPT
/dev/sdb1 ends after the last sector of /dev/sdb
GUID Partition Table detected.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sdb1 2,048 61,341,662 61,339,615 Data partition (Windows/Linux)
Attributes: R=Required, N=No Block IO, B=Legacy BIOS Bootable, +=More bits set
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/nvme0n1
/dev/nvme0n1p1 5A13-355C vfat
/dev/nvme0n1p2 356fd619-71bc-4c93-a8b7-96e8a5db7c90 ext4
/dev/nvme0n1p3 58b9def0-e9e3-4f64-bd60-db4a2cefd6c4 swap
/dev/nvme0n1p4 AC126F35126F03A4 ntfs
/dev/sda1 2e4fbf58-290c-4954-ae77-9ea6152bbe42 ext4
/dev/sdb1 0C5D-13F4 vfat UBUNTU 16_0
========================= "ls -l /dev/disk/by-id" output: ======================
total 0
lrwxrwxrwx 1 root root 9 Feb 28 17:06 ata-HGST_HTS721010A9E630_JR1000D30D42UF -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 28 17:06 ata-HGST_HTS721010A9E630_JR1000D30D42UF-part1 -> ../../sda1
lrwxrwxrwx 1 root root 13 Feb 28 17:06 nvme-SAMSUNG_MZVLV256HCHP-000H1_S2CSNX0H934364 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-SAMSUNG_MZVLV256HCHP-000H1_S2CSNX0H934364-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-SAMSUNG_MZVLV256HCHP-000H1_S2CSNX0H934364-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-SAMSUNG_MZVLV256HCHP-000H1_S2CSNX0H934364-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-SAMSUNG_MZVLV256HCHP-000H1_S2CSNX0H934364-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 13 Feb 28 17:06 nvme-eui.0025384961b4d8d1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-eui.0025384961b4d8d1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-eui.0025384961b4d8d1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-eui.0025384961b4d8d1-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 15 Feb 28 17:06 nvme-eui.0025384961b4d8d1-part4 -> ../../nvme0n1p4
lrwxrwxrwx 1 root root 9 Feb 28 17:06 usb-Lexar_USB_Flash_Drive_AA9VQNNZJT3RP9QZ-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 10 Feb 28 17:06 usb-Lexar_USB_Flash_Drive_AA9VQNNZJT3RP9QZ-0:0-part1 -> ../../sdb1
lrwxrwxrwx 1 root root 9 Feb 28 17:06 wwn-0x5000cca8c8c583cf -> ../../sda
lrwxrwxrwx 1 root root 10 Feb 28 17:06 wwn-0x5000cca8c8c583cf-part1 -> ../../sda1
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdb1 /cdrom vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
=========================== sdb1/boot/grub/grub.cfg: ===========================
--------------------------------------------------------------------------------
if loadfont /boot/grub/font.pf2 ; then
set gfxmode=auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
menuentry "Try Ubuntu without installing" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
initrd /casper/initrd.lz
}
menuentry "Install Ubuntu" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash ---
initrd /casper/initrd.lz
}
menuentry "OEM install (for manufacturers)" {
set gfxpayload=keep
linux /casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity quiet splash oem-config/enable=true ---
initrd /casper/initrd.lz
}
menuentry "Check disc for defects" {
set gfxpayload=keep
linux /casper/vmlinuz.efi boot=casper integrity-check quiet splash ---
initrd /casper/initrd.lz
}
--------------------------------------------------------------------------------
============================== sdb1/syslinux.cfg: ==============================
--------------------------------------------------------------------------------
DEFAULT loadconfig
LABEL loadconfig
CONFIG /isolinux/isolinux.cfg
APPEND /isolinux/
--------------------------------------------------------------------------------
=================== sdb1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
?? = ?? boot/grub/grub.cfg 1
================= sdb1: Location of files loaded by Syslinux: ==================
GiB - GB File Fragment(s)
?? = ?? syslinux.cfg 1
=============================== StdErr Messages: ===============================
File descriptor 9 (/proc/5481/mounts) leaked on lvs invocation. Parent PID 15088: bash
File descriptor 63 (pipe:[51320]) leaked on lvs invocation. Parent PID 15088: bash
ADDITIONAL INFORMATION :
=================== log of boot-info 20180228_1706 ===================
boot-info version : 4ppa65
boot-sav version : 4ppa65
boot-sav-extra version : 4ppa65
glade2script version : 3.2.3~ppa4
boot-info is executed in live-session (Ubuntu 16.04.3 LTS, xenial, Ubuntu, x86_64)
CPU op-mode(s): 32-bit, 64-bit
BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed boot=casper quiet splash ---
ls: cannot access '/home/usr/.config': No such file or directory
Windows is hibernated, refused to mount.
Failed to mount '/dev/nvme0n1p4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
mount -t ntfs-3g -o remove_hiberfile /dev/nvme0n1p4 /mnt/boot-sav/nvme0n1p4
The disk contains an unclean file system (0, 0).
Metadata kept in Windows cache, refused to mount.
Failed to mount '/dev/nvme0n1p4': Operation not permitted
The NTFS partition is in an unsafe state. Please resume and shutdown
Windows fully (no hibernation or fast restarting), or mount the volume
read-only with the 'ro' mount option.
mount /dev/nvme0n1p4 : Error code 14
mount -r /dev/nvme0n1p4 /mnt/boot-sav/nvme0n1p4
=================== os-prober:
/dev/nvme0n1p1@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/nvme0n1p2:Ubuntu 16.04.3 LTS (16.04):Ubuntu:linux
=================== blkid:
/dev/nvme0n1p1: UUID="5A13-355C" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="5ef619a8-dde3-4d11-a230-abfaf62be405"
/dev/nvme0n1p2: UUID="356fd619-71bc-4c93-a8b7-96e8a5db7c90" TYPE="ext4" PARTUUID="a81a52ab-d76c-4eeb-a518-6810a50c4b34"
/dev/nvme0n1p4: UUID="AC126F35126F03A4" TYPE="ntfs" PARTLABEL="placepourwindows" PARTUUID="47958912-143c-474b-ae07-ff0fbe76ed11"
/dev/sda1: UUID="2e4fbf58-290c-4954-ae77-9ea6152bbe42" TYPE="ext4" PARTUUID="346c74c2-af05-432b-a415-c5bcce7795b5"
/dev/sdb1: LABEL="UBUNTU 16_0" UUID="0C5D-13F4" TYPE="vfat" PARTLABEL="Microsoft Basic Data" PARTUUID="4aa43bf4-ab9c-4c5d-b81e-5f270c034fc2"
/dev/loop0: TYPE="squashfs"
/dev/nvme0n1p3: UUID="58b9def0-e9e3-4f64-bd60-db4a2cefd6c4" TYPE="swap" PARTUUID="80962bac-8d1a-4629-9d3e-291c3f6608ac"
/dev/nvme0n1: PTUUID="672ccf36-a3e3-4beb-b8ec-d22f0288cddd" PTTYPE="gpt"
1 disks with OS, 2 OS : 1 Linux, 0 MacOS, 1 Windows, 0 unknown type OS.
Windows not detected by os-prober on nvme0n1p4.
Presence of EFI/Microsoft file detected: /mnt/boot-sav/nvme0n1p1/EFI/Microsoft/Boot/bootmgfw.efi
Presence of EFI/Boot file detected: /mnt/boot-sav/nvme0n1p1/EFI/Boot/bootx64.efi
=================== nvme0n1p2/etc/grub.d/ :
drwxr-xr-x 2 root root 4096 Jan 3 23:27 grub.d
total 80
-rwxr-xr-x 1 root root 9791 Apr 15 2016 00_header
-rwxr-xr-x 1 root root 6258 Mar 15 2016 05_debian_theme
-rwxr-xr-x 1 root root 12512 Jun 21 2017 10_linux
-rwxr-xr-x 1 root root 11082 Apr 15 2016 20_linux_xen
-rwxr-xr-x 1 root root 1992 Jan 28 2016 20_memtest86+
-rwxr-xr-x 1 root root 11692 Apr 15 2016 30_os-prober
-rwxr-xr-x 1 root root 1418 Apr 15 2016 30_uefi-firmware
-rwxr-xr-x 1 root root 214 Apr 15 2016 40_custom
-rwxr-xr-x 1 root root 216 Apr 15 2016 41_custom
-rw-r--r-- 1 root root 483 Apr 15 2016 README
=================== nvme0n1p2/etc/default/grub :
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
# info -f grub -n 'Simple configuration'
GRUB_DEFAULT=0
#GRUB_HIDDEN_TIMEOUT=0
GRUB_HIDDEN_TIMEOUT_QUIET=true
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480
# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"
# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"
/boot/efi detected in the fstab of nvme0n1p2: UUID=5A13-355C (nvme0n1p1)
=================== nvme0n1p2recordfail=1/grub/grubenv :
recordfail=1
=================== efibootmgr -v
BootCurrent: 0002
Timeout: 5 seconds
BootOrder: 2001,0001,3001,0005,0004,0003,0000,2002,2004
Boot0000* Disque dur portable - HGST HTS721010A9E630 BBS(HD,Disque dur portable - HGST HTS721010A9E630,0x500)................-...........A.......................................k.......A.........................
Boot0001* ubuntu HD(1,GPT,5ef619a8-dde3-4d11-a230-abfaf62be405,0x800,0x100000)/File(EFIubuntushimx64.efi)
Boot0002* Disque dur USB (UEFI) - Lexar USB Flash Drive PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,GPT,4aa43bf4-ab9c-4c5d-b81e-5f270c034fc2,0x800,0x3a7f7df)RC
Boot0003* Disque dur portable - SAMSUNG MZVLV256HCHP-000H1 BBS(HD,Disque dur portable - SAMSUNG MZVLV256HCHP-000H1,0x500)................+..P....#..P?..P....................................j.......A...........................%8Ia......
Boot0004* Disque dur USB - Lexar USB Flash Drive BBS(7,Disque dur USB - Lexar USB Flash Drive,0x500)..................F.......D...H...................................].j.......A.....................
Boot0005* Windows Boot Manager HD(1,GPT,5ef619a8-dde3-4d11-a230-abfaf62be405,0x800,0x100000)/File(EFIMicrosoftBootbootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot2001* EFI USB Device RC
Boot3001* Internal Hard Disk or Solid State Disk RC
=================== UEFI/Legacy mode:
BIOS is EFI-compatible, and is setup in EFI-mode for this live-session.
SecureBoot disabled. (maybe sec-boot, Please report this message to boot.repair@gmail.com)
=================== PARTITIONS & DISKS:
nvme0n1p1 : nvme0n1, not-sepboot, no-grubenv nogrub, no-docgrub, no-update-grub, 32, no-boot, is-os, is-correct-EFI, part-has-no-fstab, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, nopakmgr, nogrubinstall, no---usr, part-has-no-fstab, not-sep-usr, standard, not-far, notbiosboot, /mnt/boot-sav/nvme0n1p1.
nvme0n1p2 : nvme0n1, not-sepboot, grubenv-ng grub2, signed grub-efi , update-grub, 64, with-boot, is-os, not--efi--part, fstab-without-boot, fstab-has-goodEFI, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, apt-get, grub-install, with--usr, fstab-without-usr, not-sep-usr, standard, farbios, notbiosboot, /mnt/boot-sav/nvme0n1p2.
nvme0n1p4 : nvme0n1, not-sepboot, no-grubenv nogrub, no-docgrub, no-update-grub, 32, no-boot, is-os, not--efi--part, part-has-no-fstab, part-has-no-fstab, no-nt, haswinload, no-recov-nor-hid, no-bmgr, notwinboot, nopakmgr, nogrubinstall, no---usr, part-has-no-fstab, not-sep-usr, standard, not-far, notbiosboot, /mnt/boot-sav/nvme0n1p4.
sda1 : sda, maybesepboot, no-grubenv nogrub, no-docgrub, no-update-grub, 32, no-boot, no-os, not--efi--part, part-has-no-fstab, part-has-no-fstab, no-nt, no-winload, no-recov-nor-hid, no-bmgr, notwinboot, nopakmgr, nogrubinstall, no---usr, part-has-no-fstab, not-sep-usr, standard, farbios, notbiosboot, /mnt/boot-sav/sda1.
nvme0n1 : GPT, no-BIOS_boot, has-correctEFI, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
sda : GPT, no-BIOS_boot, has-no-EFIpart, not-usb, not-mmc, no-os, 2048 sectors * 512 bytes
=================== parted -lm:
BYT;
/dev/sda:1000GB:scsi:512:4096:gpt:ATA HGST HTS721010A9:;
1:1049kB:1000GB:1000GB:ext4::;
BYT;
/dev/sdb:31.4GB:scsi:512:512:gpt:Lexar USB Flash Drive:;
1:1049kB:31.4GB:31.4GB:fat32:Microsoft Basic Data:msftdata;
BYT;
/dev/nvme0n1:256GB:unknown:512:512:gpt:Unknown:;
1:1049kB:538MB:537MB:fat32:EFI System Partition:boot, esp;
4:538MB:62.3GB:61.8GB:ntfs:placepourwindows:msftdata;
2:62.3GB:248GB:185GB:ext4::;
3:248GB:256GB:8475MB:linux-swap(v1)::;
=================== lsblk:
KNAME TYPE FSTYPE SIZE LABEL
sdb disk 29.3G
sdb1 part vfat 29.3G UBUNTU 16_0
loop0 loop squashfs 1.4G
sda disk 931.5G
sda1 part ext4 931.5G
nvme0n1 disk 238.5G
nvme0n1p3 part swap 7.9G
nvme0n1p1 part vfat 512M
nvme0n1p4 part ntfs 57.5G
nvme0n1p2 part ext4 172.6G
KNAME ROTA RO RM STATE MOUNTPOINT
sdb 1 0 1 running
sdb1 1 0 1 /cdrom
loop0 1 1 0 /rofs
sda 1 0 0 running
sda1 1 0 0 /mnt/boot-sav/sda1
nvme0n1 0 0 0
nvme0n1p3 0 0 0
nvme0n1p1 0 0 0 /mnt/boot-sav/nvme0n1p1
nvme0n1p4 0 0 0 /mnt/boot-sav/nvme0n1p4
nvme0n1p2 0 0 0 /mnt/boot-sav/nvme0n1p2
=================== mount:
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,nosuid,relatime,size=4014384k,nr_inodes=1003596,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=806088k,mode=755)
/dev/sdb1 on /cdrom type vfat (ro,noatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/loop0 on /rofs type squashfs (ro,noatime)
aufs on / type aufs (rw,noatime,si=ec5fc77d7e395029)
securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
efivarfs on /sys/firmware/efi/efivars type efivarfs (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=34,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=13052)
mqueue on /dev/mqueue type mqueue (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,relatime)
tmpfs on /run/user/999 type tmpfs (rw,nosuid,nodev,relatime,size=806088k,mode=700,uid=999,gid=999)
gvfsd-fuse on /run/user/999/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=999,group_id=999)
/dev/nvme0n1p1 on /mnt/boot-sav/nvme0n1p1 type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/nvme0n1p2 on /mnt/boot-sav/nvme0n1p2 type ext4 (rw,relatime,data=ordered)
/dev/nvme0n1p4 on /mnt/boot-sav/nvme0n1p4 type fuseblk (ro,relatime,user_id=0,group_id=0,allow_other,blksize=4096)
/dev/sda1 on /mnt/boot-sav/sda1 type ext4 (rw,relatime,data=ordered)
=================== ls:
/sys/block/nvme0n1 (filtered): alignment_offset badblocks bdi capability dev device discard_alignment eui ext_range holders inflight integrity mq nsid nvme0n1p1 nvme0n1p2 nvme0n1p3 nvme0n1p4 power queue range removable ro size slaves stat subsystem trace uevent wwid
/sys/block/sda (filtered): alignment_offset badblocks bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sda1 size slaves stat subsystem trace uevent
/sys/block/sdb (filtered): alignment_offset badblocks bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range holders inflight integrity power queue range removable ro sdb1 size slaves stat subsystem trace uevent
/dev (filtered): acpi_thermal_rel autofs block bsg btrfs-control bus char console core cpu cpu_dma_latency cuse disk dri drm_dp_aux0 ecryptfs fb0 fd freefall full fuse hpet hugepages hwrng i2c-0 i2c-1 i2c-10 i2c-11 i2c-12 i2c-13 i2c-14 i2c-15 i2c-2 i2c-3 i2c-4 i2c-5 i2c-6 i2c-7 i2c-8 i2c-9 initctl input kmsg lightnvm log mapper mcelog media0 mei0 mem memory_bandwidth mqueue net network_latency network_throughput null nvme0 nvme0n1 nvme0n1p1 nvme0n1p2 nvme0n1p3 nvme0n1p4 port ppp psaux ptmx pts random rfkill rtc rtc0 sda sda1 sdb sdb1 sg0 sg1 shm snapshot snd stderr stdin stdout tpm0 uhid uinput urandom userio v4l vfio vga_arbiter vhci vhost-net video0 zero
ls /dev/mapper: control
=================== hexdump -n512 -C /dev/nvme0n1p1
00000000 eb 58 90 6d 6b 66 73 2e 66 61 74 00 02 08 20 00 |.X.mkfs.fat... .|
00000010 02 00 00 00 00 f8 00 00 20 00 40 00 00 08 00 00 |........ .@.....|
00000020 00 00 10 00 fe 03 00 00 00 00 00 00 02 00 00 00 |................|
00000030 01 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00000040 80 01 29 5c 35 13 5a 4e 4f 20 4e 41 4d 45 20 20 |..)5.ZNO NAME |
00000050 20 20 46 41 54 33 32 20 20 20 0e 1f be 77 7c ac | FAT32 ...w|.|
00000060 22 c0 74 0b 56 b4 0e bb 07 00 cd 10 5e eb f0 32 |".t.V.......^..2|
00000070 e4 cd 16 cd 19 eb fe 54 68 69 73 20 69 73 20 6e |.......This is n|
00000080 6f 74 20 61 20 62 6f 6f 74 61 62 6c 65 20 64 69 |ot a bootable di|
00000090 73 6b 2e 20 20 50 6c 65 61 73 65 20 69 6e 73 65 |sk. Please inse|
000000a0 72 74 20 61 20 62 6f 6f 74 61 62 6c 65 20 66 6c |rt a bootable fl|
000000b0 6f 70 70 79 20 61 6e 64 0d 0a 70 72 65 73 73 20 |oppy and..press |
000000c0 61 6e 79 20 6b 65 79 20 74 6f 20 74 72 79 20 61 |any key to try a|
000000d0 67 61 69 6e 20 2e 2e 2e 20 0d 0a 00 00 00 00 00 |gain ... .......|
000000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
*
000001f0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa |..............U.|
00000200
=================== hexdump -n512 -C /dev/nvme0n1p4
00000000 eb 52 90 4e 54 46 53 20 20 20 20 00 02 08 00 00 |.R.NTFS .....|
00000010 00 00 00 00 00 f8 00 00 3f 00 ff 00 00 08 10 00 |........?.......|
00000020 00 00 00 00 80 00 80 00 ff a7 30 07 00 00 00 00 |..........0.....|
00000030 00 00 0c 00 00 00 00 00 02 00 00 00 00 00 00 00 |................|
00000040 f6 00 00 00 01 00 00 00 a4 03 6f 12 35 6f 12 ac |..........o.5o..|
00000050 00 00 00 00 fa 33 c0 8e d0 bc 00 7c fb 68 c0 07 |.....3.....|.h..|
00000060 1f 1e 68 66 00 cb 88 16 0e 00 66 81 3e 03 00 4e |..hf......f.>..N|
00000070 54 46 53 75 15 b4 41 bb aa 55 cd 13 72 0c 81 fb |TFSu..A..U..r...|
00000080 55 aa 75 06 f7 c1 01 00 75 03 e9 dd 00 1e 83 ec |U.u.....u.......|
00000090 18 68 1a 00 b4 48 8a 16 0e 00 8b f4 16 1f cd 13 |.h...H..........|
000000a0 9f 83 c4 18 9e 58 1f 72 e1 3b 06 0b 00 75 db a3 |.....X.r.;...u..|
000000b0 0f 00 c1 2e 0f 00 04 1e 5a 33 db b9 00 20 2b c8 |........Z3... +.|
000000c0 66 ff 06 11 00 03 16 0f 00 8e c2 ff 06 16 00 e8 |f...............|
000000d0 4b 00 2b c8 77 ef b8 00 bb cd 1a 66 23 c0 75 2d |K.+.w......f#.u-|
000000e0 66 81 fb 54 43 50 41 75 24 81 f9 02 01 72 1e 16 |f..TCPAu$....r..|
000000f0 68 07 bb 16 68 52 11 16 68 09 00 66 53 66 53 66 |h...hR..h..fSfSf|
00000100 55 16 16 16 68 b8 01 66 61 0e 07 cd 1a 33 c0 bf |U...h..fa....3..|
00000110 0a 13 b9 f6 0c fc f3 aa e9 fe 01 90 90 66 60 1e |.............f`.|
00000120 06 66 a1 11 00 66 03 06 1c 00 1e 66 68 00 00 00 |.f...f.....fh...|
00000130 00 66 50 06 53 68 01 00 68 10 00 b4 42 8a 16 0e |.fP.Sh..h...B...|
00000140 00 16 1f 8b f4 cd 13 66 59 5b 5a 66 59 66 59 1f |.......fY[ZfYfY.|
00000150 0f 82 16 00 66 ff 06 11 00 03 16 0f 00 8e c2 ff |....f...........|
00000160 0e 16 00 75 bc 07 1f 66 61 c3 a1 f6 01 e8 09 00 |...u...fa.......|
00000170 a1 fa 01 e8 03 00 f4 eb fd 8b f0 ac 3c 00 74 09 |............<.t.|
00000180 b4 0e bb 07 00 cd 10 eb f2 c3 0d 0a 45 72 72 65 |............Erre|
00000190 75 72 20 6c 65 63 74 75 72 65 20 64 69 73 71 75 |ur lecture disqu|
000001a0 65 00 0d 0a 42 4f 4f 54 4d 47 52 20 63 6f 6d 70 |e...BOOTMGR comp|
000001b0 72 65 73 73 82 00 0d 0a 43 74 72 6c 2b 41 6c 74 |ress....Ctrl+Alt|
000001c0 2b 53 75 70 70 72 20 70 6f 75 72 20 72 65 64 82 |+Suppr pour red.|
000001d0 6d 61 72 72 65 72 0d 0a 00 73 74 61 72 74 0d 0a |marrer...start..|
000001e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000001f0 00 00 00 00 00 00 8a 01 a2 01 b6 01 00 00 55 aa |..............U.|
00000200
=================== df -Th:
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 3.9G 0 3.9G 0% /dev
tmpfs tmpfs 788M 9.5M 778M 2% /run
/dev/sdb1 vfat 30G 1.5G 28G 6% /cdrom
/dev/loop0 squashfs 1.5G 1.5G 0 100% /rofs
aufs aufs 3.9G 75M 3.8G 2% /
tmpfs tmpfs 3.9G 180K 3.9G 1% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
tmpfs tmpfs 3.9G 264K 3.9G 1% /tmp
tmpfs tmpfs 788M 88K 788M 1% /run/user/999
/dev/nvme0n1p1 vfat 511M 29M 483M 6% /mnt/boot-sav/nvme0n1p1
/dev/nvme0n1p2 ext4 170G 12G 151G 7% /mnt/boot-sav/nvme0n1p2
/dev/nvme0n1p4 fuseblk 58G 57G 982M 99% /mnt/boot-sav/nvme0n1p4
/dev/sda1 ext4 917G 818G 54G 94% /mnt/boot-sav/sda1
=================== fdisk -l:
Disk /dev/loop0: 1.4 GiB, 1532116992 bytes, 2992416 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 /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 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
Disklabel type: gpt
Disk identifier: 672CCF36-A3E3-4BEB-B8EC-D22F0288CDDD
Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme0n1p2 121679872 483565567 361885696 172.6G Linux filesystem
/dev/nvme0n1p3 483565568 500117503 16551936 7.9G Linux swap
/dev/nvme0n1p4 1050624 121679871 120629248 57.5G Microsoft basic data
Partition table entries are not in disk order.
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 011ADF34-62E7-40BA-BF16-2FDDBB5827EF
Device Start End Sectors Size Type
/dev/sda1 2048 1953523711 1953521664 931.5G Linux filesystem
Disk /dev/sdb: 29.3 GiB, 31406948352 bytes, 61341696 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
Disklabel type: gpt
Disk identifier: 8B6C8B51-FB43-47DE-9CDE-F6ADFA72A4F2
Device Start End Sectors Size Type
/dev/sdb1 2048 61341662 61339615 29.3G Microsoft basic data
=================== Suggested repair
The default repair of the Boot-Repair utility would reinstall the grub-efi-amd64-signed of nvme0n1p2, using the following options: nvme0n1p1/boot/efi,
Additional repair would be performed: unhide-bootmenu-10s fix-windows-boot use-standard-efi-file
=================== Final advice in case of suggested repair
Please do not forget to make your BIOS boot on nvme0n1p1/efi/.../grub*.efi file!
If your computer reboots directly into Windows, try to change the boot order in your BIOS.
If your BIOS does not allow to change the boot order, change the default boot entry of the Windows bootloader.
For example you can boot into Windows, then type the following command in an admin command prompt:
bcdedit /set {bootmgr} path \EFI\...\grub*.efi
=================== User settings
The settings chosen by the user will not act on the boot.Difficile à suivre avec les nvme, mais bon.
As-tu audité tes disques avec gsmartcontrol ?
Gaulois Matter !
Hors ligne
#19 Le 28/02/2018, à 19:32
- bdadvi94
Re : Busybox au démarrage (initramfs)
J'ai suivi les instruction de la partie 1 de cette page: https://doc.ubuntu-fr.org/smartmontools
Mais lorsque je veux installer l'interface graphique gsmartcontrol, une boîte de dialogue me dit que le paquet est virtuel. C'est tout.
C'est normal ?
Merci encore
Hors ligne
#20 Le 28/02/2018, à 19:54
- lucmars
Re : Busybox au démarrage (initramfs)
Oui, car soit c'est smartmontools en ligne de commande; soit gsmartcontrol avec smartmontools inclus.
Gaulois Matter !
Hors ligne
#21 Le 28/02/2018, à 19:59
- bdadvi94
Re : Busybox au démarrage (initramfs)
Ok, mais même si je désinstalle smartmontools, je ne peux toujours pas installer la version graphique.
Qu'est-ce que je dois faire du coup ?
Hors ligne
#22 Le 28/02/2018, à 20:34
- lucmars
Re : Busybox au démarrage (initramfs)
Refais une session live (je suppose que tu y étais).
Commences par gsmartcontrol et sinon smartmontools en ligne de commande
Gaulois Matter !
Hors ligne
#23 Le 28/02/2018, à 21:05
- bdadvi94
Re : Busybox au démarrage (initramfs)
Bon je n'ai pas réussi à installer gsmartcontrol
sudo apt install gsmartcontrol
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package gsmartcontrol is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'gsmartcontrol' has no installation candidateMais pour smartmontools, voilà les retours:
sudo smartctl -s on -a /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: HGST Travelstar 7K1000
Device Model: HGST HTS721010A9E630
Serial Number: JR1000D30D42UF
LU WWN Device Id: 5 000cca 8c8c583cf
Firmware Version: JB0OA3T0
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Feb 28 19:03:05 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 170) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0025 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0023 136 100 033 Pre-fail Always - 2
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1746
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x002f 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 2125
10 Spin_Retry_Count 0x0033 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1231
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 188979412992
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 65536
190 Airflow_Temperature_Cel 0x0022 065 054 045 Old_age Always - 35 (Min/Max 28/39)
191 G-Sense_Error_Rate 0x0032 091 091 000 Old_age Always - 2398
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2752554
193 Load_Cycle_Count 0x0032 089 089 000 Old_age Always - 116940
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 0
223 Load_Retry_Count 0x002a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
ubuntu@ubuntu:~$ sudo smartctl -s on -a /dev/sda1
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: HGST Travelstar 7K1000
Device Model: HGST HTS721010A9E630
Serial Number: JR1000D30D42UF
LU WWN Device Id: 5 000cca 8c8c583cf
Firmware Version: JB0OA3T0
User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 7200 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Wed Feb 28 19:03:09 2018 UTC
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF ENABLE/DISABLE COMMANDS SECTION ===
SMART Enabled.
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x84) Offline data collection activity
was suspended by an interrupting command from host.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 45) seconds.
Offline data collection
capabilities: (0x5b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
No Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 170) minutes.
SCT capabilities: (0x003d) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 100 100 062 Pre-fail Always - 0
2 Throughput_Performance 0x0025 100 100 040 Pre-fail Offline - 0
3 Spin_Up_Time 0x0023 136 100 033 Pre-fail Always - 2
4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1746
5 Reallocated_Sector_Ct 0x0033 100 100 005 Pre-fail Always - 0
7 Seek_Error_Rate 0x002f 100 100 067 Pre-fail Always - 0
8 Seek_Time_Performance 0x0025 100 100 040 Pre-fail Offline - 0
9 Power_On_Hours 0x0032 096 096 000 Old_age Always - 2125
10 Spin_Retry_Count 0x0033 100 100 060 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1231
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0033 100 100 097 Pre-fail Always - 0
187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 188979412992
188 Command_Timeout 0x0032 100 100 000 Old_age Always - 65536
190 Airflow_Temperature_Cel 0x0022 065 054 045 Old_age Always - 35 (Min/Max 28/39)
191 G-Sense_Error_Rate 0x0032 091 091 000 Old_age Always - 2398
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 2752554
193 Load_Cycle_Count 0x0032 089 089 000 Old_age Always - 116940
196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 100 100 000 Old_age Always - 0
223 Load_Retry_Count 0x002a 100 100 000 Old_age Always - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
ubuntu@ubuntu:~$ sudo smartctl -s on -a /dev/sdb
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/sdb: Unknown USB bridge [0x05dc:0xa815 (0x1100)]
Please specify device type with the -d option.
Use smartctl -h to get a usage summary
ubuntu@ubuntu:~$ sudo smartctl -s on -a /dev/sdb1
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Vendor: Lexar
Product: USB Flash Drive
Revision: 1100
User Capacity: 31,406,948,352 bytes [31.4 GB]
Logical block size: 512 bytes
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
ubuntu@ubuntu:~$ Dernière modification par bdadvi94 (Le 28/02/2018, à 21:05)
Hors ligne
#24 Le 01/03/2018, à 17:59
- lucmars
Re : Busybox au démarrage (initramfs)
J'en reviens à toi (à moins que tu ais tout réinstallé).
T'as audité deux fois ton HD, et aussi ta clef, mais pas le ssd.
Apparemment rien d'anormal pour ton HD.
Je sais bien qu'en live on ne conserve rien mais bon, tu pourrais recommencer l'audite en passant au préalable la commande
sudo parted -lafin de reperer ton SSD.
Du boot-info ta partition windows est proche des 100%, ton home est plein à 94%.
Mais cela est normalement sans rapport avec ton problème. La cause tiendrait de ta partition racine, quasi vide; d'où l'audite du SSD
Gaulois Matter !
Hors ligne
#25 Le 03/03/2018, à 01:51
- bdadvi94
Re : Busybox au démarrage (initramfs)
Salut, alors voilà le retour des commandes:
sudo parted -l
Model: ATA HGST HTS721010A9 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1000GB 1000GB ext4
Model: Lexar USB Flash Drive (scsi)
Disk /dev/sdb: 31.4GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 31.4GB 31.4GB fat32 Microsoft Basic Data msftdata
Model: Unknown (unknown)
Disk /dev/nvme0n1: 256GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 538MB 537MB fat32 EFI System Partition boot, esp
4 538MB 62.3GB 61.8GB ntfs placepourwindows msftdata
2 62.3GB 248GB 185GB ext4
3 248GB 256GB 8475MB linux-swap(v1)Malheureusement la commande appliquée au nom du SSD ne donne pas grand chose:
sudo smartctl -s on -a /dev/nvme0n1
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.10.0-28-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
/dev/nvme0n1: Unable to detect device type
Please specify device type with the -d option.
Use smartctl -h to get a usage summaryPourtant le SSD est bien le disque de 256 Go
J'obtiens le même retour lorsque je change "nvme0n1" par "nvme" ou "nvme0n1p1" etc.
Hors ligne