#1 Le 02/08/2017, à 19:05
- pitufo64
Message Grub-rescue [RESOLU]
Bonsoir à toutes et à tous,
Sur mon pc qui était sous windows vista, j'avais installé seven. Par la suite j'ai découvert Ubuntu, l'ai installé en dual-boot et adopté.
Malheureusement, en démarrant mon pc, j'ai sélectionné la mauvaise option de démarrage (windows recovery environnement). J'ai choisi l'option "quitter" mais depuis je n'ai qu'un message pour grub-rescue. J'ai parcouru le forum, mais j'ai lu que Boot repair disk ne fonctionné plus (ou mal) depuis Ubuntu 16.04. Voici le rapport boot-info : http://paste.ubuntu.com/25227520/
Je vous remercie d'avance pour votre aide.
Dernière modification par pitufo64 (Le 04/08/2017, à 10:49)
Hors ligne
#2 Le 03/08/2017, à 21:58
- pitufo64
Re : Message Grub-rescue [RESOLU]
Bonsoir, je pense avoir mal compris lorsque j'ai lu que boot-repair ne fonctionnait plus sur Ubuntu 16.04 lts. J'ai donc fais (laissé faire plutôt) les réparations recommandées mais je tombe toujours sur grub-rescue au démarrage. Cela dit, j'ai maintenant un autre rapport qui, je l’espère, permettra à quelqu'un de m'aider. Le voici : http://paste.ubuntu.com/25234995
Merci.
Hors ligne
#3 Le 03/08/2017, à 22:15
- ??
Re : Message Grub-rescue [RESOLU]
Bonsoir.
Peux-tu faire un rapport bisnext car je pense que ton outil de réparation ne sait pas reconnaitre ubuntu qui me semble présent dans la partition SDA4 et non plus dans la partition SDA6 https://doc.ubuntu-fr.org/bisnext
De plus ton boot-info donne un contenu qui n'est pas du tout sérieux. Mais tu n'y es pour rien.
Pour t'expliquer un peu, Le contenu du MBR qui commande le boot
============================= Boot Info Summary: ===============================
=> 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 (,msdos6)/boot/grub. It also embeds following components:
=indique qu'il faut booter avec la partition msdos6 soit la 6eme mais elle n'existe pas. Tu ne peux donc pas booter
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 63 20,980,889 20,980,827 27 Hidden NTFS (Recovery Environment)
/dev/sda2 * 20,981,760 148,585,184 127,603,425 7 NTFS / exFAT / HPFS
/dev/sda3 148,586,494 187,647,999 39,061,506 5 Extended
/dev/sda5 181,506,048 187,647,999 6,141,952 82 Linux swap / Solaris
/dev/sda4 187,648,000 488,396,799 300,748,800 83 LinuxOr il y en a une en position 4 qui est notée linux. qui pourrait probablement convenir .
Mais Il faut croire que c'est trop compliqué pour ces deux outils de lister le répertoire grub
Soit le répertoire n'existe plus, soit ils se trompent. C'est pour cela que je demande un second avis car pour pour moi, il y a des choses cette partition N° 4
=================== df -Th:
Filesystem Type Size Used Avail Use% Mounted on
/dev/sda4 ext4 142G 17G 117G 13% /mnt/boot-sav/sda4Si tu n'as pas trop de temps à perdre une nouvelle installation de ubuntu se fait en 1 heure.
Dernière modification par ?? (Le 03/08/2017, à 22:36)
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
#4 Le 03/08/2017, à 22:56
- pitufo64
Re : Message Grub-rescue [RESOLU]
Bonsoir et merci pour ton aide. (c'est bizarre mais certains messages ont disparus)
Si une nouvelle installation d'Ubuntu est suffisante, c'est pas un problème. Mais, quand sera-t-il de mon windows ? Mes données seront elles perdues ? Sinon voici le rapport demandé mais je ne suis pas sur de l'avoir correctement posté.
Aug 3, 2017, bisnext report id 21bbf
=== 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 ======================
Resuming in non X mode: glxinfo not found. For package install advice run: inxi --recommends
System: Kernel: 4.8.0-36-generic i686 (32 bit gcc: 5.4.0)
Console: tty 4 dm: lightdm Distro: Ubuntu 16.04.2 LTS
Machine: Device: other-vm? System: eMachines product: eMachines E525 v: V1.03
Mobo: eMachines model: eMachines E525 v: V1.03
BIOS: eMachines v: V1.03 date: 03/11/2009
CPU: Single core Intel Celeron 900 (-UP-) cache: 1024 KB
flags: (lm nx pae sse sse2 sse3 ssse3) bmips: 4389 speed: 2194 MHz (max)
Memory: Array-1 capacity: 4 GB (check) devices: 2 EC: None
max module size: 2 GB
Device-1: DIMM0 size: 2 GB (Single-bank) speed: 667 MHz type: DDR2
manufacturer: Samsung part: 3C3C3C3C3C3C3C3C3C3C3C3C3C3C3C3C3C3C
Device-2: DIMM2 size: 1 GB (Single-bank) speed: 667 MHz type: DDR2
manufacturer: Micron part: 474747474747474747474747474747474747
Graphics: Card: Intel Mobile 4 Series Integrated Graphics Controller
bus-ID: 00:02.0 chip-ID: 8086:2a42
Display Server: X.org 1.18.4 drivers: modesetting (unloaded: fbdev,vesa)
tty size: 80x24
Audio: Card Intel 82801I (ICH9 Family) HD Audio Controller
driver: snd_hda_intel bus-ID: 00:1b.0 chip-ID: 8086:293e
Sound: Advanced Linux Sound Architecture v: k4.8.0-36-generic
Network: Card-1: Qualcomm Atheros AR242x / AR542x Wireless Network Adapter (PCI-Express)
driver: ath5k bus-ID: 04:00.0 chip-ID: 168c:001c
IF: wlp4s0 state: up mac: <filter>
Card-2: Qualcomm Atheros AR8132 Fast Ethernet
driver: atl1c v: 1.0.1.1-NAPI port: 1000
bus-ID: 05:00.0 chip-ID: 1969:1062
IF: enp5s0 state: down mac: <filter>
Drives: HDD Total Size: 258.1GB (1.2% used)
ID-1: /dev/sda model: TOSHIBA_MK2555GS size: 250.1GB
ID-2: USB /dev/sdb model: USB_DISK_2.0 size: 8.0GB
Optical-1: /dev/sr0 model: Optiarc DVD RW AD-7580S
rev: FX04 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
Partition: ID-1: swap-1 size: 3.14GB used: 0.00GB (0%) fs: swap dev: /dev/sda5
label: N/A uuid: a9e3d5e4-7cb0-48ab-8d2f-837d7ef75ef7
RAID: System: supported: N/A
No RAID devices: /proc/mdstat, md_mod kernel module present
Unused Devices: none
Sensors: None detected - is lm-sensors installed and configured?
Repos: Active apt sources in file: /etc/apt/sources.list
deb cdrom:[Ubuntu 16.04.2 LTS _Xenial Xerus_ - Release i386 (20170215.2)]/ xenial main restricted
deb http://archive.ubuntu.com/ubuntu/ xenial main restricted
deb http://security.ubuntu.com/ubuntu/ xenial-security main restricted
deb http://archive.ubuntu.com/ubuntu/ xenial-updates main restricted
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: 2.0% command: compiz pid: 4399 mem: 86.91MB (2.9%)
2: cpu: 1.4% command: Xorg pid: 3930 mem: 41.91MB (1.4%)
3: cpu: 1.0% command: init pid: 1 mem: 5.14MB (0.1%)
4: cpu: 0.8% command: nm-applet pid: 4371 mem: 54.02MB (1.8%)
5: cpu: 0.6% command: bisnext (started by: bash) pid: 9141 mem: 3.75MB (0.1%)
Info: Processes: 198 Uptime: 12 min Memory: 482.8/2957.3MB
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:Windows Recovery Environment (loader):Windows:chain
/dev/sda2:Windows 7 (loader):Windows1:chain========================= 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 (,msdos6)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
=> ISOhybrid (Syslinux 4.05 and higher) is installed in the MBR of /dev/sdb.
sda1: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows Vista: NTFS
Boot sector info:
Operating System:
Boot files: /BOOTMGR /BOOT/BCD /Windows/System32/winload.exe
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 7/2008: NTFS
Boot sector info:
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exe
_________________________=== Drive/Partition Info ===__________________________
Drive: sda _____________________________________________________________________
Disque /dev/sda : 232,9 GiB, 250059350016 octets, 488397168 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 63 20,980,889 20,980,827 27 Hidden NTFS (Recovery Environment)
/dev/sda2 * 20,981,760 148,585,184 127,603,425 7 NTFS / exFAT / HPFS
/dev/sda3 148,586,494 187,647,999 39,061,506 5 Extended
/dev/sda5 181,506,048 187,647,999 6,141,952 82 Linux swap / Solaris
/dev/sda4 187,648,000 488,396,799 300,748,800 83 Linux
Drive: sdb _____________________________________________________________________
Disque /dev/sdb : 7,5 GiB, 8004829184 octets, 15634432 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 * 64 3,068,159 3,068,096 17 Hidden NTFS / HPFS
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/loop0 squashfs
/dev/sda1 04EC05BAEC05A750 ntfs PQSERVICE
/dev/sda2 661C9E3F1C9E09E7 ntfs
/dev/sda4 0f54ea16-94bd-4b28-9fff-51094b7b2c21 ext4
/dev/sda5 a9e3d5e4-7cb0-48ab-8d2f-837d7ef75ef7 swap
/dev/sdb1 2017-02-15-21-46-36-00 iso9660 Ubuntu 16.04.2 LTS i386
____________________ "ls -l /dev/disk/by-id" output (filtered) ______________________
total 0
lrwxrwxrwx 1 root root 9 Aug 3 20:22 ata-Optiarc_DVD_RW_AD-7580S_30656330_2021922Q112 -> ../../sr0
lrwxrwxrwx 1 root root 9 Aug 3 20:22 ata-TOSHIBA_MK2555GSX_49LRT36BT -> ../../sda
lrwxrwxrwx 1 root root 9 Aug 3 20:22 usb-_USB_DISK_2.0_079C0702BB4E0B0A-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 Aug 3 20:22 wwn-0x50000391b1d04c24 -> ../../sda
_________________________ "ls -R /dev/mapper/" output _________________________
None===============================================================================
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 24.712s (kernel) + 50.048s (userspace) = 1min 14.760s
blame, first 5:
ubiquity.service 46.958s
dev-loop0.device 7.338s
dev-sda5.device 6.714s
dev-sdb.device 6.380s
console-setup.service 4.692s
_________________________ RAM usage & Free disk space _________________________
total used free shared buff/cache available
Mem: 2.9G 414M 1.1G 318M 1.4G 1.9G
Swap: 2.9G 0B 2.9G
Swappiness = 60
Filesystem Mounted on Type Size Used Avail Use% IUse%
aufs / aufs 1.5G 95M 1.4G 7% 1%
/dev/loop0 /rofs squashfs 1.5G 1.5G 0 100% 100%
/dev/sdb /cdrom iso9660 1.5G 1.5G 0 100% -
_______________________________ Wireless Status _______________________________
0: acer-wireless: Wireless LAN
Soft blocked: no
Hard blocked: no
1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
_______________________________ Modules Loaded _______________________________
Excerpt:
drm 311296 6 i915,drm_kms_helper
drm_kms_helper 151552 1 i915
i2c_algo_bit 16384 1 i915
i915 1245184 84
video 36864 2 acer_wmi,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 351 not upgraded.
__________________ Configuration files of uninstalled packages: ________________
Package Version
myspell-es 1.11-14
_________________________ 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]
_________________________________ 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.093023] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.132129] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug
[ 0.354496] acpi PNP0A08:00: _OSC failed (AE_NOT_FOUND); disabling ASPM
[ 0.354501] acpi PNP0A08:00: [Firmware Info]: MMCONFIG for domain 0000 [bus 00-3f] only partially covers this bridge
[ 0.732198] pci 0000:05:00.0: [Firmware Bug]: VPD access disabled
[ 71.730183] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe A FIFO underrun
_____________________________________ Xorg ____________________________________
Partial log entries:
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 74.788] (--) PCI:*(0:0:2:0) 8086:2a42:1025:0212 rev 9, Mem @ 0xd0000000/4194304, 0xc0000000/268435456, I/O @ 0x000050f0/8, BIOS @ 0x????????/131072
[ 74.788] (--) PCI: (0:0:2:1) 8086:2a43:1025:0212 rev 9, Mem @ 0xd3400000/1048576
2017-08-03, 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:2a42
BusID "PCI:0@0:2:0"
Is boot vga? yes
Vendor/Device Id: 8086:2a43
BusID "PCI:0@0:2:1"
Error: can't access /sys/bus/pci/devices/0000:00:02.1/driver
The device is not bound to any driver. Skipping...
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 i386-linux-gnu, other_arch_path x86_64-linux-gnu
Current alternative: /usr/lib/i386-linux-gnu/mesa/ld.so.conf
Current core alternative: (null)
Current egl alternative: /usr/lib/i386-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============================ Disks SMART Attributes ===========================
### ATA disks: sda
# Drive sda:
smartctl 6.6 2016-05-31 r4324 [i686-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: Toshiba 2.5" HDD MK..55GSX
Device Model: TOSHIBA MK2555GSX
Firmware Version: FG001J
User Capacity: 250 059 350 016 bytes [250 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA8-ACS (minor revision not indicated)
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Thu Aug 3 20:34:32 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
3 Spin_Up_Time POS--K 100 100 001 - 1004
4 Start_Stop_Count -O--CK 100 100 000 - 4111
9 Power_On_Hours -O--CK 078 078 000 - 9119
12 Power_Cycle_Count -O--CK 100 100 000 - 3909
191 G-Sense_Error_Rate -O--CK 100 100 000 - 224
192 Power-Off_Retract_Count -O--CK 100 100 000 - 52
193 Load_Cycle_Count -O--CK 092 092 000 - 89862
194 Temperature_Celsius -O---K 100 100 000 - 40 (Min/Max 6/55)
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 1
220 Disk_Shift -O---- 100 100 000 - 53
222 Loaded_Hours -O--CK 084 084 000 - 6579
226 Load-in_Time -OS--K 100 100 000 - 340
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning
SMART Error Log Version: 1
ATA Error Count: 4
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 4 occurred at disk power-on lifetime: 3407 hours (141 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 52 4f 19 68 6f Error: WP at LBA = 0x0f68194f = 258480463
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 c8 10 e8 ee 9f 40 00 00:17:43.558 WRITE FPDMA QUEUED
61 20 f0 a0 d6 a4 40 00 00:17:43.556 WRITE FPDMA QUEUED
61 08 e8 b0 01 91 40 00 00:17:43.556 WRITE FPDMA QUEUED
60 0d e0 bb 4d 5e 40 00 00:17:43.556 READ FPDMA QUEUED
60 30 d8 5a 75 43 40 00 00:17:43.556 READ FPDMA QUEUED
Error 3 occurred at disk power-on lifetime: 3407 hours (141 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 d2 4f 19 68 6f Error: UNC at LBA = 0x0f68194f = 258480463
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 2e d0 28 19 68 40 00 00:17:39.190 READ FPDMA QUEUED
60 08 b8 38 56 a2 40 00 00:17:39.190 READ FPDMA QUEUED
60 08 a8 d8 6c a1 40 00 00:17:39.190 READ FPDMA QUEUED
61 10 a0 b0 75 e7 40 00 00:17:39.190 WRITE FPDMA QUEUED
60 18 98 70 20 0c 40 00 00:17:39.190 READ FPDMA QUEUED
Error 2 occurred at disk power-on lifetime: 3407 hours (141 days + 23 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 41 22 4f 19 68 6f Error: UNC at LBA = 0x0f68194f = 258480463
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
60 2e 20 28 19 68 40 00 00:17:34.833 READ FPDMA QUEUED
60 08 18 b0 07 19 40 00 00:17:34.817 READ FPDMA QUEUED
60 0b 10 70 8d d6 40 00 00:17:34.775 READ FPDMA QUEUED
60 2d 08 b0 cb 42 40 00 00:17:34.730 READ FPDMA QUEUED
60 20 f8 20 a7 43 40 00 00:17:34.711 READ FPDMA QUEUED
Error 1 occurred at disk power-on lifetime: 3297 hours (137 days + 9 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
84 41 08 ff 1b 85 60 Error: ICRC, ABRT at LBA = 0x00851bff = 8723455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
61 40 10 00 1c 85 40 00 00:11:16.745 WRITE FPDMA QUEUED
61 20 08 e0 1b 85 40 00 00:11:16.745 WRITE FPDMA QUEUED
61 40 f8 a0 1b 85 40 00 00:11:16.745 WRITE FPDMA QUEUED
60 40 e8 40 76 40 40 00 00:11:16.392 READ FPDMA QUEUED
60 20 e0 00 76 40 40 00 00:11:16.392 READ FPDMA QUEUED
### USB disks: sdb
# Drive sdb:
smartctl 6.6 2016-05-31 r4324 [i686-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 unsupported scsi opcode
A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options.Hors ligne
#5 Le 04/08/2017, à 00:44
- ??
Re : Message Grub-rescue [RESOLU]
Lui non plus ne trouve rien.
Comme tu dis que ce n'est pas un gros problème, le plus simple est de refaire une installation.
Ne te trompes pas en écrasant windows qui est bien resté présent.
sda2: __________________________________________________________________________
File system: ntfs
Boot sector type: Windows 7/2008: NTFS
Boot sector info:
Operating System:
Boot files: /bootmgr /Boot/BCD /Windows/System32/winload.exeDernière modification par ?? (Le 04/08/2017, à 00:44)
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
#6 Le 04/08/2017, à 10:47
- pitufo64
Re : Message Grub-rescue [RESOLU]
Merci ?? (ça fait bizarre mais ce n'est pas une question !!)
Je vais donc ré-installer Ubuntu. J'ai maintenant un doute concernant l'emplacement pour la ré-installation mais je vais ouvrir un autre sujet et marquer celui là en résolu. Encore merci.
Hors ligne