#1 Le 03/08/2017, à 17:54
- AnatoleD
Démarrage bloqué
Bonjour,
Mauvaise surprise à l'allumage : « The root file system on /dev/sda1 requires a manual fsck »
Et puis une invite que je n'avais jamais vu : (initramfs)
Qqn pour me sortir de ce mauvais pas ?
Merci !
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#2 Le 03/08/2017, à 18:02
- teabow
Re : Démarrage bloqué
Message sensiblement différent du mien, mais problème similaire.
Je te tiens au courant si j'ai du nouveau ici.
En attendant, tu peux consulter les pages du forum qui traitent déjà du sujet, et qui sont répertoriées dans mon post. Le plus simple est apparemment de redémarrer sur un liveusb et de faire check and repair via gparted (sur sda1 pour toi) ou via fsck dans un terminal (mais il faut au préalable booter depuis un live)
Hors ligne
#3 Le 03/08/2017, à 19:34
- AnatoleD
Re : Démarrage bloqué
Cata... J'ai tenté une réparation, et j'en suis maintenant à une "kernel panic"...
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#4 Le 03/08/2017, à 23:33
- ??
Re : Démarrage bloqué
Bonsoir
vus tous ces ennuis, je te propose un petit bilan avec un rapport bisnext https://doc.ubuntu-fr.org/bisnext
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#5 Le 04/08/2017, à 05:33
- AnatoleD
Re : Démarrage bloqué
Voici le rapport :
Aug 4 2017, bisnext report id 2644c also available at https://paste.debian.net/979792/
=== Hints ===
- The hard disk SMART Attibutes shows the shock-sensitive sensors recorded
errors as a result of impact loads. This might damage the hard disk, take care.
bisnext 0.11.5
============================ Hardware and System Summary ======================
System: Kernel: 4.8.0-36-generic x86_64 (64 bit gcc: 5.4.0)
Console: tty 1 dm: lightdm Distro: Ubuntu 16.04.2 LTS
Machine: Device: laptop System: CLEVO product: W240EU/W250EUQ/W270EUQ
Mobo: CLEVO model: W240EU/W250EUQ/W270EUQ v: V3.0
BIOS: American Megatrends v: 4.6.5 date: 09/27/2012
Chassis: No Enclosure type: 10
CPU: Quad core Intel Core i7-3610QM (-HT-MCP-) cache: 6144 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 18359
clock speeds: min/max: 1200/3300 MHz 1: 1204 MHz 2: 1212 MHz
3: 1200 MHz 4: 1579 MHz 5: 1293 MHz 6: 1449 MHz 7: 1212 MHz
8: 1224 MHz
Memory: Array-1 capacity: 16 GB devices: 2 EC: None
Device-1: ChannelA-DIMM0 size: 8 GB speed: 1600 MHz type: DDR3
manufacturer: Samsung part: M471B1G73CB0-YK0
Device-2: ChannelB-DIMM0 size: 8 GB speed: 1600 MHz type: DDR3
manufacturer: Samsung part: M471B1G73CB0-YK0
Graphics: Card: Intel 3rd Gen Core processor Graphics Controller
bus-ID: 00:02.0 chip-ID: 8086:0166
Display Server: X.Org 1.18.4 drivers: modesetting (unloaded: fbdev,vesa)
Resolution: 1366x768@60.00hz
OpenGL: renderer: Mesa DRI Intel Ivybridge Mobile
version: 3.3 Mesa 12.0.6 (compat-v: 3.0) Direct Render: Yes
Audio: Card Intel 7 Series/C210 Series Family High Definition Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:1e20
Sound: Advanced Linux Sound Architecture v: k4.8.0-36-generic
Network: Card-1: Qualcomm Atheros AR9285 Wireless Network Adapter (PCI-Express)
driver: ath9k bus-ID: 02:00.0 chip-ID: 168c:002b
IF: wlp2s0 state: up mac: <filter>
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
driver: r8169 v: 2.3LK-NAPI port: e000
bus-ID: 03:00.2 chip-ID: 10ec:8168
IF: enp3s0f2 state: down mac: <filter>
Drives: HDD Total Size: NA (-)
ID-1: /dev/sda model: SAMSUNG_HN size: 1000.2GB
temp: 34C
ID-2: USB /dev/sdb model: Transcend_4GB size: 4.0GB
temp: 0C
Optical-1: /dev/sr0 model: TSST CDDVDW SN-208DB
rev: TC01 dev-links: cdrom,cdrw,dvd,dvdrw
Features: speed: 24x multisession: yes
audio: yes dvd: yes rw: cd-r,cd-rw,dvd-r,dvd-ram state: running
RAID: System: supported: N/A
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Sensors: System Temperatures: cpu: 57.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Repos: Active apt sources in file: /etc/apt/sources.list
deb cdrom:[Ubuntu 16.04.2 LTS _Xenial Xerus_ - Release amd64 (20170215.2)]/ xenial main restricted
deb http://archive.ubuntu.com/ubuntu/ xenial main restricted multiverse universe
deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted multiverse universe
deb http://archive.ubuntu.com/ubuntu/ xenial-updates main restricted multiverse universe
Active apt sources in file: /etc/apt/sources.list.d/cematinla-ubuntu-bisnext-xenial.list
deb http://ppa.launchpad.net/cematinla/bisnext/ubuntu xenial main
Processes: CPU: % used - Memory: MB / % used - top 5 active
1: cpu: 3.6% command: firefox pid: 5234 mem: 273.48MB (1.7%)
2: cpu: 2.0% command: bisnext (started by: bash) pid: 13905 mem: 4.25MB (0.0%)
3: cpu: 1.5% command: compiz pid: 4551 mem: 186.41MB (1.1%)
4: cpu: 1.3% command: plugin-container pid: 5356 mem: 149.34MB (0.9%)
5: cpu: 1.0% command: Xorg pid: 4092 mem: 77.17MB (0.4%)
Info: Processes: 276 Uptime: 15 min Memory: 1212.4/15938.4MB
Init: systemd v: 229 runlevel: 5 default: 2 Gcc sys: 5.4.0
Client: Shell (bisnext running in bisnext) inxi: 2.3.25
_______________________________ UEFI settings _________________________________
Computer booted in Legacy mode for this session.
UEFI currently not active or not available on this system.
Secure Boot disabled or not available on this system.
__________________________________ OS prober ________________________________
/dev/sda1:Ubuntu 16.04.2 LTS (16.04):Ubuntu:linux
========================= Boot Information Details ============================
=> Grub2 (v2.00) is installed in the MBR of /dev/sda and looks at sector 1 of
the same hard drive for core.img. core.img is at this location and looks
for (,msdos1)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
=> No known boot loader is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: ext4
Boot sector type:
Boot sector info:
Operating System: Ubuntu 16.04.2 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab /etc/default/grub
/boot/grub/i386-pc/core.img
sdb2: __________________________________________________________________________
File system: vfat
Boot sector type: FAT16
Boot sector info: According to the info in the boot sector, sdb2 starts
at sector 0. But according to the info from fdisk,
sdb2 starts at sector 14432. According to the info in
the boot sector, sdb2 has 0 sectors.
Operating System:
Boot files:
_________________________=== Drive/Partition Info ===__________________________
Drive: sda _____________________________________________________________________
Disque /dev/sda : 931,5 GiB, 1000204886016 octets, 1953525168 secteurs
Unités : sectors of 1 * 512 = 512 octets
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 1,936,969,727 1,936,967,680 83 Linux
/dev/sda2 1,936,971,774 1,953,523,711 16,551,938 5 Extended
/dev/sda5 1,936,971,776 1,953,523,711 16,551,936 82 Linux swap / Solaris
Drive: sdb _____________________________________________________________________
Disque /dev/sdb : 3,8 GiB, 4016046080 octets, 7843840 secteurs
Unités : sectors of 1 * 512 = 512 octets
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sdb1 * 0 3,035,519 3,035,520 0 Empty
/dev/sdb2 14,432 19,295 4,864 ef EFI (FAT-12/16/32)
/dev/sdb1 overlaps with /dev/sdb2
GUID Partition Table detected, but does not seem to be used.
Partition Attrs Start Sector End Sector # of Sectors System
/dev/sdb1 + R 0 3,035,463 3,035,464 Data partition (Windows/Linux)
/dev/sdb2 + R 14,432 19,295 4,864 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/sda1 e67de868-4c89-4619-a168-a1158e1226f4 ext4
/dev/sda5 a6c82857-1153-4631-ad68-643a2fc7787a swsuspend
/dev/sdb1 2017-02-15-21-44-13-00 iso9660 Ubuntu 16.04.2 LTS amd64
/dev/sdb2 E561-C446 vfat
____________________ "ls -l /dev/disk/by-id" output (filtered) ______________________
total 0
lrwxrwxrwx 1 root root 9 Aug 4 03:15 ata-SAMSUNG_HN-M101MBB_S2R8J1DBA00157 -> ../../sda
lrwxrwxrwx 1 root root 9 Aug 4 03:15 ata-TSSTcorp_CDDVDW_SN-208DB_R8XW6GNC9003CG -> ../../sr0
lrwxrwxrwx 1 root root 9 Aug 4 03:15 usb-JetFlash_Transcend_4GB_X9HXJHVH-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 Aug 4 03:15 wwn-0x50024e9005151e7e -> ../../sda
_________________________ "ls -R /dev/mapper/" output _________________________
None
_________________________=== Boot Files Contents ===___________________________
___________________________ sda1/boot/grub/grub.cfg: ___________________________
File size: 31823, Line count: 707, Menu entries (sub entries included) : 30
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/10_linux ###
--- Notice bisnext removed top of file contents from the report for readability
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-e67de868-4c89-4619-a168-a1158e1226f4' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 e67de868-4c89-4619-a168-a1158e1226f4
else
search --no-floppy --fs-uuid --set=root e67de868-4c89-4619-a168-a1158e1226f4
fi
linux /boot/vmlinuz-4.4.0-87-generic root=UUID=e67de868-4c89-4619-a168-a1158e1226f4 ro quiet splash $vt_handoff
initrd /boot/initrd.img-4.4.0-87-generic
}
--- Notice bisnext removed the submenu section from the report for readability
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry 'Memory test (memtest86+)' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 e67de868-4c89-4619-a168-a1158e1226f4
else
search --no-floppy --fs-uuid --set=root e67de868-4c89-4619-a168-a1158e1226f4
fi
knetbsd /boot/memtest86+.elf
}
menuentry 'Memory test (memtest86+, serial console 115200)' {
insmod part_msdos
insmod ext2
set root='hd0,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,msdos1 --hint-efi=hd0,msdos1 --hint-baremetal=ahci0,msdos1 e67de868-4c89-4619-a168-a1158e1226f4
else
search --no-floppy --fs-uuid --set=root e67de868-4c89-4619-a168-a1158e1226f4
fi
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/30_uefi-firmware ###
### END /etc/grub.d/30_uefi-firmware ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
_________________________ sda1/etc/fstab, Legacy mode: _________________________
UUID=e67de868-4c89-4619-a168-a1158e1226f4 / ext4 errors=remount-ro 0 1
UUID=a6c82857-1153-4631-ad68-643a2fc7787a none swap sw 0 0
____________________________ sda1/etc/default/grub: ____________________________
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=""
===============================================================================
Running System
===============================================================================
______________________________ Kernel parameters ______________________________
file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
______________________________ Boot-up Statistics ______________________________
Startup finished in 18.794s (kernel) + 30.035s (userspace) = 48.829s
blame, first 5:
ubiquity.service 28.541s
dev-sdb.device 2.753s
dev-loop0.device 2.656s
alsa-restore.service 1.791s
ModemManager.service 1.755s
_________________________ RAM usage & Free disk space _________________________
total used free shared buff/cache available
Mem: 15G 1.0G 12G 564M 2.2G 13G
Swap: 0B 0B 0B
Swappiness = 60
Filesystem Mounted on Type Size Used Avail Use% IUse%
aufs / aufs 7.8G 271M 7.6G 4% 1%
/dev/loop0 /rofs squashfs 1.4G 1.4G 0 100% 100%
/dev/sda1 /tmp/bisnext-JGJDSFO1/mnt/sda1 ext4 910G 300G 564G 35% 2%
/dev/sdb /cdrom iso9660 1.5G 1.5G 0 100% -
_______________________________ Wireless Status _______________________________
0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
_______________________________ Modules Loaded _______________________________
Excerpt:
drm 368640 8 i915,drm_kms_helper
drm_kms_helper 167936 1 i915
i2c_algo_bit 16384 1 i915
i915 1310720 114
video 40960 1 i915
______________________________ Additional Drivers _____________________________
== cpu-microcode.py ==
driver : intel-microcode - distro non-free
_____________________________ Upgradable Packages _____________________________
Live Session
________________________ Package Configuration Pending ________________________
None
__________________________ Package Installation Pending _______________________
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 353 not upgraded.
_________________________ Kernel Packages Installed __________________________
Package Version Status
linux-headers-4.8.0-36 4.8.0-36.36~16.04.1 [installed,automatic]
linux-headers-4.8.0-36-generic 4.8.0-36.36~16.04.1 [installed,automatic]
linux-image-4.8.0-36-generic 4.8.0-36.36~16.04.1 [installed,automatic]
linux-image-extra-4.8.0-36-generic 4.8.0-36.36~16.04.1 [installed,automatic]
linux-signed-image-4.8.0-36-generic 4.8.0-36.36~16.04.1 [installed,automatic]
_________________________________ System Logs ________________________________
Failed services:
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.
Selection of relevent log entries:
[ 0.167899] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 2.137758] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
_____________________________________ Xorg ____________________________________
Partial log entries:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 48.863] (--) PCI:*(0:0:2:0) 8086:0166:1558:0240 rev 9, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64, BIOS @ 0x????????/131072
2017-08-04, GPU Manager logs:
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.8.0-36-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.8.0-36-generic/updates/dkms
Is intel loaded? yes
Vendor/Device Id: 8086:166
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-LVDS-1
Number of connected outputs for /dev/dri/card0: 1
Does it require offloading? yes
I couldn't open /var/lib/ubuntu-drivers-common/last_gfx_boot for reading.
Create /var/lib/ubuntu-drivers-common/last_gfx_boot for the 1st time
last cards number = 1
Has intel? yes
How many cards? 1
Has the system changed? Yes
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is mesa enabled? yes
Is mesa egl enabled? yes
Is mesa available? yes
Is mesa egl available? yes
System configuration has changed
Single card detected
Nothing to do
No change - nothing to do
==============================================================================
# in /dev/sda1
==============================================================================
_____________________________ Upgradable Packages _____________________________
No data available.
_________________________ Kernel Packages Installed __________________________
_________________________________ System Logs ________________________________
Selection of relevent log entries:
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4743] error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4743] error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4744] error requesting auth for org.freedesktop.NetworkManager.reload: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4744] error requesting auth for org.freedesktop.NetworkManager.enable-disable-network: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4745] error requesting auth for org.freedesktop.NetworkManager.sleep-wake: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4745] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wifi: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4746] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wwan: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4746] error requesting auth for org.freedesktop.NetworkManager.enable-disable-wimax: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4747] error requesting auth for org.freedesktop.NetworkManager.network-control: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4747] error requesting auth for org.freedesktop.NetworkManager.wifi.share.protected: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4747] error requesting auth for org.freedesktop.NetworkManager.wifi.share.open: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4748] error requesting auth for org.freedesktop.NetworkManager.settings.modify.system: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4750] error requesting auth for org.freedesktop.NetworkManager.settings.modify.own: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4751] error requesting auth for org.freedesktop.NetworkManager.settings.modify.hostname: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:26 <filter> NetworkManager[1107]: <warn> [1501618286.4751] error requesting auth for org.freedesktop.NetworkManager.reload: Authorization check failed: Refusing activation, D-Bus is shutting down.
Aug 1 22:11:28 <filter> dbus[1007]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.nm-dispatcher.service': Refusing activation, D-Bus is shutting down.
Aug 1 22:11:59 <filter> kernel: [58594.436606] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
Aug 1 22:11:59 <filter> kernel: [58594.436690] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.436744] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.436905] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.436957] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.437115] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.437166] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.437325] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.437376] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.437532] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.437583] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.437741] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.437792] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.437949] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.438000] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.438157] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.438208] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.438365] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.438416] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.438573] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.438623] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.438781] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.438832] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.438989] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.439039] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.445074] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.446943] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.452544] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.454280] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.459470] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.461202] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.466293] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.467902] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.472772] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.474388] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.479180] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.480706] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.485293] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.486813] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.491330] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.492776] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.497119] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.498564] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.502848] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.504218] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.508339] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.509714] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.513793] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.515099] res 40/00:00:06:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.519031] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.520335] res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.524272] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.525584] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.529345] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.530593] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.534348] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.535596] res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.539315] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.540513] res 40/00:00:01:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.544113] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.545316] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.548933] ata1.00: failed command: READ FPDMA QUEUED
Aug 1 22:11:59 <filter> kernel: [58594.550093] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.553550] ata1: hard resetting link
Aug 1 22:12:00 <filter> kernel: [58594.920518] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.920538] blk_update_request: I/O error, dev sda, sector 1853884888
Aug 1 22:12:00 <filter> kernel: [58594.922505] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.922520] blk_update_request: I/O error, dev sda, sector 1853884896
Aug 1 22:12:00 <filter> kernel: [58594.924451] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.924466] blk_update_request: I/O error, dev sda, sector 1853884904
Aug 1 22:12:00 <filter> kernel: [58594.926404] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.926418] blk_update_request: I/O error, dev sda, sector 1853884912
Aug 1 22:12:00 <filter> kernel: [58594.928296] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.928310] blk_update_request: I/O error, dev sda, sector 1853884928
Aug 1 22:12:00 <filter> kernel: [58594.930136] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.930148] blk_update_request: I/O error, dev sda, sector 1853884920
Aug 1 22:12:00 <filter> kernel: [58594.931926] sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.931938] blk_update_request: I/O error, dev sda, sector 1853884680
Aug 1 22:12:00 <filter> kernel: [58594.933693] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.933705] blk_update_request: I/O error, dev sda, sector 1853884688
Aug 1 22:12:00 <filter> kernel: [58594.935320] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.935331] blk_update_request: I/O error, dev sda, sector 1853884704
Aug 1 22:12:00 <filter> kernel: [58594.936912] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.936924] blk_update_request: I/O error, dev sda, sector 1853884712
_____________________________________ Xorg ____________________________________
Partial log entries:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 100.112] (--) PCI:*(0:0:2:0) 8086:0166:1558:0240 rev 9, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64
2017-08-01, GPU Manager logs:
log_file: /var/log/gpu-manager.log
last_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
new_boot_file: /var/lib/ubuntu-drivers-common/last_gfx_boot
can't access /run/u-d-c-nvidia-was-loaded file
can't access /run/u-d-c-fglrx-was-loaded file
Looking for fglrx modules in /lib/modules/4.4.0-87-generic/updates/dkms
Looking for nvidia modules in /lib/modules/4.4.0-87-generic/updates/dkms
Is intel loaded? yes
Vendor/Device Id: 8086:166
BusID "PCI:0@0:2:0"
Is boot vga? yes
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Skipping "/dev/dri/card0", driven by "i915"
Found "/dev/dri/card0", driven by "i915"
output 0:
card0-VGA-1
output 1:
card0-LVDS-1
Number of connected outputs for /dev/dri/card0: 2
Does it require offloading? yes
last cards number = 1
Has intel? yes
How many cards? 1
main_arch_path x86_64-linux-gnu, other_arch_path i386-linux-gnu
Current alternative: /usr/lib/x86_64-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/x86_64-linux-gnu/mesa-egl/ld.so.conf
Is mesa enabled? yes
Is mesa egl enabled? yes
Is mesa available? yes
Is mesa egl available? yes
Single card detected
Nothing to do
No change - nothing to do
============================ Disks SMART Attributes ===========================
### ATA disks: sda
# Drive sda:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: SAMSUNG SpinPoint M8 (AF)
Device Model: SAMSUNG HN-M101MBB
Firmware Version: 2AR10001
User Capacity: 1 000 204 886 016 bytes [1,00 TB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 5400 rpm
Form Factor: 2.5 inches
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS T13/1699-D revision 6
SATA Version is: SATA 3.0, 3.0 Gb/s (current: 3.0 Gb/s)
Local Time is: Fri Aug 4 03:31:20 2017 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
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 100 051 - 11740
3 Spin_Up_Time PO---K 089 084 025 - 3462
4 Start_Stop_Count -O--CK 097 097 000 - 3927
9 Power_On_Hours -O--CK 100 100 000 - 13380
11 Calibration_Retry_Count -O--CK 100 100 000 - 436
12 Power_Cycle_Count -O--CK 097 097 000 - 3839
181 Program_Fail_Cnt_Total -O---K 100 100 000 - 2426
191 G-Sense_Error_Rate -O---K 100 100 000 - 111
194 Temperature_Celsius -O---- 064 046 000 - 34 (Min/Max 14/54)
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 133
223 Load_Retry_Count -O--CK 100 100 000 - 436
225 Load_Cycle_Count -O--CK 099 099 000 - 15740
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
SMART Error Log Version: 1
No Errors Logged
### USB disks: sdb
# Drive sdb:
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-4.8.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
Read Device Identity failed: scsi error badly formed scsi parameters
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.
=============================== StdErr Messages ===============================
Failed to probe /dev/sda5 for filesystem type
grub-probe : erreur : impossible de trouver un périphérique GRUB pour /dev/sdb1. Vérifiez device.map..
chroot: impossible d'exécuter la commande «mount»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «mount»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «mount»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «mount»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «mkdir»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «mount»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «lsb_release»: Aucun fichier ou dossier de ce type
chroot: impossible d'exécuter la commande «dpkg»: Aucun fichier ou dossier de ce type
ou bien en ligne :
https://paste.debian.net/979792/
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#6 Le 04/08/2017, à 14:30
- nam1962
Re : Démarrage bloqué
Avec la touche echap ou la touche majuscule au démarrage, as-tu accès au grub ? Si oui essaie de démarrer sur le kernel précédent.
[ Modéré ]
Hors ligne
#7 Le 04/08/2017, à 15:06
- Laurent85
Re : Démarrage bloqué
============================================
# in /dev/sda1
============================================
_________________________________ System LogsSelection of relevent log entries:
...
Aug 1 22:11:59 <filter> kernel: [58594.436606] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
Aug 1 22:11:59 <filter> kernel: [58594.436690] ata1.00: failed command: READ FPDMA QUEUED
...
Aug 1 22:11:59 <filter> kernel: [58594.550093] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.553550] ata1: hard resetting link
Aug 1 22:12:00 <filter> kernel: [58594.920518] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.920538] blk_update_request: I/O error, dev sda, sector 1853884888
Aug 1 22:12:00 <filter> kernel: [58594.922505] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.922520] blk_update_request: I/O error, dev sda, sector 1853884896
Aug 1 22:12:00 <filter> kernel: [58594.924451] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.924466] blk_update_request: I/O error, dev sda, sector 1853884904
Aug 1 22:12:00 <filter> kernel: [58594.926404] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.926418] blk_update_request: I/O error, dev sda, sector 1853884912
Aug 1 22:12:00 <filter> kernel: [58594.928296] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.928310] blk_update_request: I/O error, dev sda, sector 1853884928
Aug 1 22:12:00 <filter> kernel: [58594.930136] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.930148] blk_update_request: I/O error, dev sda, sector 1853884920
Aug 1 22:12:00 <filter> kernel: [58594.931926] sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.931938] blk_update_request: I/O error, dev sda, sector 1853884680
Aug 1 22:12:00 <filter> kernel: [58594.933693] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.933705] blk_update_request: I/O error, dev sda, sector 1853884688
Aug 1 22:12:00 <filter> kernel: [58594.935320] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.935331] blk_update_request: I/O error, dev sda, sector 1853884704
Aug 1 22:12:00 <filter> kernel: [58594.936912] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.936924] blk_update_request: I/O error, dev sda, sector 1853884712
Problème matériel de disque dur, erreurs d'entrée sortie, des secteurs illisible, vois les erreurs enregistrées dans le journal système d'Ubuntu installé sur sda1.
Hors ligne
#8 Le 04/08/2017, à 18:35
- AnatoleD
Re : Démarrage bloqué
Avec la touche echap ou la touche majuscule au démarrage, as-tu accès au grub ? Si oui essaie de démarrer sur le kernel précédent.
J'ai bien accès au grub, mais aucun kernel ne démarre.
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#9 Le 04/08/2017, à 18:37
- AnatoleD
Re : Démarrage bloqué
AnatoleD a écrit :============================================
# in /dev/sda1
============================================
_________________________________ System LogsSelection of relevent log entries:
...
Aug 1 22:11:59 <filter> kernel: [58594.436606] ata1.00: exception Emask 0x0 SAct 0x7fffffff SErr 0x0 action 0x6 frozen
Aug 1 22:11:59 <filter> kernel: [58594.436690] ata1.00: failed command: READ FPDMA QUEUED
...
Aug 1 22:11:59 <filter> kernel: [58594.550093] res 40/00:00:00:4f:c2/00:00:00:00:00/00 Emask 0x4 (timeout)
Aug 1 22:11:59 <filter> kernel: [58594.553550] ata1: hard resetting link
Aug 1 22:12:00 <filter> kernel: [58594.920518] sd 0:0:0:0: [sda] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.920538] blk_update_request: I/O error, dev sda, sector 1853884888
Aug 1 22:12:00 <filter> kernel: [58594.922505] sd 0:0:0:0: [sda] tag#1 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.922520] blk_update_request: I/O error, dev sda, sector 1853884896
Aug 1 22:12:00 <filter> kernel: [58594.924451] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.924466] blk_update_request: I/O error, dev sda, sector 1853884904
Aug 1 22:12:00 <filter> kernel: [58594.926404] sd 0:0:0:0: [sda] tag#3 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.926418] blk_update_request: I/O error, dev sda, sector 1853884912
Aug 1 22:12:00 <filter> kernel: [58594.928296] sd 0:0:0:0: [sda] tag#4 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.928310] blk_update_request: I/O error, dev sda, sector 1853884928
Aug 1 22:12:00 <filter> kernel: [58594.930136] sd 0:0:0:0: [sda] tag#5 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.930148] blk_update_request: I/O error, dev sda, sector 1853884920
Aug 1 22:12:00 <filter> kernel: [58594.931926] sd 0:0:0:0: [sda] tag#6 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.931938] blk_update_request: I/O error, dev sda, sector 1853884680
Aug 1 22:12:00 <filter> kernel: [58594.933693] sd 0:0:0:0: [sda] tag#7 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.933705] blk_update_request: I/O error, dev sda, sector 1853884688
Aug 1 22:12:00 <filter> kernel: [58594.935320] sd 0:0:0:0: [sda] tag#8 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.935331] blk_update_request: I/O error, dev sda, sector 1853884704
Aug 1 22:12:00 <filter> kernel: [58594.936912] sd 0:0:0:0: [sda] tag#9 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
Aug 1 22:12:00 <filter> kernel: [58594.936924] blk_update_request: I/O error, dev sda, sector 1853884712Problème matériel de disque dur, erreurs d'entrée sortie, des secteurs illisible, vois les erreurs enregistrées dans le journal système d'Ubuntu installé sur sda1.
Je veux bien des précisions… Quel log en particulier, pour repérer quel type d'erreur ?… Merci !
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#10 Le 04/08/2017, à 19:19
- nam1962
Re : Démarrage bloqué
Tu as aussi essayé en recovery ?
[ Modéré ]
Hors ligne
#11 Le 04/08/2017, à 19:37
- ??
Re : Démarrage bloqué
Bonjour
Désolé d'être très en retard. Encore des I/O qui vont mal..
Aug 1 22:12:00 <filter> kernel: [58594.920538] blk_update_request: I/O error, dev sda, sector 1853884888
Aug 1 22:12:00 <filter> kernel: [58594.922520] blk_update_request: I/O error, dev sda, sector 1853884896
Aug 1 22:12:00 <filter> kernel: [58594.924466] blk_update_request: I/O error, dev sda, sector 1853884904
Aug 1 22:12:00 <filter> kernel: [58594.926418] blk_update_request: I/O error, dev sda, sector 1853884912
Aug 1 22:12:00 <filter> kernel: [58594.928310] blk_update_request: I/O error, dev sda, sector 1853884928
Aug 1 22:12:00 <filter> kernel: [58594.930148] blk_update_request: I/O error, dev sda, sector 1853884920
Aug 1 22:12:00 <filter> kernel: [58594.931938] blk_update_request: I/O error, dev sda, sector 1853884680
Aug 1 22:12:00 <filter> kernel: [58594.933705] blk_update_request: I/O error, dev sda, sector 1853884688
Aug 1 22:12:00 <filter> kernel: [58594.935331] blk_update_request: I/O error, dev sda, sector 1853884704
Aug 1 22:12:00 <filter> kernel: [58594.936924] blk_update_request: I/O error, dev sda, sector 1853884712
Mais avec un disque qui dit aller très bien.
ID# ATTRIBUTE_NAME FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 100 100 051 - 11740
3 Spin_Up_Time PO---K 089 084 025 - 3462
4 Start_Stop_Count -O--CK 097 097 000 - 3927
9 Power_On_Hours -O--CK 100 100 000 - 13380
11 Calibration_Retry_Count -O--CK 100 100 000 - 436
12 Power_Cycle_Count -O--CK 097 097 000 - 3839
181 Program_Fail_Cnt_Total -O---K 100 100 000 - 2426
191 G-Sense_Error_Rate -O---K 100 100 000 - 111
194 Temperature_Celsius -O---- 064 046 000 - 34 (Min/Max 14/54)
200 Multi_Zone_Error_Rate -O-R-K 100 100 000 - 133
223 Load_Retry_Count -O--CK 100 100 000 - 436
225 Load_Cycle_Count -O--CK 099 099 000 - 15740
No Errors Logged
Ma premier idée serait de changer le branchement du câble au niveau de la carte mère pour prendre un autre port. La seconde idée serait de changer le câble et le lieu de branchement.
=> Mais c'est un portable me semble-t-il. Donc ces deux actions sont moins évidentes.
La troisième idée serait de vérifier si ces secteurs sont toujours illisibles. La quatrième idée serait de demander à anatoleD s'il a bien pensé à sauvegarder ses données personnelles car on risque de se diriger vers un remplacement du disque. Si la réponse est "OUI", on essayera de savoir combien de secteurs sont actuellement illisibles sur la totalité du disque. Ce qui permettra de faire un choix de réinstallation de ubuntu sur ce disque ou sur un neuf.
Si la réponse est NON, cela sera du ddrescue avec duplication de ce qui reste accessible
Dernière modification par ?? (Le 04/08/2017, à 19:47)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#12 Le 04/08/2017, à 20:17
- AnatoleD
Re : Démarrage bloqué
Merci des retours et des idées.
Oui c'est un portable, mais fabriqué par un assembleur (le regretté antibug computer), donc il y a moyen d'y mettre les doigts. Je ferme cette session live et je regarde...
Je n'ai pas bien compris la troisième idée…
L'essentiel de mes données est sauvegardé dans une dropbox, mais j'ai qqs vieux fichiers ou grosses vidéos sur le dd que je vais tâcher de récupérer.
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#13 Le 04/08/2017, à 21:18
- nam1962
Re : Démarrage bloqué
Je n'avais pas pigé que tu étais en live
Redémarre en live et ouvre le terminal, puis
sudo fsck -fy /dev/sda1
Réponds Y a toute demande complémentaire (ça ne devrait pas avec le y) et repasse la commande si il y a des erreurs
Puis
reboot
Dernière modification par nam1962 (Le 04/08/2017, à 21:19)
[ Modéré ]
Hors ligne
#14 Le 04/08/2017, à 22:29
- AnatoleD
Re : Démarrage bloqué
Redémarre en live et ouvre le terminal, puis
sudo fsck -fy /dev/sda1
Bigre...
ubuntu@ubuntu:~$ sudo fsck -fy /dev/sda1
fsck de util-linux 2.27.1
e2fsck 1.42.13 (17-May-2015)
/dev/sda1 est monté.
e2fsck: Ne peut continuer, arrêt immédiat.ubuntu@ubuntu:~$
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#15 Le 04/08/2017, à 22:38
- nam1962
Re : Démarrage bloqué
Et :
sudo umount /dev/sda1
sudo fsck -fy /dev/sda1
[ Modéré ]
Hors ligne
#16 Le 04/08/2017, à 22:57
- ??
Re : Démarrage bloqué
J'ai noté "L'essentiel de mes données est sauvegardé"
Pour vérifier si le problème du 1 aout à 22 heures 12 était temporaire ou définitif:
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884888
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884896
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884904
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884912
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884928
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884920
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884680
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884688
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884704
sudo dd if=/dev/sda of=/dev/null count=1 bs=512 skip=1853884712
Puis voir ce que le firmware du disque en a pensé.
sudo smartctl -A /dev/sda
Au besoin tu peux compléter par
sudo sudo fdisk -l | grep sda
Afin de partir à la recherche du fichier qui est hébergé par ces secteurs. Cela pourrait alors donner une idée précise sur la cause du non démarrage.
Nota: Ces actions sont compatibles avec la commande de réparation de la partition.
Dernière modification par ?? (Le 04/08/2017, à 23:23)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#17 Le 05/08/2017, à 06:26
- AnatoleD
Re : Démarrage bloqué
Et :
sudo umount /dev/sda1 sudo fsck -fy /dev/sda1
Pas mieux : toujours "kernel panic" au reboot.
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#18 Le 05/08/2017, à 06:33
- AnatoleD
Re : Démarrage bloqué
sudo smartctl -A /dev/sda
ubuntu@ubuntu:~$ sudo smartctl -A /dev/sda
smartctl 6.5 2016-01-24 r4214 [x86_64-linux-4.8.0-36-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org=== START OF READ SMART DATA SECTION ===
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 051 Pre-fail Always - 11741
2 Throughput_Performance 0x0026 252 252 000 Old_age Always - 0
3 Spin_Up_Time 0x0023 089 084 025 Pre-fail Always - 3452
4 Start_Stop_Count 0x0032 097 097 000 Old_age Always - 3935
5 Reallocated_Sector_Ct 0x0033 252 252 010 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 252 252 051 Old_age Always - 0
8 Seek_Time_Performance 0x0024 252 252 015 Old_age Offline - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 13384
10 Spin_Retry_Count 0x0032 252 252 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 100 000 Old_age Always - 436
12 Power_Cycle_Count 0x0032 097 097 000 Old_age Always - 3847
181 Program_Fail_Cnt_Total 0x0022 100 100 000 Old_age Always - 2426
191 G-Sense_Error_Rate 0x0022 100 100 000 Old_age Always - 111
192 Power-Off_Retract_Count 0x0022 252 252 000 Old_age Always - 0
194 Temperature_Celsius 0x0002 062 046 000 Old_age Always - 38 (Min/Max 14/54)
195 Hardware_ECC_Recovered 0x003a 100 100 000 Old_age Always - 0
196 Reallocated_Event_Count 0x0032 252 252 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 252 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 252 252 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0036 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x002a 100 100 000 Old_age Always - 133
223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 436
225 Load_Cycle_Count 0x0032 099 099 000 Old_age Always - 15752
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#19 Le 05/08/2017, à 06:35
- AnatoleD
Re : Démarrage bloqué
Au besoin tu peux compléter par
sudo sudo fdisk -l | grep sda
Afin de partir à la recherche du fichier qui est hébergé par ces secteurs. Cela pourrait alors donner une idée précise sur la cause du non démarrage.
ubuntu@ubuntu:~$ sudo sudo fdisk -l | grep sda
Disque /dev/sda : 931,5 GiB, 1000204886016 octets, 1953525168 secteurs
/dev/sda1 * 2048 1936969727 1936967680 923,6G 83 Linux
/dev/sda2 1936971774 1953523711 16551938 7,9G 5 Étendue
/dev/sda5 1936971776 1953523711 16551936 7,9G 82 partition d'échange Linux / Solaris
ubuntu@ubuntu:~$
Ubuntu 21.10 – Gnome 40.4.0 Wayland
Intel® Core™ i7-3610QM CPU @ 2.30GHz × 8
Intel® Ivybridge Mobile
Hors ligne
#20 Le 05/08/2017, à 09:03
- moko138
Re : Démarrage bloqué
Et :
sudo umount /dev/sda1 sudo fsck -fy /dev/sda1
Attention !
Quand la dégradation matérielle du disque empêche de trouver certains fichiers (c'est le cas ici) il faut sauvegarder les données lisibles AVANT le fsck.
Car un fsck appliqué à un disque matériellement dégradé risque d'accentuer la difficulté de récupération des données.
D'une part, cf. ht tp://www.thouvest.ovh/pages/hdd_defectueux/ thouvest.ovh/pages/hdd_defectueux/ à partir de "Évitez impérativement l'utilisation". (Tout en gardant à l'esprit que cette page de thouvest.ovh date beaucoup).
D'autre part, en ext4 (postérieur à cette page de thouvest.ovh), fsck s'appuie sur le journal, et quand le journal est dans une partie matériellement dégradée du disque, fsck ajoute tout simplement une sur-dégradation logicielle...
%NOINDEX%
Un utilitaire précieux : ncdu
Photo, mini-tutoriel : À la découverte de dcraw
Hors ligne
#21 Le 05/08/2017, à 14:20
- nam1962
Re : Démarrage bloqué
Wi, mais le disque "malade" qui demandait poliment un fsck (#1) s'est déjà vu coller un PPA (bisnext), un tmp (bisnext), des installs (bisnext, smartmontools...) et compagnie.
Sur le principe ok, mais vu le bazar déjà déclenché...
[ Modéré ]
Hors ligne
#22 Le 05/08/2017, à 16:52
- Saidouch
Re : Démarrage bloqué
Bonjour j'ai aussi un soucis de démarrage avec mon ordi je comprend rien y'as des lignes de commande qui commence par initramfs... Help !!!
Hors ligne
#23 Le 06/08/2017, à 17:43
- ??
Re : Démarrage bloqué
Wi, mais le disque "malade" qui demandait poliment un fsck (#1) s'est déjà vu coller un PPA (bisnext), un tmp (bisnext), des installs (bisnext, smartmontools...) et compagnie.
Sur le principe ok, mais vu le bazar déjà déclenché...
Cela suffit, Bonhomme. Arrêtes de délirer.
Il y a quelqu'un qui a décidé de lancer une opération fsck sur ce disque avant de s'assurer que le disque était en état de supporter "cette opération du petit doigt". Il n'a même pas pris la précaution de regarder la tension du malade, Ce qui est moins compliqué qu'une "coloscopie".
Alors que d'autres intervenants ont agit avec masque de décontamination.
===============================================================================
Running System
===============================================================================
______________________________ Kernel parameters ______________________________
file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
Dernière modification par ?? (Le 06/08/2017, à 17:49)
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#24 Le 06/08/2017, à 17:55
- ??
Re : Démarrage bloqué
Bonjour j'ai aussi un soucis de démarrage avec mon ordi je comprend rien y'as des lignes de commande qui commence par initramfs... Help !!!
Bonjour.
Il serait préférable que tu ouvres une nouvelle discussion.
Tu auras deux équipes qui manifestement n'ont pas la même approche du problème de initramfs.
Une photo postée sur http://www.hostingpics.net (car actuellement le forum ubuntu n'accepte pas d'héberger des photos ==> il n'y a pas d'onglets) de ton message d'erreur peut aider.
Utiliser REFIND au lieu du GRUB https://doc.ubuntu-fr.org/refind . Aidez à vous faire dépanner en suivant le guide et en utilisant les outils de diagnostic J'ai perdu ma gomme. Désolé pour les fautes d'orthographes non corrigées.
Hors ligne
#25 Le 06/08/2017, à 18:02
- nam1962
Re : Démarrage bloqué
Un disque est mort ou capable de récupérer ses erreurs (enfin c'est ce que j'ai stupidement retenu de ma prod en environnement sensible).
Je te regarde, grand chirurgien (en espérant que ce ne soit pas juste légiste..)
[ Modéré ]
Hors ligne