Je suis d’accord avec toi, quand tu as identifié la source de l’erreur, la aucune idée et vu le nombre de fichiers de log ce n’est pas l’approche que je conseillerai. C’est la magie d’un forum, pleins d’avis et libre au demandant de choisir /tester
Il est vrai que je pense aussi que le test physique (en notant ce qui est testé ou pas) est une approche basique (un peu longue puisque le delta ets de 2h ; j’en conviens).
Et une fois que la « source du souci » est identifiée, les logs devraient aider à identifier « le souci » en particulier.
Perso, je ferai donc tourner le Rpi avec Raspbian de base puis avec plex, puis avec le ventilo en sus puis sans plex mais avec le ventilo, puis … (et oui, y a du taf 
)
Je maintiens que l’approche log est à vérifier en premier : il y en a pour deux minutes montre en main (on voit bien que le nombre de logs ayant bougé n’est pas si élevé).
L’avis d’un vieux singe, quoi…
Ça ne vous empêche pas de penser et faire autrement, bien entendu, et définitivement ! Et de l’affirmer haut et fort !
Yo,
Ce n’est pas faux si on sait décrypter les logs
Parce que pour avoir regardé mes /var/log/syslog et /var/log/kern.log = j’avoue que je comprends des choses, mais pas tout (loin de là)
D’ailleurs, on va en profiter pour relancer @dean63 et @escobarrr (second profil créé ?) pour avoir :
- Les 100 dernières lignes que tu demandais (dans syslog et kern.log).
- Les résultats des tests physiques s’il y en a eu de fais
++
Ha non je n’ai pas 2 profils. Je regarderai les logs la semaine prochaine je ne suis pas chez moi là. Mais merci à vous.
Le côté obscur de la force est parfois dans les logs. Postez, postez, il en restera toujours quelque chose (comme disais Victor Hugo,où je ne sais plus quel barbu de l’époque)
prêt pour la lecture ? lol go :
/var/log/syslog
May 20 20:48:05 raspberrypi systemd[1]: bthelper@hci0.service: Unit entered failed state.
May 20 20:48:05 raspberrypi systemd[1]: bthelper@hci0.service: Failed with result ‹ exit-code ›.
May 20 20:48:05 raspberrypi kernel: [ 14.496943] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 20 20:48:05 raspberrypi kernel: [ 14.496951] Bluetooth: BNEP filters: protocol multicast
May 20 20:48:05 raspberrypi kernel: [ 14.496967] Bluetooth: BNEP socket layer initialized
May 20 20:48:05 raspberrypi bluetoothd[899]: Bluetooth management interface 1.14 initialized
May 20 20:48:05 raspberrypi bluetoothd[899]: Failed to obtain handles for « Service Changed » characteristic
May 20 20:48:05 raspberrypi dbus[328]: [system] Activating via systemd: service name=‹ org.freedesktop.hostname1 › unit=‹ dbus-org.freedesktop.hostname1.service ›
May 20 20:48:05 raspberrypi bluetoothd[899]: Sap driver initialization failed.
May 20 20:48:05 raspberrypi bluetoothd[899]: sap-server: Operation not permitted (1)
May 20 20:48:05 raspberrypi bluetoothd[899]: Failed to set mode: Blocked through rfkill (0x12)
May 20 20:48:05 raspberrypi bluetoothd[899]: Endpoint registered: sender=:1.12 path=/A2DP/SBC/Source/1
May 20 20:48:05 raspberrypi systemd[1]: Starting Hostname Service…
May 20 20:48:05 raspberrypi kernel: [ 14.558718] Bluetooth: RFCOMM TTY layer initialized
May 20 20:48:05 raspberrypi kernel: [ 14.558740] Bluetooth: RFCOMM socket layer initialized
May 20 20:48:05 raspberrypi kernel: [ 14.558762] Bluetooth: RFCOMM ver 1.11
May 20 20:48:05 raspberrypi dbus[328]: [system] Successfully activated service ‹ org.freedesktop.hostname1 ›
May 20 20:48:05 raspberrypi systemd[1]: Started Hostname Service.
May 20 20:48:07 raspberrypi ntfs-3g[980]: Version 2016.2.22AR.1 integrated FUSE 28
May 20 20:48:07 raspberrypi ntfs-3g[980]: Mounted /dev/sda1 (Read-Write, label « DDE SERIES », NTFS 3.1)
May 20 20:48:07 raspberrypi ntfs-3g[980]: Cmdline options: rw
May 20 20:48:07 raspberrypi systemd[1]: Mounted /mnt/library/DDESERIES.
May 20 20:48:07 raspberrypi ntfs-3g[980]: Mount options: rw,allow_other,nonempty,relatime,fsname=/dev/sda1,blkdev,blksize=4096
May 20 20:48:07 raspberrypi ntfs-3g[980]: Ownership and permissions disabled, configuration type 7
May 20 20:48:08 raspberrypi dbus-daemon[857]: Activating via systemd: service name=‹ org.gtk.vfs.Daemon › unit=‹ gvfs-daemon.service ›
May 20 20:48:08 raspberrypi systemd[835]: Starting Virtual filesystem service…
May 20 20:48:08 raspberrypi dbus-daemon[857]: Successfully activated service ‹ org.gtk.vfs.Daemon ›
May 20 20:48:08 raspberrypi systemd[835]: Started Virtual filesystem service.
May 20 20:48:08 raspberrypi dbus[328]: [system] Activating via systemd: service name=‹ org.freedesktop.PolicyKit1 › unit=‹ polkit.service ›
May 20 20:48:08 raspberrypi systemd[1]: Starting Authorization Manager…
May 20 20:48:09 raspberrypi polkitd[1041]: started daemon version 0.105 using authority implementation local' version 0.105’
May 20 20:48:09 raspberrypi dbus[328]: [system] Successfully activated service ‹ org.freedesktop.PolicyKit1 ›
May 20 20:48:09 raspberrypi systemd[1]: Started Authorization Manager.
May 20 20:48:09 raspberrypi dbus-daemon[857]: Activating via systemd: service name=‹ org.gtk.vfs.UDisks2VolumeMonitor › unit=‹ gvfs-udisks2-volume-monitor.service ›
May 20 20:48:09 raspberrypi systemd[835]: Starting Virtual filesystem service - disk device monitor…
May 20 20:48:09 raspberrypi dbus[328]: [system] Activating via systemd: service name=‹ org.freedesktop.UDisks2 › unit=‹ udisks2.service ›
May 20 20:48:09 raspberrypi systemd[1]: Starting Disk Manager…
May 20 20:48:10 raspberrypi udisksd[1064]: udisks daemon version 2.1.8 starting
May 20 20:48:10 raspberrypi dbus[328]: [system] Successfully activated service ‹ org.freedesktop.UDisks2 ›
May 20 20:48:10 raspberrypi systemd[1]: Started Disk Manager.
May 20 20:48:10 raspberrypi udisksd[1064]: Acquired the name org.freedesktop.UDisks2 on the system message bus
May 20 20:48:10 raspberrypi udisksd[1064]: Cleaning up mount point /media/pi/SETTINGS (device 179:5 is not mounted)
May 20 20:48:10 raspberrypi dbus-daemon[857]: Successfully activated service ‹ org.gtk.vfs.UDisks2VolumeMonitor ›
May 20 20:48:10 raspberrypi systemd[835]: Started Virtual filesystem service - disk device monitor.
May 20 20:48:10 raspberrypi dbus-daemon[857]: Activating via systemd: service name=‹ org.gtk.vfs.GoaVolumeMonitor › unit=‹ gvfs-goa-volume-monitor.service ›
May 20 20:48:10 raspberrypi systemd[835]: Starting Virtual filesystem service - GNOME Online Accounts monitor…
May 20 20:48:10 raspberrypi dbus-daemon[857]: Successfully activated service ‹ org.gtk.vfs.GoaVolumeMonitor ›
May 20 20:48:10 raspberrypi systemd[835]: Started Virtual filesystem service - GNOME Online Accounts monitor.
May 20 20:48:10 raspberrypi dbus-daemon[857]: Activating via systemd: service name=‹ org.gtk.vfs.MTPVolumeMonitor › unit=‹ gvfs-mtp-volume-monitor.service ›
May 20 20:48:10 raspberrypi systemd[835]: Starting Virtual filesystem service - Media Transfer Protocol monitor…
May 20 20:48:10 raspberrypi dbus-daemon[857]: Successfully activated service ‹ org.gtk.vfs.MTPVolumeMonitor ›
May 20 20:48:10 raspberrypi systemd[835]: Started Virtual filesystem service - Media Transfer Protocol monitor.
May 20 20:48:10 raspberrypi dbus-daemon[857]: Activating via systemd: service name=‹ org.gtk.vfs.AfcVolumeMonitor › unit=‹ gvfs-afc-volume-monitor.service ›
May 20 20:48:10 raspberrypi systemd[835]: Starting Virtual filesystem service - Apple File Conduit monitor…
May 20 20:48:10 raspberrypi gvfs-afc-volume-monitor[1091]: Volume monitor alive
May 20 20:48:10 raspberrypi dbus-daemon[857]: Successfully activated service ‹ org.gtk.vfs.AfcVolumeMonitor ›
May 20 20:48:10 raspberrypi systemd[835]: Started Virtual filesystem service - Apple File Conduit monitor.
May 20 20:48:10 raspberrypi dbus-daemon[857]: Activating via systemd: service name=‹ org.gtk.vfs.GPhoto2VolumeMonitor › unit=‹ gvfs-gphoto2-volume-monitor.service ›
May 20 20:48:10 raspberrypi systemd[835]: Starting Virtual filesystem service - digital camera monitor…
May 20 20:48:10 raspberrypi dbus-daemon[857]: Successfully activated service ‹ org.gtk.vfs.GPhoto2VolumeMonitor ›
May 20 20:48:10 raspberrypi systemd[835]: Started Virtual filesystem service - digital camera monitor.
May 20 20:48:12 raspberrypi kernel: [ 21.054126] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
May 20 20:48:12 raspberrypi udisksd[1064]: Mounted /dev/mmcblk0p5 at /media/pi/SETTINGS on behalf of uid 1000
May 20 20:48:12 raspberrypi dhcpcd[382]: wlan0: carrier acquired
May 20 20:48:12 raspberrypi kernel: [ 21.274192] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
May 20 20:48:12 raspberrypi dhcpcd[382]: wlan0: IAID eb:31:1b:57
May 20 20:48:12 raspberrypi dhcpcd[382]: wlan0: adding address fe80::fa08:77cc:9b7f:4e68
May 20 20:48:12 raspberrypi avahi-daemon[350]: Joining mDNS multicast group on interface wlan0.IPv6 with address fe80::fa08:77cc:9b7f:4e68.
May 20 20:48:12 raspberrypi avahi-daemon[350]: New relevant interface wlan0.IPv6 for mDNS.
May 20 20:48:12 raspberrypi avahi-daemon[350]: Registering new address record for fe80::fa08:77cc:9b7f:4e68 on wlan0.*.
May 20 20:48:12 raspberrypi dhcpcd[382]: wlan0: soliciting an IPv6 router
May 20 20:48:12 raspberrypi dhcpcd[382]: wlan0: rebinding lease of 192.168.0.100
May 20 20:48:12 raspberrypi dhcpcd[382]: wlan0: probing address 192.168.0.100/24
May 20 20:48:13 raspberrypi dbus[328]: [system] Activating service name=‹ net.launchpad.backintime.serviceHelper › (using servicehelper)
May 20 20:48:14 raspberrypi dbus[328]: [system] Successfully activated service ‹ net.launchpad.backintime.serviceHelper ›
May 20 20:48:17 raspberrypi dhcpcd[382]: wlan0: leased 192.168.0.100 for 43200 seconds
May 20 20:48:17 raspberrypi avahi-daemon[350]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.0.100.
May 20 20:48:17 raspberrypi avahi-daemon[350]: New relevant interface wlan0.IPv4 for mDNS.
May 20 20:48:17 raspberrypi dhcpcd[382]: wlan0: adding route to 192.168.0.0/24
May 20 20:48:17 raspberrypi avahi-daemon[350]: Registering new address record for 192.168.0.100 on wlan0.IPv4.
May 20 20:48:17 raspberrypi dhcpcd[382]: wlan0: adding default route via 192.168.0.254
May 20 20:48:21 raspberrypi systemd[1]: Started Samba NMB Daemon.
May 20 20:48:21 raspberrypi systemd[1]: Starting Samba Winbind Daemon…
May 20 20:48:21 raspberrypi systemd[1]: winbind.service: Supervising process 1259 which is not our child. We’ll most likely not notice when it exits.
May 20 20:48:21 raspberrypi systemd[1]: Started Samba Winbind Daemon.
May 20 20:48:21 raspberrypi systemd[1]: Starting Samba SMB Daemon…
May 20 20:48:22 raspberrypi systemd[1]: smbd.service: Supervising process 1278 which is not our child. We’ll most likely not notice when it exits.
May 20 20:48:22 raspberrypi systemd[1]: Started Samba SMB Daemon.
May 20 20:48:22 raspberrypi systemd[1]: Reached target Multi-User System.
May 20 20:48:22 raspberrypi systemd[1]: Reached target Graphical Interface.
May 20 20:48:22 raspberrypi systemd[1]: Starting Update UTMP about System Runlevel Changes…
May 20 20:48:22 raspberrypi systemd[1]: Started Update UTMP about System Runlevel Changes.
May 20 20:48:22 raspberrypi systemd[1]: Startup finished in 2.856s (kernel) + 28.718s (userspace) = 31.574s.
May 20 20:48:25 raspberrypi dhcpcd[382]: wlan0: no IPv6 Routers available
May 20 21:11:03 raspberrypi systemd[1]: Time has been changed
May 20 21:11:03 raspberrypi systemd[835]: Time has been changed
May 20 21:11:03 raspberrypi systemd-timesyncd[292]: Synchronized to time server 213.251.53.11:123 (2.debian.pool.ntp.org).
May 20 21:11:03 raspberrypi systemd[1]: apt-daily.timer: Adding 10h 2min 37.856248s random time.
May 20 21:11:03 raspberrypi systemd[1]: apt-daily-upgrade.timer: Adding 13min 2.097195s random time.
May 20 21:12:09 raspberrypi systemd[1]: Started Session c3 of user pi.
/var/log/kern.log
May 20 20:47:58 raspberrypi kernel: [ 3.085908] NET: Registered protocol family 10
May 20 20:47:58 raspberrypi kernel: [ 3.087312] Segment Routing with IPv6
May 20 20:47:58 raspberrypi kernel: [ 3.132296] random: systemd: uninitialized urandom read (16 bytes read)
May 20 20:47:58 raspberrypi kernel: [ 3.135151] random: systemd: uninitialized urandom read (16 bytes read)
May 20 20:47:58 raspberrypi kernel: [ 3.235953] random: systemd-cryptse: uninitialized urandom read (16 bytes read)
May 20 20:47:58 raspberrypi kernel: [ 3.881940] i2c /dev entries driver
May 20 20:47:58 raspberrypi kernel: [ 4.242601] EXT4-fs (mmcblk0p7): re-mounted. Opts: (null)
May 20 20:47:58 raspberrypi kernel: [ 4.759098] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
May 20 20:47:58 raspberrypi kernel: [ 4.761213] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
May 20 20:47:58 raspberrypi kernel: [ 4.761233] [vc_sm_connected_init]: start
May 20 20:47:58 raspberrypi kernel: [ 4.765711] [vc_sm_connected_init]: installed successfully
May 20 20:47:58 raspberrypi kernel: [ 4.773176] media: Linux media interface: v0.10
May 20 20:47:58 raspberrypi kernel: [ 4.804263] videodev: Linux video capture interface: v2.00
May 20 20:47:58 raspberrypi kernel: [ 4.859528] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
May 20 20:47:58 raspberrypi kernel: [ 4.859533] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
May 20 20:47:58 raspberrypi kernel: [ 4.896194] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
May 20 20:47:58 raspberrypi kernel: [ 4.910554] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
May 20 20:47:58 raspberrypi kernel: [ 4.981472] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
May 20 20:47:58 raspberrypi kernel: [ 4.989313] bcm2835_audio soc:audio: card created with 8 channels
May 20 20:47:58 raspberrypi kernel: [ 5.161638] cfg80211: Loading compiled-in X.509 certificates for regulatory database
May 20 20:47:58 raspberrypi kernel: [ 5.246704] cfg80211: Loaded X.509 cert ‹ sforshee: 00b28ddf47aef9cea7 ›
May 20 20:47:58 raspberrypi kernel: [ 5.371430] brcmfmac: F1 signature read @0x18000000=0x15264345
May 20 20:47:58 raspberrypi kernel: [ 5.382352] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
May 20 20:47:58 raspberrypi kernel: [ 5.383254] usbcore: registered new interface driver brcmfmac
May 20 20:47:58 raspberrypi kernel: [ 5.525101] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
May 20 20:47:58 raspberrypi kernel: [ 5.525114] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
May 20 20:47:58 raspberrypi kernel: [ 5.531186] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
May 20 20:47:58 raspberrypi kernel: [ 5.531200] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
May 20 20:47:58 raspberrypi kernel: [ 5.534908] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
May 20 20:47:58 raspberrypi kernel: [ 5.534922] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
May 20 20:47:58 raspberrypi kernel: [ 5.619435] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
May 20 20:47:58 raspberrypi kernel: [ 5.637445] random: crng init done
May 20 20:47:58 raspberrypi kernel: [ 5.637462] random: 7 urandom warning(s) missed due to ratelimiting
May 20 20:47:58 raspberrypi kernel: [ 5.645853] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Feb 27 2018 03:15:32 version 7.45.154 (r684107 CY) FWID 01-4fbe0b04
May 20 20:47:58 raspberrypi kernel: [ 6.032094] usb 1-1.1.2.1: new high-speed USB device number 7 using dwc_otg
May 20 20:47:58 raspberrypi kernel: [ 6.243060] usb 1-1.1.2.1: New USB device found, idVendor=0bc2, idProduct=231a, bcdDevice= 7.08
May 20 20:47:58 raspberrypi kernel: [ 6.243078] usb 1-1.1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 20 20:47:58 raspberrypi kernel: [ 6.243089] usb 1-1.1.2.1: Product: Expansion
May 20 20:47:58 raspberrypi kernel: [ 6.243098] usb 1-1.1.2.1: Manufacturer: Seagate
May 20 20:47:58 raspberrypi kernel: [ 6.243107] usb 1-1.1.2.1: SerialNumber: NA8PTA5M
May 20 20:47:58 raspberrypi kernel: [ 6.243927] usb 1-1.1.2.1: The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is
May 20 20:47:58 raspberrypi kernel: [ 6.243939] usb 1-1.1.2.1: required by the UAS driver. Please try an other USB controller if you wish to use UAS.
May 20 20:47:58 raspberrypi kernel: [ 6.243951] usb-storage 1-1.1.2.1:1.0: USB Mass Storage device detected
May 20 20:47:58 raspberrypi kernel: [ 6.249606] scsi host0: usb-storage 1-1.1.2.1:1.0
May 20 20:47:58 raspberrypi kernel: [ 6.306415] usbcore: registered new interface driver uas
May 20 20:47:58 raspberrypi kernel: [ 6.342086] usb 1-1.1.2.2: new high-speed USB device number 8 using dwc_otg
May 20 20:47:58 raspberrypi kernel: [ 6.483716] usb 1-1.1.2.2: New USB device found, idVendor=0bc2, idProduct=2321, bcdDevice= 1.00
May 20 20:47:58 raspberrypi kernel: [ 6.483734] usb 1-1.1.2.2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
May 20 20:47:58 raspberrypi kernel: [ 6.483743] usb 1-1.1.2.2: Product: Expansion
May 20 20:47:58 raspberrypi kernel: [ 6.483752] usb 1-1.1.2.2: Manufacturer: Seagate
May 20 20:47:58 raspberrypi kernel: [ 6.483760] usb 1-1.1.2.2: SerialNumber: NA4BKTY4
May 20 20:47:58 raspberrypi kernel: [ 6.484606] usb 1-1.1.2.2: The driver for the USB controller dwc_otg_hcd does not support scatter-gather which is
May 20 20:47:58 raspberrypi kernel: [ 6.484618] usb 1-1.1.2.2: required by the UAS driver. Please try an other USB controller if you wish to use UAS.
May 20 20:47:58 raspberrypi kernel: [ 6.484629] usb-storage 1-1.1.2.2:1.0: USB Mass Storage device detected
May 20 20:47:58 raspberrypi kernel: [ 6.485153] scsi host1: usb-storage 1-1.1.2.2:1.0
May 20 20:47:58 raspberrypi kernel: [ 7.273231] scsi 0:0:0:0: Direct-Access Seagate Expansion 0708 PQ: 0 ANSI: 6
May 20 20:47:58 raspberrypi kernel: [ 7.384400] sd 0:0:0:0: Attached scsi generic sg0 type 0
May 20 20:47:58 raspberrypi kernel: [ 7.506900] uart-pl011 3f201000.serial: no DMA platform data
May 20 20:47:58 raspberrypi kernel: [ 7.514781] scsi 1:0:0:0: Direct-Access Seagate Expansion 0502 PQ: 0 ANSI: 6
May 20 20:47:58 raspberrypi kernel: [ 7.520502] sd 1:0:0:0: [sdb] Spinning up disk…
May 20 20:47:58 raspberrypi kernel: [ 7.521023] sd 1:0:0:0: Attached scsi generic sg1 type 0
May 20 20:47:58 raspberrypi kernel: [ 7.909954] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
May 20 20:47:59 raspberrypi kernel: [ 8.094074] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 20 20:47:59 raspberrypi kernel: [ 8.094110] brcmfmac: power management disabled
May 20 20:47:59 raspberrypi kernel: [ 8.552118] .
May 20 20:47:59 raspberrypi kernel: [ 8.566551] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
May 20 20:48:00 raspberrypi kernel: [ 9.592049] .ready
May 20 20:48:00 raspberrypi kernel: [ 9.592832] sd 1:0:0:0: [sdb] 3907029167 512-byte logical blocks: (2.00 TB/1.82 TiB)
May 20 20:48:00 raspberrypi kernel: [ 10.004033] sd 1:0:0:0: [sdb] Write Protect is off
May 20 20:48:00 raspberrypi kernel: [ 10.004051] sd 1:0:0:0: [sdb] Mode Sense: 4f 00 00 00
May 20 20:48:00 raspberrypi kernel: [ 10.004607] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
May 20 20:48:00 raspberrypi kernel: [ 10.023561] sdb: sdb1
May 20 20:48:00 raspberrypi kernel: [ 10.027441] sd 1:0:0:0: [sdb] Attached SCSI disk
May 20 20:48:01 raspberrypi kernel: [ 10.559536] fuse init (API version 7.27)
May 20 20:48:02 raspberrypi kernel: [ 11.729002] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16).
May 20 20:48:02 raspberrypi kernel: [ 11.730584] sd 0:0:0:0: [sda] 7814037167 512-byte logical blocks: (4.00 TB/3.64 TiB)
May 20 20:48:02 raspberrypi kernel: [ 11.730592] sd 0:0:0:0: [sda] 4096-byte physical blocks
May 20 20:48:02 raspberrypi kernel: [ 11.731475] sd 0:0:0:0: [sda] Write Protect is off
May 20 20:48:02 raspberrypi kernel: [ 11.731483] sd 0:0:0:0: [sda] Mode Sense: 47 00 00 08
May 20 20:48:02 raspberrypi kernel: [ 11.732746] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
May 20 20:48:02 raspberrypi kernel: [ 11.865369] sda: sda1
May 20 20:48:02 raspberrypi kernel: [ 11.870918] sd 0:0:0:0: [sda] Attached SCSI disk
May 20 20:48:04 raspberrypi kernel: [ 13.928522] Bluetooth: Core ver 2.22
May 20 20:48:04 raspberrypi kernel: [ 13.928581] NET: Registered protocol family 31
May 20 20:48:04 raspberrypi kernel: [ 13.928584] Bluetooth: HCI device and connection manager initialized
May 20 20:48:04 raspberrypi kernel: [ 13.928598] Bluetooth: HCI socket layer initialized
May 20 20:48:04 raspberrypi kernel: [ 13.928604] Bluetooth: L2CAP socket layer initialized
May 20 20:48:04 raspberrypi kernel: [ 13.928623] Bluetooth: SCO socket layer initialized
May 20 20:48:04 raspberrypi kernel: [ 13.990967] Bluetooth: HCI UART driver ver 2.3
May 20 20:48:04 raspberrypi kernel: [ 13.990977] Bluetooth: HCI UART protocol H4 registered
May 20 20:48:04 raspberrypi kernel: [ 13.991020] Bluetooth: HCI UART protocol Three-wire (H5) registered
May 20 20:48:04 raspberrypi kernel: [ 13.991138] Bluetooth: HCI UART protocol Broadcom registered
May 20 20:48:05 raspberrypi kernel: [ 14.496943] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
May 20 20:48:05 raspberrypi kernel: [ 14.496951] Bluetooth: BNEP filters: protocol multicast
May 20 20:48:05 raspberrypi kernel: [ 14.496967] Bluetooth: BNEP socket layer initialized
May 20 20:48:05 raspberrypi kernel: [ 14.558718] Bluetooth: RFCOMM TTY layer initialized
May 20 20:48:05 raspberrypi kernel: [ 14.558740] Bluetooth: RFCOMM socket layer initialized
May 20 20:48:05 raspberrypi kernel: [ 14.558762] Bluetooth: RFCOMM ver 1.11
May 20 20:48:12 raspberrypi kernel: [ 21.054126] EXT4-fs (mmcblk0p5): mounted filesystem with ordered data mode. Opts: (null)
May 20 20:48:12 raspberrypi kernel: [ 21.274192] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
voilà lol
mais bon j’ai l’impression que c’est le resultat d’après le redémarrage suite au plantage…
Hello,
Rien de bien suspect là-dedans.
Sinon que je vois à 21h11 une synchronisation de temps. J’ai déjà constaté sur mon RPI une perte de montage au changement d’heure d’hiver (ou été). Ceci peut-il être une cause de plantage ? On peut en douter. En tout cas, tout va bien jusque 20h48.
Le plantage date de quand ? Avant 20h47 ? Dans ce cas, il nous faudrait la log au moment du plantage. Dès que j’ai une minute, je regarde comment tu peux avoir ça.
Je suppose que ce sont les deux seuls fichiers qui ont bougé ?
Normalement, syslog et kernel.log ne sont pas réinitialisés au boot, et s’il y a une erreur mémorisée, on devrait l’avoir dans ce que tu as posté si le plantage est postérieur à 20:48:05 (syslog), voire 20:47:58 (kernel.log).
Ce qui veut dire que le problème n’est pas dans ces logs. L’info que ça donne, si le raisonnement se répète pour les autres logs, c’est que c’est un problème non géré correctement par le logiciel fautif.
C’est décevant, j’en conviens.
Ce que j’essaierais en dernier recours, c’est de désactiver la synchro horaire (celle qui génère la ligne « May 20 21:11:03 raspberrypi systemd[1]: Time has been changed »).
Par contre, quand tu dis que tu ne vois rien dans le cron, tu as bien vérifié l’ensemble des comptes ? C’est-à-dire dans /var/spool/cron/crontabs, de manière à voir l’ensemble des tâches cron de tous les utilisateurs ?
Suis les conseils de @nabla : « petit à petit »
Moi j’arrêterais le service plex et j’attendrais 2 heures de voir si ça plante.
Si oui tu te concentres sur plex
Si non tu continues tes investigations
re,
j’ai toujours mon souci. en fait je me rends compte que c’est surement backintime qui fait planter. pourtant quand j’ai commencé à avoir le problème, je l’ai désinstaller. souci, c’est que je me rends compte que j’ai un dossier de sauvegarde qui se créé toujours régulièrement, et les horaires ont l’air de correspondre aux plantages. comment cela ce peut ? comment être sur de bien supprimer backintime ?
merci
Salut,
Je crois que :
sudo apt-get remove backintime*
sudo apt-get purge backintime*
peut être un bon début.
++
Bonjour,
J’ai eu sur une PI le même symptôme à chaque fois que je lançait une opération, ça plantait. J’ai cru que c’était le logiciel en question mais non, c’était la carte SD qui était défectueuse juste sur cet endroit. La solution à été de changer de carte SD.
A+
merci je teste et je vous dit. sinon je verrais avec une autre carte sd.
Bon j’ai essayé y’a rien à faire. les sauvegardes se font toujours…
ca me gonfle. meme quand les disques ne sont pas branchés ça plante. je vais acheter une autre carte sd. j’essaierai d’abord avec une duplication, et si le problème continue, je réinstallerai tout…… raspberry pi rime avec pourri….
Salut,
J’ai :
- 1 Rpi3B+
- 1 Rpi3B (Rpi3)
- 1 Rpi2B (Rpi2)
- 1 Rpi1b+
- 2 RpiZero V1.3
Pas de souci.
Oui, j’ai eu des difficultés à surmonter ; ça je ne le nie pas.
En gros, on ne paye presque pas le « matériel » ; on ne paye pas le « logiciel » ; on doit donc faire nous même.
Ouais un Mac Mini, ça tourne, mais c’est plus gros, c’est moins libre et c’est plus cher
Si tu as une clef USB, tu peux commencer par tenter de cloner ton système dessus pour voir.
Tu peux aussi essayer de réinstaller en partant de zéro pour voir.
Courage !