#1 Le 06/12/2019, à 12:26
- david69
/dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
bonjour,
le pc d'une cousine sur lequel j'avais installe une Lubuntu 16.04 voila quelque temps faisait son taf jusqu'a recemment ou est apparu au moment du demarrage un message du type:
jjjjjjjjjjjjjjjjjjjjjjjjj /dev/sda1: clean, ***/**** files, *****/**** blocks jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
accompagne d'un son strident.
je me suis dit "sans doute un probleme de mis a jour".
comme je suis bourin, j'ai reinstalle une Lubuntu 18.04 mais le probleme persiste.
avant de rincer, j'ai cherche d'ou provenait le probleme mais rien ne m'inspirait.
avec la 18.04, comme je n'ai plus rien a perdre, j'ai essaye des trucs mais je dois dire en aveugle.
probleme nvidia?
https://munix.dk/fix-boot-hangs-devsda1 … les-blocks
https://www.cnblogs.com/klcf0220/p/11359701.html
un truc dans le grub?
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
to
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash fastboot"
comme ici:
https://forum.ubuntu.org.cn/viewtopic.php?t=480912
ou encore dans le fstab
https://stackoverflow.com/questions/431 … ing-system
enfin bref, je pourrais encore allonger la liste.
ca manque de methode et c'est pourquoi je pose la question: par quel bout commencer?
Hors ligne
#2 Le 06/12/2019, à 12:31
- malbo
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Bonjour,
Je te propose de vérifier le disque dur depuis une session live de Ubuntu : https://forum.ubuntu-fr.org/viewtopic.php?id=1988280
Hors ligne
#3 Le 06/12/2019, à 13:01
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
bonjour et merci
le retour de smartctl sur l'unique disque sda est:
brigitte@brigitte:~$ sudo smartctl -a /dev/sda
smartctl 6.6 2016-05-31 r4324 [x86_64-linux-5.0.0-37-generic] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Seagate Momentus 7200.4
Device Model: ST9500420AS
Serial Number: 5VJ4S6S6
LU WWN Device Id: 5 000c50 02438e51d
Firmware Version: 0006HPM1
User Capacity: 500107862016 bytes [500 GB]
Sector Size: 512 bytes logical/physical
Rotation Rate: 7200 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 4
SATA Version is: SATA 2.6, 3.0 Gb/s
Local Time is: Fri Dec 6 11:53:55 2019 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
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: ( 0) 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: ( 109) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 117 099 006 Pre-fail Always - 163640372
3 Spin_Up_Time 0x0002 098 097 000 Old_age Always - 0
4 Start_Stop_Count 0x0033 099 099 000 Pre-fail Always - 1982
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 41258777
9 Power_On_Hours 0x0032 099 099 000 Old_age Always - 1409
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0033 099 037 020 Pre-fail Always - 1963
183 Runtime_Bad_Block 0x0032 100 253 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 - 0
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 288
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 068 052 045 Old_age Always - 32 (Min/Max 30/32)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 3
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 8
193 Load_Cycle_Count 0x0032 087 087 000 Old_age Always - 27239
194 Temperature_Celsius 0x0022 032 048 000 Old_age Always - 32 (0 15 0 0 0)
195 Hardware_ECC_Recovered 0x001a 048 043 000 Old_age Always - 163640372
196 Reallocated_Event_Count 0x0033 100 100 036 Pre-fail Always - 0
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
254 Free_Fall_Sensor 0x0032 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.
brigitte@brigitte:~$
Hors ligne
#4 Le 06/12/2019, à 13:18
- malbo
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
selon moi, ce disque dur est en pleine forme. C'était une fausse piste.
Hors ligne
#5 Le 06/12/2019, à 13:19
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
pas de probleme, au moins on sait que ce n'est pas lui.
Hors ligne
#6 Le 06/12/2019, à 14:14
- malbo
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Je te prie de faire un Boot-info et de donner l'URL de ce Boot-info dans ta réponse.
Hors ligne
#7 Le 06/12/2019, à 14:34
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
voila le lien:
http://paste.ubuntu.com/p/gxxDmHBk4Z/
pas mal cet outil de diagnostique.
Hors ligne
#8 Le 06/12/2019, à 15:29
- geole
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
bonjour,
jusqu'a recemment ou est apparu au moment du demarrage un message du type:
jjjjjjjjjjjjjjjjjjjjjjjjj /dev/sda1: clean, ***/**** files, *****/**** blocks jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
accompagne d'un son strident.ca manque de methode et c'est pourquoi je pose la question: par quel bout commencer?
Bonjour.
Le premier message que tu indiques est nornal car l'O.S. controle systematiquement l'état du disque en le traçant. On a vu que l'état du disque est bon.
C'est le son strident qui est anormal. Que donne le retour de cette commande.
journalctl -p err
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#9 Le 06/12/2019, à 15:55
- malbo
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Le Boot-info dont tu as donné le lien ( http://paste.ubuntu.com/p/gxxDmHBk4Z/ ) dans le post #7 est là :
Boot Info Script 8f991e4 + Boot-Repair extra info [Boot-Info 25oct2017]
============================= 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 (,msdos1)/boot/grub. It also embeds following components:
modules
---------------------------------------------------------------------------
fshelp ext2 part_msdos biosdisk
---------------------------------------------------------------------------
sda1: __________________________________________________________________________
File system: ext4
Boot sector type: -
Boot sector info:
Operating System: Ubuntu 18.04.3 LTS
Boot files: /boot/grub/grub.cfg /etc/fstab
/boot/grub/i386-pc/core.img
============================ Drive/Partition Info: =============================
Drive: sda _____________________________________________________________________
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: dos
Partition Boot Start Sector End Sector # of Sectors Id System
/dev/sda1 * 2,048 976,771,071 976,769,024 83 Linux
"blkid" output: ________________________________________________________________
Device UUID TYPE LABEL
/dev/sda1 78f9d251-8e31-48a1-923f-b1a37316fe2e ext4
========================= "ls -l /dev/disk/by-id" output: ======================
total 0
lrwxrwxrwx 1 root root 9 Dec 6 13:31 ata-ST9500420AS_5VJ4S6S6 -> ../../sda
lrwxrwxrwx 1 root root 10 Dec 6 13:31 ata-ST9500420AS_5VJ4S6S6-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Dec 6 11:47 ata-hp_DVDRAM_GT30L_M36A21I1007 -> ../../sr0
lrwxrwxrwx 1 root root 9 Dec 6 13:30 usb-Generic-_Multi-Card_20071114173400000-0:0 -> ../../sdb
lrwxrwxrwx 1 root root 9 Dec 6 13:31 wwn-0x5000c5002438e51d -> ../../sda
lrwxrwxrwx 1 root root 10 Dec 6 13:31 wwn-0x5000c5002438e51d-part1 -> ../../sda1
================================ Mount points: =================================
Device Mount_Point Type Options
/dev/sda1 / ext4 (rw,relatime,errors=remount-ro)
=========================== sda1/boot/grub/grub.cfg: ===========================
--------------------------------------------------------------------------------
#
# 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/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function recordfail {
set recordfail=1
if [ -n "${have_grubenv}" ]; then if [ -z "${boot_once}" ]; then save_env recordfail; fi; fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=fr_FR
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=30
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=hidden
set timeout=0
# Fallback hidden-timeout code in case the timeout_style feature is
# unavailable.
elif sleep --interruptible 0 ; then
set timeout=0
fi
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###
### BEGIN /etc/grub.d/10_linux ###
function gfxmode {
set gfxpayload="${1}"
if [ "${1}" = "keep" ]; then
set vt_handoff=vt.handoff=1
else
set vt_handoff=
fi
}
if [ "${recordfail}" != 1 ]; then
if [ -e ${prefix}/gfxblacklist.txt ]; then
if hwmatch ${prefix}/gfxblacklist.txt 3; then
if [ ${match} = 0 ]; then
set linux_gfx_mode=keep
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=text
fi
else
set linux_gfx_mode=keep
fi
else
set linux_gfx_mode=text
fi
export linux_gfx_mode
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-78f9d251-8e31-48a1-923f-b1a37316fe2e' {
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
fi
linux /boot/vmlinuz-5.0.0-37-generic root=UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e ro quiet splash $vt_handoff
initrd /boot/initrd.img-5.0.0-37-generic
}
submenu 'Options avancées pour Ubuntu' $menuentry_id_option 'gnulinux-advanced-78f9d251-8e31-48a1-923f-b1a37316fe2e' {
menuentry 'Ubuntu, avec Linux 5.0.0-37-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.0.0-37-generic-advanced-78f9d251-8e31-48a1-923f-b1a37316fe2e' {
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
fi
echo 'Chargement de Linux 5.0.0-37-generic…'
linux /boot/vmlinuz-5.0.0-37-generic root=UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e ro quiet splash $vt_handoff
echo 'Chargement du disque mémoire initial…'
initrd /boot/initrd.img-5.0.0-37-generic
}
menuentry 'Ubuntu, with Linux 5.0.0-37-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.0.0-37-generic-recovery-78f9d251-8e31-48a1-923f-b1a37316fe2e' {
recordfail
load_video
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
fi
echo 'Chargement de Linux 5.0.0-37-generic…'
linux /boot/vmlinuz-5.0.0-37-generic root=UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e ro recovery nomodeset
echo 'Chargement du disque mémoire initial…'
initrd /boot/initrd.img-5.0.0-37-generic
}
menuentry 'Ubuntu, avec Linux 5.0.0-23-generic' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.0.0-23-generic-advanced-78f9d251-8e31-48a1-923f-b1a37316fe2e' {
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
fi
echo 'Chargement de Linux 5.0.0-23-generic…'
linux /boot/vmlinuz-5.0.0-23-generic root=UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e ro quiet splash $vt_handoff
echo 'Chargement du disque mémoire initial…'
initrd /boot/initrd.img-5.0.0-23-generic
}
menuentry 'Ubuntu, with Linux 5.0.0-23-generic (recovery mode)' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-5.0.0-23-generic-recovery-78f9d251-8e31-48a1-923f-b1a37316fe2e' {
recordfail
load_video
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
fi
echo 'Chargement de Linux 5.0.0-23-generic…'
linux /boot/vmlinuz-5.0.0-23-generic root=UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e ro recovery nomodeset
echo 'Chargement du disque mémoire initial…'
initrd /boot/initrd.img-5.0.0-23-generic
}
}
### 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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
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 78f9d251-8e31-48a1-923f-b1a37316fe2e
else
search --no-floppy --fs-uuid --set=root 78f9d251-8e31-48a1-923f-b1a37316fe2e
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: ================================
--------------------------------------------------------------------------------
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e / ext4 errors=remount-ro 0 1
/swapfile none swap sw 0 0
--------------------------------------------------------------------------------
=================== sda1: Location of files loaded by Grub: ====================
GiB - GB File Fragment(s)
416.182697296 = 446.872768512 boot/grub/grub.cfg 3
40.134975433 = 43.094601728 boot/grub/i386-pc/core.img 1
3.259082794 = 3.499413504 boot/vmlinuz-5.0.0-23-generic 1
4.368530273 = 4.690673664 boot/vmlinuz-5.0.0-37-generic 1
4.368530273 = 4.690673664 vmlinuz 1
3.259082794 = 3.499413504 vmlinuz.old 1
4.632785797 = 4.974415872 boot/initrd.img-5.0.0-23-generic 2
4.101585388 = 4.404043776 boot/initrd.img-5.0.0-37-generic 3
4.101585388 = 4.404043776 initrd.img 3
4.632785797 = 4.974415872 initrd.img.old 2
========= Devices which don't seem to have a corresponding hard drive: =========
sdb
ADDITIONAL INFORMATION :
=================== log of boot-info 20191206_1331 ===================
boot-info version : 4ppa66
boot-sav version : 4ppa66
boot-sav-extra version : 4ppa66
glade2script version : 3.2.3~ppa4
boot-info is executed in installed-session (Ubuntu 18.04.3 LTS, bionic, Ubuntu, x86_64)
CPU op-mode(s): 32-bit, 64-bit
BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=78f9d251-8e31-48a1-923f-b1a37316fe2e ro quiet splash vt.handoff=1
=================== os-prober:
/dev/sda1:L'OS actuellement utilisé - Ubuntu 18.04.3 LTS CurrentSession:linux
=================== blkid:
/dev/sda1: UUID="78f9d251-8e31-48a1-923f-b1a37316fe2e" TYPE="ext4" PARTUUID="911d43d3-01"
1 disks with OS, 1 OS : 1 Linux, 0 MacOS, 0 Windows, 0 unknown type OS.
=================== /etc/grub.d/ :
drwxr-xr-x 2 root root 4096 déc. 6 10:31 grub.d
total 80
-rwxr-xr-x 1 root root 10046 mars 18 2019 00_header
-rwxr-xr-x 1 root root 6258 mars 18 2019 05_debian_theme
-rwxr-xr-x 1 root root 12693 mars 18 2019 10_linux
-rwxr-xr-x 1 root root 11298 mars 18 2019 20_linux_xen
-rwxr-xr-x 1 root root 1992 janv. 28 2016 20_memtest86+
-rwxr-xr-x 1 root root 12059 mars 18 2019 30_os-prober
-rwxr-xr-x 1 root root 1418 mars 18 2019 30_uefi-firmware
-rwxr-xr-x 1 root root 214 mars 18 2019 40_custom
-rwxr-xr-x 1 root root 216 mars 18 2019 41_custom
-rw-r--r-- 1 root root 483 mars 18 2019 README
=================== /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_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash fastboot"
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"
=================== UEFI/Legacy mode:
This installed-session is not in EFI-mode.
SecureBoot disabled.
=================== PARTITIONS & DISKS:
sda1 : sda, not-sepboot, grubenv-ok grub2, grub-pc , update-grub, 64, with-boot, is-os, not--efi--part, fstab-without-boot, fstab-without-efi, 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, .
sda : not-GPT, BIOSboot-not-needed, has-no-EFIpart, not-usb, not-mmc, has-os, 2048 sectors * 512 bytes
=================== parted -lm:
BYT;
/dev/sda:500GB:scsi:512:512:msdos:ATA ST9500420AS:;
1:1049kB:500GB:500GB:ext4::boot;
=================== lsblk:
KNAME TYPE FSTYPE SIZE LABEL
sda disk 465,8G
sda1 part ext4 465,8G
sr0 rom 1024M
KNAME ROTA RO RM STATE MOUNTPOINT
sda 1 0 0 running
sda1 1 0 0 /
sr0 1 0 1 running
=================== 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=1924344k,nr_inodes=481086,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=389704k,mode=755)
/dev/sda1 on / type ext4 (rw,relatime,errors=remount-ro)
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/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate)
cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd)
pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids)
cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset)
cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
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/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma)
systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=24,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=15527)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M)
mqueue on /dev/mqueue type mqueue (rw,relatime)
configfs on /sys/kernel/config type configfs (rw,relatime)
tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=389700k,mode=700,uid=1000,gid=1000)
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
=================== ls:
/sys/block/sda (filtered): alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range hidden holders inflight integrity mq power queue range removable ro sda1 size slaves stat subsystem trace uevent
/sys/block/sdb (filtered): alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range hidden holders inflight integrity mq power queue range removable ro size slaves stat subsystem trace uevent
/sys/block/sr0 (filtered): alignment_offset bdi capability dev device discard_alignment events events_async events_poll_msecs ext_range hidden holders inflight integrity mq power queue range removable ro size slaves stat subsystem trace uevent
/dev (filtered): autofs block bsg btrfs-control bus cdrom cdrw char console core cpu cpu_dma_latency cuse disk dri dvd dvdrw ecryptfs fb0 fd full fuse hpet hugepages hwrng i2c-0 i2c-1 i2c-2 i2c-3 i2c-4 i2c-5 i2c-6 i2c-7 initctl input kmsg lightnvm log mapper mcelog media0 mei0 mem memory_bandwidth mqueue net network_latency network_throughput null port ppp psaux ptmx pts random rfkill rtc rtc0 sda sda1 sdb sg0 sg1 sg2 shm snapshot snd sr0 stderr stdin stdout udmabuf uhid uinput urandom userio v4l vfio vga_arbiter vhci vhost-net vhost-vsock video0 video1 zero
ls /dev/mapper: control
=================== df -Th:
Filesystem Type Size Used Avail Use% Mounted on
udev devtmpfs 1.9G 0 1.9G 0% /dev
tmpfs tmpfs 381M 1.3M 380M 1% /run
/dev/sda1 ext4 458G 5.5G 429G 2% /
tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm
tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup
tmpfs tmpfs 381M 12K 381M 1% /run/user/1000
=================== fdisk -l:
Disk /dev/sda: 465.8 GiB, 500107862016 bytes, 976773168 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: dos
Disk identifier: 0x911d43d3
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 976771071 976769024 465.8G 83 Linux
=================== Suggested repair
The default repair of the Boot-Repair utility would reinstall the grub2 of sda1 into the MBR of sda.
Additional repair would be performed: unhide-bootmenu-10s
=================== Final advice in case of suggested repair
Les fichiers de démarrage de [L'OS actuellement utilisé - Ubuntu 18.04.3 LTS] sont loin du début du disque. Votre BIOS pourrait ne pas les détecter. Vous voudrez peut-être re-essayer après avoir créé une partition /boot (EXT4, >200MB, en début de disque). Cela peut être réalisé via des outils tels que gParted. Puis sélectionnez cette partition via l'option [Partition /boot séparée :] de [Boot-Repair]. (http://doc.ubuntu-fr.org/tutoriel/partition_boot)
=================== User settings
The settings chosen by the user will not act on the boot.
Pour moi, tout est correct dans ce Boot-info.
geole a expliqué dans le post #8 que le message est normal. Du coup, le problème c'est le "son strident" que tu as mentionné dans le post #1. Mais il dure combien de temps ce son strident ?
Dernière modification par malbo (Le 06/12/2019, à 15:58)
Hors ligne
#10 Le 06/12/2019, à 16:05
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
dans mon premier post, j'ecrivais:
jjjjjjjjjjjjjjjjjjjjjjjjj /dev/sda1: clean, ***/**** files, *****/**** blocks jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
en suivant tes instructions, il s'est avere que la lettre 'j' ne repondait pas. or il y a peut etre une relation avec le print d'au-dessus.
quant au son strident, cela pourrait ressembler a une touche enfoncee en permanence... il y a peut etre une relation.
en tout cas, pour taper la commande, j'ai taper help qui m'a fourni un mot avec la lettre 'j' que j'ai recopie.
brigitte@brigitte:~$ journalctl -p err
-- Logs begin at Tue 2019-12-03 22:13:48 CET, end at Fri 2019-12-06 14:52:49 CET. --
-- Logs begin at Tue 2019-12-03 22:13:48 CET, end at Fri 2019-12-06 14:52:49 CET. --
déc. 03 22:13:52 brigitte kernel: mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: Could not read FW version
déc. 03 22:13:52 brigitte kernel: mei mei::55213584-9a29-4916-badf-0fb7ed682aeb:01: FW version command failed -5
déc. 03 22:14:03 brigitte lightdm[659]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 03 22:14:03 brigitte lightdm[659]: PAM adding faulty module: pam_gnome_keyring.so
déc. 03 22:14:03 brigitte lightdm[659]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 03 22:14:03 brigitte lightdm[659]: PAM adding faulty module: pam_kwallet.so
déc. 03 22:14:03 brigitte lightdm[659]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 03 22:14:03 brigitte lightdm[659]: PAM adding faulty module: pam_kwallet5.so
déc. 03 22:14:03 brigitte wpa_supplicant[501]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 03 22:14:03 brigitte wpa_supplicant[501]: dbus: Failed to construct signal
déc. 03 22:14:07 brigitte lightdm[719]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 03 22:14:07 brigitte lightdm[719]: PAM adding faulty module: pam_gnome_keyring.so
déc. 03 22:14:07 brigitte lightdm[719]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 03 22:14:07 brigitte lightdm[719]: PAM adding faulty module: pam_kwallet.so
déc. 03 22:14:07 brigitte lightdm[719]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 03 22:14:07 brigitte lightdm[719]: PAM adding faulty module: pam_kwallet5.so
déc. 03 22:45:48 brigitte wpa_supplicant[13970]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 03 22:45:48 brigitte wpa_supplicant[13970]: dbus: Failed to construct signal
-- Reboot --
déc. 03 22:54:55 brigitte wpa_supplicant[570]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 03 22:54:55 brigitte wpa_supplicant[570]: dbus: Failed to construct signal
déc. 03 22:54:58 brigitte lightdm[656]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 03 22:54:58 brigitte lightdm[656]: PAM adding faulty module: pam_gnome_keyring.so
déc. 03 22:54:58 brigitte lightdm[656]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 03 22:54:58 brigitte lightdm[656]: PAM adding faulty module: pam_kwallet.so
déc. 03 22:54:58 brigitte lightdm[656]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 03 22:54:58 brigitte lightdm[656]: PAM adding faulty module: pam_kwallet5.so
déc. 03 22:55:03 brigitte lightdm[765]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 03 22:55:03 brigitte lightdm[765]: PAM adding faulty module: pam_gnome_keyring.so
déc. 03 22:55:03 brigitte lightdm[765]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 03 22:55:03 brigitte lightdm[765]: PAM adding faulty module: pam_kwallet.so
déc. 03 22:55:03 brigitte lightdm[765]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 03 22:55:03 brigitte lightdm[765]: PAM adding faulty module: pam_kwallet5.so
-- Reboot --
déc. 06 10:16:47 brigitte wpa_supplicant[584]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 10:16:47 brigitte wpa_supplicant[584]: dbus: Failed to construct signal
déc. 06 10:16:49 brigitte lightdm[675]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:16:49 brigitte lightdm[675]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:16:49 brigitte lightdm[675]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:16:49 brigitte lightdm[675]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:16:49 brigitte lightdm[675]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:16:49 brigitte lightdm[675]: PAM adding faulty module: pam_kwallet5.so
déc. 06 10:16:51 brigitte lightdm[724]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:16:51 brigitte lightdm[724]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:16:51 brigitte lightdm[724]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:16:51 brigitte lightdm[724]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:16:51 brigitte lightdm[724]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:16:51 brigitte lightdm[724]: PAM adding faulty module: pam_kwallet5.so
-- Reboot --
déc. 06 10:18:07 brigitte kernel: [drm:radeon_init [radeon]] *ERROR* No UMS support in radeon module!
déc. 06 10:29:14 brigitte systemd[2537]: /lib/systemd/system-generators/friendly-recovery failed with exit status 1.
déc. 06 10:29:14 brigitte avahi-daemon[2593]: chroot.c: open() failed: No such file or directory
déc. 06 10:29:18 brigitte wpa_supplicant[2566]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 10:29:18 brigitte wpa_supplicant[2566]: dbus: Failed to construct signal
déc. 06 10:29:20 brigitte lightdm[2696]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 10:29:20 brigitte lightdm[2696]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:29:20 brigitte lightdm[2696]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:29:20 brigitte lightdm[2696]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:29:20 brigitte lightdm[2696]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:29:20 brigitte lightdm[2696]: PAM adding faulty module: pam_kwallet5.so
déc. 06 10:29:23 brigitte lightdm[2749]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 10:29:23 brigitte lightdm[2749]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:29:23 brigitte lightdm[2749]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:29:23 brigitte lightdm[2749]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:29:23 brigitte lightdm[2749]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:29:23 brigitte lightdm[2749]: PAM adding faulty module: pam_kwallet5.so
déc. 06 10:31:15 brigitte systemd[3508]: /lib/systemd/system-generators/friendly-recovery failed with exit status 1.
déc. 06 10:31:16 brigitte systemd[3556]: /lib/systemd/system-generators/friendly-recovery failed with exit status 1.
déc. 06 10:31:20 brigitte systemd[3604]: /lib/systemd/system-generators/friendly-recovery failed with exit status 1.
déc. 06 10:31:20 brigitte systemd[3628]: /lib/systemd/system-generators/friendly-recovery failed with exit status 1.
déc. 06 10:31:51 brigitte systemd[5391]: /lib/systemd/system-generators/friendly-recovery failed with exit status 1.
-- Reboot --
déc. 06 10:34:28 brigitte wpa_supplicant[559]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 10:34:28 brigitte wpa_supplicant[559]: dbus: Failed to construct signal
déc. 06 10:34:32 brigitte lightdm[666]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:34:32 brigitte lightdm[666]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:34:32 brigitte lightdm[666]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:34:32 brigitte lightdm[666]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:34:32 brigitte lightdm[666]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:34:32 brigitte lightdm[666]: PAM adding faulty module: pam_kwallet5.so
déc. 06 10:34:37 brigitte lightdm[775]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:34:37 brigitte lightdm[775]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:34:37 brigitte lightdm[775]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:34:37 brigitte lightdm[775]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:34:37 brigitte lightdm[775]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:34:37 brigitte lightdm[775]: PAM adding faulty module: pam_kwallet5.so
-- Reboot --
déc. 06 10:46:13 brigitte wpa_supplicant[518]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 10:46:13 brigitte wpa_supplicant[518]: dbus: Failed to construct signal
déc. 06 10:46:14 brigitte lightdm[658]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:46:14 brigitte lightdm[658]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:46:14 brigitte lightdm[658]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:46:14 brigitte lightdm[658]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:46:14 brigitte lightdm[658]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:46:14 brigitte lightdm[658]: PAM adding faulty module: pam_kwallet5.so
déc. 06 10:46:16 brigitte lightdm[712]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:46:16 brigitte lightdm[712]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:46:16 brigitte lightdm[712]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:46:16 brigitte lightdm[712]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:46:16 brigitte lightdm[712]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:46:16 brigitte lightdm[712]: PAM adding faulty module: pam_kwallet5.so
-- Reboot --
déc. 06 10:55:26 brigitte wpa_supplicant[571]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 10:55:26 brigitte wpa_supplicant[571]: dbus: Failed to construct signal
déc. 06 10:55:27 brigitte lightdm[659]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:55:27 brigitte lightdm[659]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:55:27 brigitte lightdm[659]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:55:27 brigitte lightdm[659]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:55:27 brigitte lightdm[659]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:55:27 brigitte lightdm[659]: PAM adding faulty module: pam_kwallet5.so
déc. 06 10:55:29 brigitte lightdm[713]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 10:55:29 brigitte lightdm[713]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 10:55:29 brigitte lightdm[713]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 10:55:29 brigitte lightdm[713]: PAM adding faulty module: pam_kwallet.so
déc. 06 10:55:29 brigitte lightdm[713]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 10:55:29 brigitte lightdm[713]: PAM adding faulty module: pam_kwallet5.so
déc. 06 11:13:31 brigitte lightdm[1200]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 11:13:31 brigitte lightdm[1200]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 11:13:31 brigitte lightdm[1200]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 11:13:31 brigitte lightdm[1200]: PAM adding faulty module: pam_kwallet.so
déc. 06 11:13:31 brigitte lightdm[1200]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 11:13:31 brigitte lightdm[1200]: PAM adding faulty module: pam_kwallet5.so
déc. 06 11:13:32 brigitte lightdm[1249]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 11:13:32 brigitte lightdm[1249]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 11:13:32 brigitte lightdm[1249]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 11:13:32 brigitte lightdm[1249]: PAM adding faulty module: pam_kwallet.so
déc. 06 11:13:32 brigitte lightdm[1249]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 11:13:32 brigitte lightdm[1249]: PAM adding faulty module: pam_kwallet5.so
-- Reboot --
déc. 06 11:47:46 brigitte wpa_supplicant[579]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 11:47:46 brigitte wpa_supplicant[579]: dbus: Failed to construct signal
déc. 06 11:47:47 brigitte lightdm[669]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 11:47:47 brigitte lightdm[669]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 11:47:47 brigitte lightdm[669]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 11:47:47 brigitte lightdm[669]: PAM adding faulty module: pam_kwallet.so
déc. 06 11:47:47 brigitte lightdm[669]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 11:47:47 brigitte lightdm[669]: PAM adding faulty module: pam_kwallet5.so
déc. 06 11:47:49 brigitte lightdm[718]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 11:47:49 brigitte lightdm[718]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 11:47:49 brigitte lightdm[718]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 11:47:49 brigitte lightdm[718]: PAM adding faulty module: pam_kwallet.so
déc. 06 11:47:49 brigitte lightdm[718]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 11:47:49 brigitte lightdm[718]: PAM adding faulty module: pam_kwallet5.so
déc. 06 11:51:58 brigitte systemd[1]: Failed to start Postfix Mail Transport Agent (instance -).
déc. 06 11:57:34 brigitte kernel: print_req_error: I/O error, dev sdc, sector 2049 flags 1
déc. 06 11:57:34 brigitte kernel: Buffer I/O error on dev sdc1, logical block 1, lost async page write
déc. 06 11:57:34 brigitte kernel: print_req_error: I/O error, dev sdc, sector 17328 flags 1
déc. 06 11:57:34 brigitte kernel: Buffer I/O error on dev sdc1, logical block 15280, lost async page write
déc. 06 11:57:34 brigitte kernel: Buffer I/O error on dev sdc1, logical block 15281, lost async page write
déc. 06 11:57:34 brigitte kernel: Buffer I/O error on dev sdc1, logical block 15282, lost async page write
déc. 06 11:57:34 brigitte kernel: Buffer I/O error on dev sdc1, logical block 15283, lost async page write
déc. 06 12:07:39 brigitte lightdm[3056]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 12:07:39 brigitte lightdm[3056]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 12:07:39 brigitte lightdm[3056]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 12:07:39 brigitte lightdm[3056]: PAM adding faulty module: pam_kwallet.so
déc. 06 12:07:39 brigitte lightdm[3056]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 12:07:39 brigitte lightdm[3056]: PAM adding faulty module: pam_kwallet5.so
déc. 06 12:07:40 brigitte lightdm[3105]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 12:07:40 brigitte lightdm[3105]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 12:07:40 brigitte lightdm[3105]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 12:07:40 brigitte lightdm[3105]: PAM adding faulty module: pam_kwallet.so
déc. 06 12:07:40 brigitte lightdm[3105]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 12:07:40 brigitte lightdm[3105]: PAM adding faulty module: pam_kwallet5.so
déc. 06 13:28:39 brigitte kernel: print_req_error: I/O error, dev sdc, sector 2049 flags 1
déc. 06 13:28:39 brigitte kernel: Buffer I/O error on dev sdc1, logical block 1, lost async page write
déc. 06 13:28:39 brigitte kernel: print_req_error: I/O error, dev sdc, sector 17331 flags 1
déc. 06 13:28:39 brigitte kernel: Buffer I/O error on dev sdc1, logical block 15283, lost async page write
déc. 06 14:48:18 brigitte lightdm[20055]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 14:48:18 brigitte lightdm[20055]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 14:48:18 brigitte lightdm[20055]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 14:48:18 brigitte lightdm[20055]: PAM adding faulty module: pam_kwallet.so
déc. 06 14:48:18 brigitte lightdm[20055]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 14:48:18 brigitte lightdm[20055]: PAM adding faulty module: pam_kwallet5.so
déc. 06 14:48:19 brigitte lightdm[20104]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 14:48:19 brigitte lightdm[20104]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 14:48:19 brigitte lightdm[20104]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 14:48:19 brigitte lightdm[20104]: PAM adding faulty module: pam_kwallet.so
déc. 06 14:48:19 brigitte lightdm[20104]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 14:48:19 brigitte lightdm[20104]: PAM adding faulty module: pam_kwallet5.so
déc. 06 14:48:27 brigitte lightdm[20106]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or
déc. 06 14:48:27 brigitte lightdm[20106]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 14:48:27 brigitte lightdm[20106]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 14:48:27 brigitte lightdm[20106]: PAM adding faulty module: pam_kwallet.so
déc. 06 14:48:27 brigitte lightdm[20106]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 14:48:27 brigitte lightdm[20106]: PAM adding faulty module: pam_kwallet5.so
-- Reboot --
déc. 06 14:51:55 brigitte wpa_supplicant[551]: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
déc. 06 14:51:55 brigitte wpa_supplicant[551]: dbus: Failed to construct signal
déc. 06 14:51:58 brigitte lightdm[669]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 14:51:58 brigitte lightdm[669]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 14:51:58 brigitte lightdm[669]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 14:51:58 brigitte lightdm[669]: PAM adding faulty module: pam_kwallet.so
déc. 06 14:51:58 brigitte lightdm[669]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 14:51:58 brigitte lightdm[669]: PAM adding faulty module: pam_kwallet5.so
déc. 06 14:52:02 brigitte lightdm[732]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 06 14:52:02 brigitte lightdm[732]: PAM adding faulty module: pam_gnome_keyring.so
déc. 06 14:52:02 brigitte lightdm[732]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
déc. 06 14:52:02 brigitte lightdm[732]: PAM adding faulty module: pam_kwallet.so
déc. 06 14:52:02 brigitte lightdm[732]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
déc. 06 14:52:02 brigitte lightdm[732]: PAM adding faulty module: pam_kwallet5.so
déc. 06 14:52:03 brigitte systemd[1]: Failed to start Postfix Mail Transport Agent (instance -).
la date de jeudi correspond a la reinstalle en 18.04.
Hors ligne
#11 Le 06/12/2019, à 16:06
- Sciensous
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
si le pc est ancien, ça peut être un ventilo qui couigne (vécu sur un asus)
ça disparaissait après qq minutes
antiX 19 et 21 et Ubuntu 20.04 et 22.04
( sous LXDE et gnome-shell )
Hors ligne
#12 Le 06/12/2019, à 16:16
- malbo
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
dans mon premier post, j'ecrivais:
jjjjjjjjjjjjjjjjjjjjjjjjj /dev/sda1: clean, ***/**** files, *****/**** blocks jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
en suivant tes instructions, il s'est avere que la lettre 'j' ne repondait pas. or il y a peut etre une relation avec le print d'au-dessus.
quant au son strident, cela pourrait ressembler a une touche enfoncee en permanence... il y a peut etre une relation.
Je crois que tu as mis le doigt sur le problème. Je n'avais pas fais attention que le message "/dev/sda1: clean, ***/**** files, *****/**** blocks" était encadré par une suite de "j" mais là c'est sûr que c'est lié.
Hors ligne
#13 Le 06/12/2019, à 16:17
- geole
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Pourquoi voit-on des traces de ligthdm ? puisque tu es en version 18.04 ? ( https://doc.ubuntu-fr.org/lightdm )
déc. 03 22:14:03 brigitte lightdm[659]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or d
déc. 03 22:14:03 brigitte lightdm[659]: PAM adding faulty module: pam_gnome_keyring.so
Dernière modification par geole (Le 06/12/2019, à 16:20)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#14 Le 06/12/2019, à 16:19
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
le pc a qlq hrs de vol certe, mais non, ce n'est pas un bruit de ventilo.
tout se passe au moment du boot.
1ere possibilite: le son ding-ding-ding (sur un windows, c'est le meme son si on appuie longtemps sur une touche) avec ecran noir apres avoir vu l'invite ".... Echappe" et la, on est bon pour rebooter. j'etteins par l'interrupteur. cette possibilite apparait si j'arrive de la 2eme en ayant eteint normalement.
2eme possibilite: on arrive dans le grub, je choisi ubuntu et j'ai droit au print qui se termine par la fenetre normale de log. cette possibilite si j'ai eteint par l'interrupteur physique.
il y a peut etre une 3eme, j'ai le souvenir d'un mixte des 2 avec au final comme echappatoire l'interrupteur, mais c'est a confirmer.
Hors ligne
#15 Le 06/12/2019, à 16:20
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
je suis sur une Lubuntu 18.04.
Hors ligne
#16 Le 06/12/2019, à 16:30
- geole
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Je ne sais que penser de ce bug https://bugs.launchpad.net/ubuntu/+sour … ug/1768488
Cela serait surprenant qu'il provoque un bip
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#17 Le 06/12/2019, à 16:53
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
geole, ca pourrait etre une piste. aurait il ete introduit en 16.04.03? le pc en vient. je suis passe en 18.04 en pensant le regler mais comme ecrit, le probleme a suivi cette derniere version.
ds ton lien, il est ecrit:
It's because /etc/pam.d/lightdm and /etc/pam.d/lightdm-greeter try to load pam modules which are not installed since there are not dependencies to libpam-gnome-keyring libpam-kwallet4 libpam-kwallet5
If it is not intended to let things run into error message (and possible further trouble), you should either remove these lines from the config files or add dependencies to pull in that packages.
il suffirait d'editer lightdm & lightdm-greeter et de surprimer les lignes en relation avec pam?
du style pour lightdm. j'ai rajouter les #
#%PAM-1.0
auth requisite pam_nologin.so
auth sufficient pam_succeed_if.so user ingroup nopasswdlogin
@include common-auth
#auth optional pam_gnome_keyring.so
auth optional pam_kwallet.so
#auth optional pam_kwallet5.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
#session required pam_loginuid.so
session required pam_limits.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
#session optional pam_gnome_keyring.so auto_start
session optional pam_kwallet.so auto_start
#session optional pam_kwallet5.so auto_start
session required pam_env.so readenv=1
session required pam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale
@include common-password
et lightdm-greeter:
#%PAM-1.0
auth required pam_permit.so
#auth optional pam_gnome_keyring.so
auth optional pam_kwallet.so
#auth optional pam_kwallet5.so
@include common-account
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
session required pam_limits.so
@include common-session
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
#session optional pam_gnome_keyring.so auto_start
session optional pam_kwallet.so auto_start
#session optional pam_kwallet5.so auto_start
session required pam_env.so readenv=1
session required pam_env.so readenv=1 user_readenv=1 envfile=/etc/default/locale
Hors ligne
#18 Le 06/12/2019, à 17:36
- geole
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Je ne ne sais pas conseiller pour l'affichage écran. Dans les discussions internet que j'ai vu sur ce problème. Certains disaient d'éliminer une librairie....
J'ai constaté que tu vas certainement tenter d'appliquer ce conseil https://bugs.launchpad.net/ubuntu/+sour … omments/17
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash fastboot"
Ce n'est pas une bonne idée.
Dernière modification par geole (Le 06/12/2019, à 17:39)
Les grilles de l'installateur https://doc.ubuntu-fr.org/tutoriel/inst … _subiquity
"gedit admin:///etc/fstab" est proscrit, utilisez "pkexec env DISPLAY=$DISPLAY XAUTHORITY=$XAUTHORITY xdg-open /etc/fstab" Voir https://doc.ubuntu-fr.org/gedit
Les partitions EXT4 des disques externes => https://forum.ubuntu-fr.org/viewtopic.p … #p22697248
Hors ligne
#19 Le 06/12/2019, à 17:52
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
rajouter fasboot n'a rien changer, ni en mieux ni en pire.
il est sans doute preferable de revenir a la config initiale.
Hors ligne
#20 Le 06/12/2019, à 18:04
- erresse
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
david69 a écrit :dans mon premier post, j'ecrivais:
jjjjjjjjjjjjjjjjjjjjjjjjj /dev/sda1: clean, ***/**** files, *****/**** blocks jjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj
en suivant tes instructions, il s'est avere que la lettre 'j' ne repondait pas. or il y a peut etre une relation avec le print d'au-dessus.
quant au son strident, cela pourrait ressembler a une touche enfoncee en permanence... il y a peut etre une relation.Je crois que tu as mis le doigt sur le problème. Je n'avais pas fais attention que le message "/dev/sda1: clean, ***/**** files, *****/**** blocks" était encadré par une suite de "j" mais là c'est sûr que c'est lié.
Bonjour,
Il est très possible que ce son soit produit par le code qui fait s'afficher un "j" sur l'écran. Ce n'est pas forcément le code de "j" qui est reçu, mais il peut être interprété par cette lettre pour l'affichage, alors qu'il provoque un "bell" par exemple.
Le son pourrait être émis par le haut-parleur intégré (si le PC est une tour) la machine se comportant au démarrage comme une console.
S'il était possible d'empêcher le message de sortir ou d'en modifier la teneur pour virer les pseudo "j", ce serait une bonne manière de vérifier cette hypothèse...
Plus de 50 ans d'informatique, ça en fait des lignes de commandes en console, mais on n'avait pas le choix...
Excellente raison pour, aujourd'hui qu'on le peut, utiliser au maximum les INTERFACES GRAPHIQUES !
Important : Une fois résolu, pensez à clore votre sujet en ajoutant [Résolu] devant le titre du 1er message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.
Hors ligne
#21 Le 06/12/2019, à 18:08
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
c'est un laptop.
neanmoins, comment peut on expliquer la relation entre une touche et la maniere dont le pc se comporte au demarrage? voir post#14.
Hors ligne
#22 Le 06/12/2019, à 18:41
- erresse
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
Dans la table des codes ascii, il en est qui ne sont pas affichables parce-qu'ils n'ont pas de représentation graphique, mais qui sont destinés à commander le terminal, comme les codes de déplacement du curseur, la sonnerie, l'effacement, etc.
Il peut arriver qu'un de ces codes soit interprété à tort par l'affichage d'un signe qui correspond à une partie de sa valeur, ce qui pourrait faire afficher "j", et si ce code correspond à l'activation de la sonnerie, la machine bipe.
Si tu as une série de signes de ce type, ça déclenche un son strident et prolongé, ce qui pourrait correspondre aux deux séries de signes "j" qui sont listés dans ton message, mais ce n'est bien sûr qu'une supposition...
Plus de 50 ans d'informatique, ça en fait des lignes de commandes en console, mais on n'avait pas le choix...
Excellente raison pour, aujourd'hui qu'on le peut, utiliser au maximum les INTERFACES GRAPHIQUES !
Important : Une fois résolu, pensez à clore votre sujet en ajoutant [Résolu] devant le titre du 1er message, et un bref récapitulatif de la solution à la fin de celui-ci. Merci.
Hors ligne
#23 Le 07/12/2019, à 10:45
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
a priori ce n'est pas le hardware, ce pourrait etre un bug ou une mesinterpretation d'un code ascii. comment en avoir le coeur net?
est ce que ce que j'ennoncais au post#17 soit correct au regard de la remonter de bug?
Hors ligne
#24 Le 09/12/2019, à 17:33
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
j'ai applique les modifs du post#17, le probleme persiste. rien n'a change en terme de comportement. ni pire ni mieux.
Hors ligne
#25 Le 13/12/2019, à 21:30
- david69
Re : /dev/sda1: clean, ***/**** files, *****/**** blocks au demarrage
je remonte le sujet pour lui eviter de descendre dans les abimes du forum. si je reviens vers ma cousine en disant je ne sais pas, il est a parie qu'elle va acheter une nouvelle machine.
Hors ligne