Bonjour à tous, ayant du temps j'ai voulu me lancer dans une manip qui sans que je comprenne pourquoi à complétement planter mon raspberry pi 0. Pourtant, j'ai uniquement voulu installer certbot et generer un certificat en local…
Mais mantenant le systeme ne parviens pas à booter correctement, on dirait que les erreurs commence avec
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ TIME ] Timed out waiting for device ▒▒v/disk/by-partuuid/e724c016-01.
[DEPEND] Dependency failed for File …v/disk/by-partuuid/e724c016-01.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.Quelqu'un aurait une idée me permettant de sauver mon systeme (j'ai passer beaucoup de temps à le configurer ce me tente pas trop de tout recommencer from scratch)?
Merci d'avance
Voici le log complet du systeme, il est impossible de reprendre la main dessus.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.14.52+ (dc4@dc4-XPS13-9333) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1123 Wed Jun 27 17:05:32 BST 2018
[ 0.000000] CPU: ARMv6-compatible processor [410fb767] revision 7 (ARMv7), cr=00c5387d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT nonaliasing instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi Zero W Rev 1.1
[ 0.000000] Memory policy: Data cache writeback
[ 0.000000] cma: Reserved 8 MiB at 0x1b400000
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 113680
[ 0.000000] Kernel command line: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 smsc95xx.macaddr=B8:27:EB:82:60:B3 vc_mem.mem_base=0x1ec00000 vc_mem.mem_size=0x20000000 dwc_otg.lpm_enable=0 console=ttyS0,115200 console=tty1 root=PARTUUID=e724c016-02 rootfstype=ext4 elevator=deadline fsck.repair=no rootwait
[ 0.000000] PID hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.000000] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
[ 0.000000] Memory: 435260K/458752K available (6422K kernel code, 587K rwdata, 1988K rodata, 440K init, 677K bss, 15300K reserved, 8192K cma-reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
[ 0.000000] vmalloc : 0xdc800000 - 0xff800000 ( 560 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xdc000000 ( 448 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc064ddac (6424 kB)
[ 0.000000] .init : 0xc08ca000 - 0xc0938000 ( 440 kB)
[ 0.000000] .data : 0xc0938000 - 0xc09cae90 ( 588 kB)
[ 0.000000] .bss : 0xc09d07d0 - 0xc0a79d1c ( 678 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
[ 0.000000] ftrace: allocating 24096 entries in 71 pages
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000030] sched_clock: 32 bits at 1000kHz, resolution 1000ns, wraps every 2147483647500ns
[ 0.000073] clocksource: timer: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275 ns
[ 0.000166] bcm2835: system timer (irq = 27)
[ 0.000726] Console: colour dummy device 80x30
[ 0.001313] console [tty1] enabled
[ 0.001372] Calibrating delay loop... 697.95 BogoMIPS (lpj=3489792)
[ 0.060340] pid_max: default: 32768 minimum: 301
[ 0.060856] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.060910] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.062234] Disabling memory control group subsystem
[ 0.062454] CPU: Testing write buffer coherency: ok
[ 0.063573] Setting up static identity map for 0x8200 - 0x8238
[ 0.064860] devtmpfs: initialized
[ 0.073705] random: get_random_u32 called from bucket_table_alloc+0x88/0x1c4 with crng_init=0
[ 0.074604] VFP support v0.3: implementor 41 architecture 1 part 20 variant b rev 5
[ 0.075022] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.075094] futex hash table entries: 256 (order: -1, 3072 bytes)
[ 0.076442] pinctrl core: initialized pinctrl subsystem
[ 0.077834] NET: Registered protocol family 16
[ 0.080818] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[ 0.087236] hw-breakpoint: found 6 breakpoint and 1 watchpoint registers.
[ 0.087306] hw-breakpoint: maximum watchpoint size is 4 bytes.
[ 0.087454] Serial: AMBA PL011 UART driver
[ 0.090242] bcm2835-mbox 2000b880.mailbox: mailbox enabled
[ 0.091114] uart-pl011 20201000.serial: could not find pctldev for node /soc/gpio@7e200000/uart0_pins, deferring probe
[ 0.130913] bcm2835-dma 20007000.dma: DMA legacy API manager at dc80d000, dmachans=0x1
[ 0.133201] SCSI subsystem initialized
[ 0.133468] usbcore: registered new interface driver usbfs
[ 0.133604] usbcore: registered new interface driver hub
[ 0.133851] usbcore: registered new device driver usb
[ 0.140798] raspberrypi-firmware soc:firmware: Attached to firmware from 2018-07-03 14:15
[ 0.142810] clocksource: Switched to clocksource timer
[ 0.231214] VFS: Disk quotas dquot_6.6.0
[ 0.231394] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.231722] FS-Cache: Loaded
[ 0.232077] CacheFiles: Loaded
[ 0.249169] NET: Registered protocol family 2
[ 0.250398] TCP established hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.250532] TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
[ 0.250649] TCP: Hash tables configured (established 4096 bind 4096)
[ 0.250827] UDP hash table entries: 256 (order: 0, 4096 bytes)
[ 0.250885] UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
[ 0.251273] NET: Registered protocol family 1
[ 0.252005] RPC: Registered named UNIX socket transport module.
[ 0.252062] RPC: Registered udp transport module.
[ 0.252090] RPC: Registered tcp transport module.
[ 0.252114] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.254119] hw perfevents: no irqs for PMU, sampling events not supported
[ 0.254245] hw perfevents: enabled with armv6_1176 PMU driver, 3 counters available
[ 0.257919] workingset: timestamp_bits=14 max_order=17 bucket_order=3
[ 0.269884] FS-Cache: Netfs 'nfs' registered for caching
[ 0.271246] NFS: Registering the id_resolver key type
[ 0.271344] Key type id_resolver registered
[ 0.271374] Key type id_legacy registered
[ 0.271422] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.276168] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 251)
[ 0.276645] io scheduler noop registered
[ 0.276696] io scheduler deadline registered (default)
[ 0.277241] io scheduler cfq registered
[ 0.277290] io scheduler mq-deadline registered
[ 0.277319] io scheduler kyber registered
[ 0.279631] BCM2708FB: allocated DMA memory 5b500000
[ 0.279743] BCM2708FB: allocated DMA channel 0 @ dc80d000
[ 0.287754] Console: switching to colour frame buffer device 82x26
[ 0.296608] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled
[ 0.301982] bcm2835-rng 20104000.rng: hwrng registered
[ 0.305142] vc-mem: phys_addr:0x00000000 mem_base=0x1ec00000 mem_size:0x20000000(512 MiB)
[ 0.311423] vc-sm: Videocore shared memory driver
[ 0.314876] gpiomem-bcm2835 20200000.gpiomem: Initialised: Registers at 0x20200000
[ 0.338706] brd: module loaded
[ 0.353566] loop: module loaded
[ 0.356280] Loading iSCSI transport class v2.0-870.
[ 0.359732] usbcore: registered new interface driver smsc95xx
[ 0.362442] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.593561] Core Release: 2.80a
[ 0.596192] Setting default values for core params
[ 0.598813] Finished setting default values for core params
[ 0.801784] Using Buffer DMA mode
[ 0.804546] Periodic Transfer Interrupt Enhancement - disabled
[ 0.807279] Multiprocessor Interrupt Enhancement - disabled
[ 0.810052] OTG VER PARAM: 0, OTG VER FLAG: 0
[ 0.813006] Dedicated Tx FIFOs mode
[ 0.816704] WARN::dwc_otg_hcd_init:1046: FIQ DMA bounce buffers: virt = 0xdb514000 dma = 0x5b514000 len=9024
[ 0.822392] FIQ FSM acceleration enabled for :
[ 0.822392] Non-periodic Split Transactions
[ 0.822392] Periodic Split Transactions
[ 0.822392] High-Speed Isochronous Endpoints
[ 0.822392] Interrupt/Control Split Transaction hack enabled
[ 0.835648] WARN::hcd_init_fiq:459: FIQ on core 0 at 0xc049a438
[ 0.838274] WARN::hcd_init_fiq:460: FIQ ASM at 0xc049a714 length 36
[ 0.840852] WARN::hcd_init_fiq:486: MPHI regs_base at 0xdc8a5000
[ 0.843614] dwc_otg 20980000.usb: DWC OTG Controller
[ 0.846290] dwc_otg 20980000.usb: new USB bus registered, assigned bus number 1
[ 0.849012] dwc_otg 20980000.usb: irq 56, io mem 0x00000000
[ 0.851641] Init: Port Power? op_state=1
[ 0.854256] Init: Power Port (0)
[ 0.857096] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 0.859723] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.862315] usb usb1: Product: DWC OTG Controller
[ 0.864920] usb usb1: Manufacturer: Linux 4.14.52+ dwc_otg_hcd
[ 0.867494] usb usb1: SerialNumber: 20980000.usb
[ 0.871168] hub 1-0:1.0: USB hub found
[ 0.873838] hub 1-0:1.0: 1 port detected
[ 0.877678] usbcore: registered new interface driver usb-storage
[ 0.880620] mousedev: PS/2 mouse device common for all mice
[ 0.883250] IR NEC protocol handler initialized
[ 0.885720] IR RC5(x/sz) protocol handler initialized
[ 0.888182] IR RC6 protocol handler initialized
[ 0.890575] IR JVC protocol handler initialized
[ 0.892946] IR Sony protocol handler initialized
[ 0.895316] IR SANYO protocol handler initialized
[ 0.897659] IR Sharp protocol handler initialized
[ 0.899891] IR MCE Keyboard/mouse protocol handler initialized
[ 0.902155] IR XMP protocol handler initialized
[ 0.905776] bcm2835-wdt 20100000.watchdog: Broadcom BCM2835 watchdog timer
[ 0.908714] bcm2835-cpufreq: min=700000 max=1000000
[ 0.911766] sdhci: Secure Digital Host Controller Interface driver
[ 0.914298] sdhci: Copyright(c) Pierre Ossman
[ 0.917301] mmc-bcm2835 20300000.mmc: could not get clk, deferring probe
[ 0.920448] sdhost-bcm2835 20202000.mmc: could not get clk, deferring probe
[ 0.923277] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.926360] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.929090] hidraw: raw HID events driver (C) Jiri Kosina
[ 0.931984] usbcore: registered new interface driver usbhid
[ 0.934707] usbhid: USB HID core driver
[ 0.938225] vchiq: vchiq_init_state: slot_zero = db580000, is_master = 0
[ 0.942775] [vc_sm_connected_init]: start
[ 0.953151] [vc_sm_connected_init]: end - returning 0
[ 0.956897] Initializing XFRM netlink socket
[ 0.959687] NET: Registered protocol family 17
[ 0.962528] Key type dns_resolver registered
[ 0.967000] registered taskstats version 1
[ 0.978138] uart-pl011 20201000.serial: cts_event_workaround enabled
[ 0.981198] 20201000.serial: ttyAMA0 at MMIO 0x20201000 (irq = 81, base_baud = 0) is a PL011 rev2
[ 0.989455] console [ttyS0] disabled
[ 0.992331] 20215040.serial: ttyS0 at MMIO 0x0 (irq = 160, base_baud = 31250000) is a 16550
[ 1.952705] console [ttyS0] enabled
[ 1.960832] mmc-bcm2835 20300000.mmc: mmc_debug:0 mmc_debug2:0
[ 1.969771] mmc-bcm2835 20300000.mmc: DMA channel allocated
[ 2.036339] sdhost: log_buf @ db513000 (5b513000)
[ 2.078445] random: fast init done
[ 2.086367] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 2.096435] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 2.106433] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 2.117458] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 2.125549] mmc0: sdhost-bcm2835 loaded - DMA enabled (>1)
[ 2.135060] of_cfs_init
[ 2.140084] of_cfs_init: OK
[ 2.166800] Waiting for root device PARTUUID=e724c016-02...
[ 2.220885] mmc0: host does not support reading read-only switch, assuming write-enable
[ 2.236126] mmc0: Problem switching card into high-speed mode!
[ 2.245493] mmc0: new SDHC card at address 0001
[ 2.253779] mmcblk0: mmc0:0001 SD32G 29.0 GiB (quirks 0x80000000)
[ 2.265895] mmcblk0: p1 p2
[ 2.314157] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 2.327570] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 2.350849] mmc1: new high speed SDIO card at address 0001
[ 2.360621] devtmpfs: mounted
[ 2.368794] Freeing unused kernel memory: 440K
[ 2.376037] This architecture does not have kernel memory protection.
[ 3.622138] systemd[1]: System time before build time, advancing clock.
[ 3.871601] NET: Registered protocol family 10
[ 3.881236] Segment Routing with IPv6
[ 3.920102] ip_tables: (C) 2000-2006 Netfilter Core Team
[ 3.981219] systemd[1]: systemd 244.3-1+rpi1 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
[ 4.017760] systemd[1]: Detected architecture arm.
[ 4.064909] systemd[1]: Set hostname to <raspberrypi>.
[ 7.174795] systemd[1]: /lib/systemd/system/dbus.socket:5: ListenStream= references a path below legacy directory /var/run/, updating /var/run/dbus/system_bus_socket → /run/dbus/system_bus_socket; please update the unit file accordingly.
[ 7.294879] systemd[1]: /lib/systemd/system/redis-server.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/redis/redis-server.pid → /run/redis/redis-server.pid; please update the unit file accordingly.
[ 7.327011] systemd[1]: /lib/systemd/system/redis-server.service:14: Unknown key name 'RunTimeDirectory' in section 'Service', ignoring.
[ 7.404140] systemd[1]: /lib/systemd/system/postgresql@.service:14: PIDFile= references a path below legacy directory /var/run/, updating /var/run/postgresql/9.6-main.pid → /run/postgresql/9.6-main.pid; please update the unit file accordingly.
[ 7.658492] systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
[ 7.745935] systemd[1]: /lib/systemd/system/avahi-daemon.socket:6: ListenStream= references a path below legacy directory /var/run/, updating /var/run/avahi-daemon/socket → /run/avahi-daemon/socket; please update the unit file accordingly.
[ 8.127431] random: systemd: uninitialized urandom read (16 bytes read)
[ 8.138962] systemd[1]: system-getty.slice: unit configures an IP firewall, but the local system does not support BPF/cgroup firewalling.
[ 8.159527] systemd[1]: (This warning is only shown for the first unit using IP firewalling.)
[ 8.182318] systemd[1]: Created slice system-getty.slice.
[ 8.197341] random: systemd: uninitialized urandom read (16 bytes read)
[ 8.210481] systemd[1]: Created slice system-postfix.slice.
[ 8.225073] random: systemd: uninitialized urandom read (16 bytes read)
[ 8.238138] systemd[1]: Created slice system-postgresql.slice.
[ 8.255260] systemd[1]: Created slice system-serial\x2dgetty.slice.
[ 8.272658] systemd[1]: Created slice system-systemd\x2dfsck.slice.
[ 8.289810] systemd[1]: Created slice User and Session Slice.
[ 8.304980] systemd[1]: Started Forward Password Requests to Wall Directory Watch.
[ 8.326979] systemd[1]: Set up automount Arbitrary Executable File Formats File System Automount Point.
[ 8.349838] systemd[1]: Reached target Slices.
[ 8.363032] systemd[1]: Reached target Swap.
[ 8.377107] systemd[1]: Listening on Syslog Socket.
[ 8.391476] systemd[1]: Listening on fsck to fsckd communication Socket.
[ 8.407594] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 8.454268] systemd[1]: Condition check resulted in Journal Audit Socket being skipped.
[ 8.471345] systemd[1]: Listening on Journal Socket (/dev/log).
[ 8.487580] systemd[1]: Listening on Journal Socket.
[ 8.502535] systemd[1]: Listening on udev Control Socket.
[ 8.517068] systemd[1]: Listening on udev Kernel Socket.
[ 8.532086] systemd[1]: Condition check resulted in Huge Pages File System being skipped.
[ 8.556120] systemd[1]: Mounting POSIX Message Queue File System...
[ 8.600983] systemd[1]: Mounting RPC Pipe File System...
[ 8.660558] systemd[1]: Mounting Kernel Debug File System...
[ 8.693903] systemd[1]: Condition check resulted in Kernel Module supporting RPCSEC_GSS being skipped.
[ 8.731157] systemd[1]: Starting Restore / save the current clock...
[ 8.788237] systemd[1]: Starting Set the console keyboard layout...
[ 8.849028] systemd[1]: Starting Create list of static device nodes for the current kernel...
[ 8.929320] systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped.
[ 8.995015] systemd[1]: Starting File System Check on Root Device...
[ 9.075184] systemd[1]: Starting Journal Service...
[ 9.190114] systemd[1]: Starting Load Kernel Modules...
[ 9.349529] systemd[1]: Mounted POSIX Message Queue File System.
[ 9.438904] systemd[1]: Mounted RPC Pipe File System.
[ 9.498787] systemd[1]: Mounted Kernel Debug File System.
[ 9.623134] systemd[1]: Started Restore / save the current clock.
[ 9.743164] systemd[1]: Started Create list of static device nodes for the current kernel.
[ 9.859312] systemd[1]: Started Load Kernel Modules.
[ 9.911417] systemd[1]: Condition check resulted in FUSE Control File System being skipped.
[ 10.034192] systemd[1]: Mounting Kernel Configuration File System...
[ 10.244956] systemd[1]: Started File System Check Daemon to report status.
[ 10.344917] systemd[1]: Starting Apply Kernel Variables...
[ 10.513139] systemd[1]: Started File System Check on Root Device.
[ 10.569144] systemd[1]: Mounted Kernel Configuration File System.
[ 10.737267] systemd[1]: Starting Remount Root and Kernel File Systems...
[ OK ] Started Show Plymouth Boot Screen.
[ OK ] Started Forward Password Re…ts to Plymouth Directory Watch.
[ OK ] Reached target Local Encrypted Volumes.
[ OK ] Reached target Paths.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ TIME ] Timed out waiting for device ▒▒v/disk/by-partuuid/e724c016-01.
[DEPEND] Dependency failed for File …v/disk/by-partuuid/e724c016-01.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Stopped Forward Password Requests to Wall Directory Watch.
Starting Enable support for…al executable binary formats...
Starting Set console font and keymap...
Starting Raise network interfaces...
Starting Preprocess NFS configuration...
[ OK ] Reached target Login Prompts.
[ OK ] Reached target Timers.
[ OK ] Closed Syslog Socket.
[ OK ] Reached target Sockets.
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
Starting Tell Plymouth To Write Out Runtime Data...
Starting Create Volatile Files and Directories...
[ OK ] Started Set console font and keymap.
[ OK ] Started Preprocess NFS configuration.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
Mounting Arbitrary Executable File Formats File System...
[ OK ] Reached target NFS client services.
[ OK ] Reached target Remote File Systems (Pre).
[ OK ] Reached target Remote File Systems.
[ OK ] Mounted Arbitrary Executable File Formats File System.
[ OK ] Started Enable support for …onal executable binary formats.
[ OK ] Started Create Volatile Files and Directories.
Starting Network Time Synchronization...
Starting Update UTMP about System Boot/Shutdown...
[ OK ] Started Update UTMP about System Boot/Shutdown.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Update UTMP about System Runlevel Changes.
[ OK ] Started Raise network interfaces.
[ OK ] Reached target Network.
[ OK ] Reached target Network is Online.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
[ OK ] Started Show Plymouth Boot Screen.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[DEPEND] Dependency failed for Flush Journal to Persistent Storage.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[ OK ] Started Load/Save Random Seed.
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ TIME ] Timed out waiting for device /dev/ttyS0.
[DEPEND] Dependency failed for Serial Getty on ttyS0.
[ TIME ] Timed out waiting for device /dev/serial1.
[ TIME ] Timed out waiting for device ▒▒v/disk/by-partuuid/e724c016-01.
[DEPEND] Dependency failed for File …v/disk/by-partuuid/e724c016-01.
[DEPEND] Dependency failed for /boot.
[DEPEND] Dependency failed for Local File Systems.
[ OK ] Stopped Forward Password Requests to Wall Directory Watch.
Starting Preprocess NFS configuration...
[ OK ] Closed Syslog Socket.
Starting Update UTMP about System Runlevel Changes...
[ OK ] Started Emergency Shell.
[ OK ] Reached target Emergency Mode.
Starting Tell Plymouth To Write Out Runtime Data...
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
[ OK ] Started Preprocess NFS configuration.
[ OK ] Started Tell Plymouth To Write Out Runtime Data.
[ OK ] Started Update UTMP about System Runlevel Changes.
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Journal Service.
See 'systemctl status systemd-journald.service' for details.
[ OK ] Stopped Journal Service.
Starting Journal Service...
[FAILED] Failed to start Network Time Synchronization.
See 'systemctl status systemd-timesyncd.service' for details.
[ OK ] Stopped Network Time Synchronization.
Starting Network Time Synchronization...
Cannot open access to console, the root account is locked.
See sulogin(8) man page for more details.
Press Enter to continue.
# Carte SD HS
Posté par Kerro . Évalué à 4.
Il est fort probable que la carte SD soit fichue.
Il y a d'énormes problèmes de qualité avec les cartes SD, c'est un accident très fréquent.
Tu peux dupliquer ta carte SD avec dd_rescue vers un fichier image, pour ensuite tenter de récupérer des fichiers ou des fragments (TestDisk, PhotoRec, éditeur hexa, etc).
Si tu n'as pas d'adaptateurs SD Card sur un ordinateur « normal », tu peux démarrer le Raspberry avec une clef USB, par exemple avec Raspbian. Ensuite tu installes dd_rescue.
[^] # Re: Carte SD HS
Posté par TheBreton . Évalué à 1.
Merci d'avoir pris le temps de répondre, sans pouvoir exclure un défaillance de la carte sd je n'en reconnais pas les symptômes.
La carte se mount tres bien avec un adaptateur usb et je la parcours sans soucis de lecture, mon home et mes dev. sont accessible et backuper ailleurs. C'est plus l'installation d'appli exotique non package voir non dispo pour l'arch armv6 que j'avais hacker pour fonctionner qui me tente pas de refaire, ainsi qu'une bdd à backuper qui me fatigue à l'avance.
La concomitance des actions installation de certbot, de création d'un certificat et de plantage totale du système me laisse espérer une guérison du système…mais sans savoir par ou commencer.
[^] # Re: Carte SD HS
Posté par Anonyme . Évalué à 3. Dernière modification le 10 avril 2020 à 21:30.
Le problème n'est pas la lecture, mais l'écriture. La mémoire NAND de la SD est usée et ne peut plus écrire de nouvelles données.
[^] # Re: Carte SD HS
Posté par Kerro . Évalué à 3.
Puisque tu peux tout relire, quel est ton problème ?
[^] # Re: Carte SD HS
Posté par Anonyme . Évalué à 4.
Ce n'est pas qu'un problème de qualité, c'est avant tout un problème de support de stockage non adapté à l'utilisation. Le controleur d'une SD, comme celui d'une clé USB, n'est pas conçu pour supporter les écritures d'un OS, encore moins sur un fs de type ext.
De plus, le RPi est réputé pour corrompre les données sur les SD si l'alimentation fait défaut ou si l'OS ne s'arrète pas correctement.
Solution : ne garder sur la SD que la partition /boot et déporter le reste sur un autre support. Ça demandera éventuellement une connexion UART pour paramétrer uboot.
[^] # Re: Carte SD HS
Posté par Anonyme . Évalué à 1.
et que donne : systemctl status systemd-timesyncd.service ?
je tenterais de deplacer les fichier systemd qui pose pb, puis si cela continue de reinstaller systemd et ses ouates milles dépendance
[^] # Re: Carte SD HS
Posté par TheBreton . Évalué à 1.
A l'issus du boot, actuelle impossible de lancer un shell,ca boucle sur le message d'erreur, c'est un pi-zero-hw, donc rien d'autre que le port série ne fonctionne (j'ai câbler un adaptateur ttl-usb) pour voir ce qui se passe.
Je tenterais la manip de gUI dans le topic du dessous quand j'aurais recu une nouvelle carte pour assurer un fonctionnement minimum
[^] # Re: Carte SD HS
Posté par Anonyme . Évalué à 1.
comme tu parle d'un port serie, il est possible que le message d'erreur s'affiche de manière continuel mais n'empeche pas la saisie en aveugle de commande, ca m'arrivait avec syslog de temps en temps qui s'affiche sur la console principal
tu peux te logger malgré le remplissage de ton écran, fait comme si de rien était et arrête systemd, ou redirige les erreur de syslog vers /dev/null
et sinon un chroot ? ca ne ferais pas le taf ?
https://doc.ubuntu-fr.org/chroot
# Reprendre la main
Posté par gUI (Mastodon) . Évalué à 4. Dernière modification le 11 avril 2020 à 09:10.
Tu peux modifier le fichier
cmdline.txt(partition FAT sur ta carte SD) pour lui dire de booter directement sur un shell. De là tu pourras essayer de voir ce qui déconne (mais ce sera pas simple).https://samx18.io/blog/2017/11/05/piBootIssue.html
Après si c'est juste qu'il y a de la config que tu veux pas perdre, tu mountes ta carte SD sur un Linux, tu récupères tous les fichiers qui t'intéressent (dans /etc vraisemblablement) et tu réinstalles un truc tout neuf.
En théorie, la théorie et la pratique c'est pareil. En pratique c'est pas vrai.
[^] # Re: Reprendre la main
Posté par TheBreton . Évalué à 1.
Merci pour le lien, je vais agir en deux phases, la première c'est acheter une nouvelle sdcard et refaire les modificiations et configuration (en faisant de la documentation au passage) ca sera toujours utiles pour au cas ou ;-) Pour cette phase, la carte actuelle ne sera modifiée. Je rajouterais aussi un backup dans le cloud de ma bdd et des scripts qui la remplisse et l'utilise.
Si tout se passe bien(ou si cela se passe mal) je passerais à la modification sur la carte actuelle pour voir si c'était réparable et voir un peut l'entendu des dégats subis par le système.
[^] # Re: Reprendre la main
Posté par totof2000 . Évalué à 2.
Pourquoi ne pas utiliser un repo git et Ansible (ou équivalent, si tu maitrises Python il doit y avoir des outils plus light style Fabric) pour appliquer tes modifs ?
Tu pourras les refaire sans problème si un jour ta carte SD lache a nouveau.
[^] # Re: Reprendre la main
Posté par NeoX . Évalué à 2.
ca va te faire un backup complet de la carte
tu peux alors agir sur celle-ci
et si besoin, revenir à l'état de depart en faisant l'inverse
Suivre le flux des commentaires
Note : les commentaires appartiennent à celles et ceux qui les ont postés. Nous n’en sommes pas responsables.