[RESOLU] Problème initialisation pfSense SG-2220
-
Bonjour,
Je me permets de vous solliciter car je rencontre un problème lors d'un redémarrage d'un pfSense SG-2220 (version 2.3.2-release-p1), après quelques semaine d'inutilisations.
Il n’arrive pas à se démarrer proprement et ne charge pas avec sa configuration, il démarre bien, mais lorsque je me connecte en console sur le routeur :
L’affichage est ainsi:**Warning**: require_once(config.inc): failed to open stream: No such file or directory in **/etc/rc.banner** on line **56** **Fatal error**: require_once(): Failed opening required 'config.inc' (include_path='.:/usr/local/share/pear') in **/etc/rc.banner** on line **56** 0) Logout (SSH only) 9) pfTop 1) Assign Interfaces 10) Filter Logs 2) Set interface(s) IP address 11) Restart webConfigurator 3) Reset webConfigurator password 12) PHP shell + pfSense tools 4) Reset to factory defaults 13) Update from console 5) Reboot system 14) Enable Secure Shell (sshd) 6) Halt system 15) Restore recent configuration 7) Ping host 16) Restart PHP-FPM 8) ShellAucune commande ne fonctionne sauf le passage en ligne commande (8) Shell), avec à chaque fois des messages d’erreurs.
Exemple pour le ping option 7 :**Fatal error**: require_once(): Failed opening required 'config.inc' (include_path='.:/usr/local/share/pear') in **/etc/rc.initial.ping** on line **59** **Warning**: require_once(config.inc): failed to open stream: No such file or directory in **/etc/rc.banner** on line **56** **Fatal error**: require_once(): Failed opening required 'config.inc' (include_path='.:/usr/local/share/pear') in **/etc/rc.banner** on line **56**Lorsque je le redémarre, il indique faire un redémarrage après panique, et passe en lecture seule. Puis il ne trouve pas les fichiers de configurations. Voici le log, d’un redémarrage :
SeaBIOS (version SageBIOS-20160122_083316-localhost.localdomain) iPXE (http://ipxe.org) 00:14.0 C100 PCI2.10 PnP PMM+7FB7D480+7FADD480 C100 iPXE (http://ipxe.org) 00:14.1 C200 PCI2.10 PnP PMM 7FB7D480 7FADD480 C200 iPXE (http://ipxe.org) 00:14.2 C300 PCI2.10 PnP PMM 7FB7D480 7FADD480 C300 iPXE (http://ipxe.org) 00:14.3 C400 PCI2.10 PnP PMM 7FB7D480 7FADD480 C400 Press F12 for boot menu. F1 pfSense F6 PXE Boot: F1 - __ ____ _ __ / _/ ___| ___ _ __ ___ ___ | '_ \| |_\___ \ / _ \ '_ \/ __|/ _ \ | |_) | _|___) | __/ | | \__ \ __/ | .__/|_| |____/ \___|_| |_|___/\___| |_| +============Welcome to pfSense===========+ | | ______ | 1\. Boot Multi User [Enter] | / \ | 2\. Boot [s]ingle User | _____/ f \ | 3\. [Esc]ape to loader prompt | / \ / | 4\. Reboot | / p \______/ Sense | | \ / \ | Options: | \_____/ \ | 5\. [K]ernel: kernel (1 of 2) | \ / | 6\. Configure Boot [O]ptions... | \______/ | | | | | | +=========================================+ /boot/kernel/kernel text=0x1292e98 data=0x8a1bb0+0x23ec20 syms=[0x8+0x177708+0x8+0x173ed4] Booting... KDB: debugger backends: ddb KDB: current backend: ddb Copyright (c) 1992-2016 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 10.3-RELEASE-p9 #1 5fc1b19(RELENG_2_3_2): Tue Sep 27 12:25:49 CDT 2016 root@factory23-amd64-builder:/builder/factory-232/tmp/obj/builder/factory-232/tmp/FreeBSD-src/sys/pfSense amd64 FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512 CPU: Intel(R) Atom(TM) CPU C2338 @ 1.74GHz (1750.04-MHz K8-class CPU) Origin="GenuineIntel" Id=0x406d8 Family=0x6 Model=0x4d Stepping=8 Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Features2=0x43d8e3bf <sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,movbe,popcnt,tscdlt,aesni,rdrand>AMD Features=0x28100800 <syscall,nx,rdtscp,lm>AMD Features2=0x101 <lahf,prefetch>Structured Extended Features=0x2282 <tscadj,smep,erms,nfpusg>VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID TSC: P-state invariant, performance statistics real memory = 2143150080 (2043 MB) avail memory = 2034401280 (1940 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: <core coreboot=""> FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 2 random: <software, yarrow=""> initialized ioapic0 <version 2.0=""> irqs 0-23 on motherboard wlan: mac acl policy registered ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80620930, 0) error 1 ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff806209e0, 0) error 1 ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/. ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80620a90, 0) error 1 iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (iwi_bss_fw, 0xffffffff80647c30, 0) error 1 iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (iwi_ibss_fw, 0xffffffff80647ce0, 0) error 1 iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi/. iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf. module_register_init: MOD_LOAD (iwi_monitor_fw, 0xffffffff80647d90, 0) error 1 netmap: loaded module kbd0 at kbdmux0 module_register_init: MOD_LOAD (vesa, 0xffffffff81016c90, 0) error 19 cryptosoft0: <software crypto=""> on motherboard padlock0: No ACE support. acpi0: <core coreboot=""> on motherboard acpi0: Power Button (fixed) hpet0: invalid period device_attach: hpet0 attach returned 6 cpu0: <acpi cpu=""> on acpi0 cpu1: <acpi cpu=""> on acpi0 hpet0: invalid period device_attach: hpet0 attach returned 6 atrtc0: <at realtime="" clock=""> port 0x70-0x77 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 attimer0: <at timer=""> port 0x40-0x43,0x50-0x53 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 Timecounter "ACPI-safe" frequency 3579545 Hz quality 850 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: <acpi host-pci="" bridge=""> port 0xcf8-0xcff on acpi0 pci0: <acpi pci="" bus=""> on pcib0 pcib1: <acpi pci-pci="" bridge=""> mem 0xdfee0000-0xdfefffff irq 16 at device 1.0 on pci0 pci1: <acpi pci="" bus=""> on pcib1 pcib2: <acpi pci-pci="" bridge=""> mem 0xdff00000-0xdff1ffff irq 19 at device 2.0 on pci0 pci2: <acpi pci="" bus=""> on pcib2 pcib3: <acpi pci-pci="" bridge=""> mem 0xdff20000-0xdff3ffff irq 20 at device 3.0 on pci0 pci3: <acpi pci="" bus=""> on pcib3 pcib4: <acpi pci-pci="" bridge=""> mem 0xdff40000-0xdff5ffff irq 23 at device 4.0 on pci0 pci4: <acpi pci="" bus=""> on pcib4 pci0: <base peripheral,="" iommu=""> at device 15.0 (no driver attached) igb0: <intel(r) 1000="" pro="" network="" connection,="" version="" -="" 2.5.3-k=""> port 0x1000-0x101f mem 0xdff60000-0xdff7ffff,0xdffe0000-0xdffe3fff irq 18 at device 20.0 on pci0 igb0: Using MSIX interrupts with 3 vectors igb0: Ethernet address: 00:08:a2:0a:ff:54 igb0: Bound queue 0 to cpu 0 igb0: Bound queue 1 to cpu 1 igb0: netmap queues/slots: TX 2/1024, RX 2/1024 igb1: <intel(r) 1000="" pro="" network="" connection,="" version="" -="" 2.5.3-k=""> port 0x1020-0x103f mem 0xdff80000-0xdff9ffff,0xdffe4000-0xdffe7fff irq 19 at device 20.1 on pci0 igb1: Using MSIX interrupts with 3 vectors igb1: Ethernet address: 00:08:a2:0a:ff:55 igb1: Bound queue 0 to cpu 0 igb1: Bound queue 1 to cpu 1 igb1: netmap queues/slots: TX 2/1024, RX 2/1024 igb2: <intel(r) 1000="" pro="" network="" connection,="" version="" -="" 2.5.3-k=""> port 0x1040-0x105f mem 0xdffa0000-0xdffbffff,0xdffe8000-0xdffebfff irq 20 at device 20.2 on pci0 igb2: Using MSIX interrupts with 3 vectors igb2: Setup of Shared code failed device_attach: igb2 attach returned 6 igb2: <intel(r) 1000="" pro="" network="" connection,="" version="" -="" 2.5.3-k=""> port 0x1060-0x107f mem 0xdffc0000-0xdffdffff,0xdffec000-0xdffeffff irq 21 at device 20.3 on pci0 igb2: Using MSIX interrupts with 3 vectors igb2: Setup of Shared code failed device_attach: igb2 attach returned 6 ehci0: <intel avoton="" usb="" 2.0="" controller=""> mem 0xdfff1400-0xdfff17ff irq 22 at device 22.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 ahci0: <intel avoton="" ahci="" sata="" controller=""> port 0x10c0-0x10c7,0x10e0-0x10e3,0x10c8-0x10cf,0x10e4-0x10e7,0x1080-0x109f mem 0xdfff0000-0xdfff07ff irq 23 at device 23.0 on pci0 ahci0: AHCI v1.30 with 4 3Gbps ports, Port Multiplier not supported ahcich0: <ahci channel=""> at channel 0 on ahci0 ahcich1: <ahci channel=""> at channel 1 on ahci0 ahcich2: <ahci channel=""> at channel 2 on ahci0 ahcich3: <ahci channel=""> at channel 3 on ahci0 ahci1: <intel avoton="" ahci="" sata="" controller=""> port 0x10d0-0x10d7,0x10e8-0x10eb,0x10d8-0x10df,0x10ec-0x10ef,0x10a0-0x10bf mem 0xdfff0800-0xdfff0fff irq 16 at device 24.0 on pci0 ahci1: AHCI v1.30 with 2 6Gbps ports, Port Multiplier not supported ahcich4: <ahci channel=""> at channel 0 on ahci1 ahcich5: <ahci channel=""> at channel 1 on ahci1 isab0: <pci-isa bridge=""> at device 31.0 on pci0 isa0: <isa bus=""> on isab0 orm0: <isa option="" rom=""> at iomem 0xc0000-0xc0fff on isa0 ppc0: cannot reserve I/O port range uart0: <16550 or compatible> at port 0x3f8-0x3ff irq 4 on isa0 uart1: <16550 or compatible> at port 0x2f8-0x2ff irq 3 flags 0x10 on isa0 uart1: console (115200,n,8,1) est0: <enhanced speedstep="" frequency="" control=""> on cpu0 est1: <enhanced speedstep="" frequency="" control=""> on cpu1 Timecounters tick every 1.000 msec random: unblocking device. usbus0: 480Mbps High Speed USB v2.0 ugen0.1: <intel> at usbus0 uhub0: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr=""> on usbus0 uhub0: 8 ports with 8 removable, self powered ugen0.2: <vendor 0x8087=""> at usbus0 uhub1: <vendor 2="" 9="" 0x8087="" product="" 0x07db,="" class="" 0,="" rev="" 2.00="" 0.02,="" addr=""> on usbus0 uhub1: 4 ports with 4 removable, self powered ugen0.3: <huawei technologies="" co.,="" ltd.=""> at usbus0 u3g0: <huawei mobile="" connect="" -="" modem=""> on usbus0 u3g0: Found 5 ports. ugen0.4: <generic> at usbus0 umass0: <generic 0="" 4="" ultra="" fast="" media,="" class="" 0,="" rev="" 2.00="" 1.98,="" addr=""> on usbus0 da0 at umass-sim0 bus 0 scbus6 target 0 lun 0 da0: <generic ultra="" hs-combo="" 1.98=""> Removable Direct Access SCSI device da0: Serial Number 000000225001 da0: 40.000MB/s transfers da0: 3648MB (7471104 512 byte sectors) da0: quirks=0x2 <no_6_byte>SMP: AP CPU #1 Launched! Timecounter "TSC" frequency 1750043505 Hz quality 1000 Trying to mount root from ufs:/dev/ufsid/5862bd7ea7d60710 [rw]... WARNING: / was not properly dismounted WARNING: /: mount pending error: blocks 120 files 4 WARNING: /: TRIM flag on fs but disk does not support TRIM Configuring crash dumps... Using /dev/label/swap0 for dump device. ** SU+J Recovering /dev/ufsid/5862bd7ea7d60710 ** Reading 21495808 byte journal from inode 4. ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 80476 name not found Stopping boot is recommended because filesystem manual action is needed, nevertheless automated repair of the filesystem will be attempted. WARNING: Trying to recover filesystem from inconsistency... ** /dev/ufsid/5862bd7ea7d60710 USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5862bd7ea7d60710 ** Reading 21495808 byte journal from inode 4. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 80476 name not found ** /dev/ufsid/5862bd7ea7d60710 USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5862bd7ea7d60710 ** Reading 21495808 byte journal from inode 4. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 80476 name not found ** /dev/ufsid/5862bd7ea7d60710 USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5862bd7ea7d60710 ** Reading 21495808 byte journal from inode 4. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 80476 name not found ** /dev/ufsid/5862bd7ea7d60710 USE JOURNAL? yes ** SU+J Recovering /dev/ufsid/5862bd7ea7d60710 ** Reading 21495808 byte journal from inode 4. RECOVER? yes ** Building recovery table. ** Resolving unreferenced inode list. ** Processing journal entries. fsck_ufs: Directory 80476 name not found ___ ___/ f \ / p \___/ Sense \___/ \ \___/ Welcome to pfSense 2.3.2-RELEASE (Patch 1) on the 'pfSense' platform... savecore: reboot after panic: handle_written_inodeblock: live inodedep 0xfffff80021219c00 savecore: unable to write to bounds file: Read-only file system savecore: info.0: Read-only file system savecore: unsaved dumps found but not saved rm: /var/etc/cert.crt: Read-only file system rm: /var/etc/cert.key: Read-only file system rm: /var/etc/dhclient_wan.conf: Read-only file system rm: /var/etc/hosts: Read-only file system rm: /var/etc/l2tp-vpn: Read-only file system rm: /var/etc/mpd.script: Read-only file system rm: /var/etc/mpd_opt1.conf: Read-only file system rm: /var/etc/nameserver_ppp0: Read-only file system rm: /var/etc/nginx-webConfigurator.conf: Read-only file system rm: /var/etc/ntpd.conf: Read-only file system rm: /var/etc/openvpn: Read-only file system rm: /var/etc/openvpn-csc: Read-only file system rm: /var/etc/radvd.conf: Read-only file system rm: /var/etc/relayd.conf: Read-only file system rm: /var/etc/resolv.conf: Read-only file system rm: /var/etc/resolvconf.conf: Read-only file system rm: /var/etc/syslog.conf: Read-only file system rm: /var/etc/xinetd.conf: Read-only file system Creating symlinks...ln: /tmp/tmp: Read-only file system rm: /tmp/config.cache: Read-only file system rm: /tmp/config.lock: Read-only file system rm: /tmp/mnt/cf: Read-only file system rm: /tmp/mnt: Read-only file system rm: /tmp/php_errors.txt: Read-only file system rm: /var/etc/nameserver_ppp0: Read-only file system ...ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.20/mach/CORE 32-bit compatibility ldconfig path: /usr/lib32 done. cap_mkdb: /etc/login.conf.db: Read-only file system pkg: Error accessing the package database /etc/rc: cannot create /tmp/php_errors.txt: Read-only file system [22-Jan-2016 01:53:46] ERROR: failed to open error_log (/var/log/php-fpm.log): Read-only file system (30) [22-Jan-2016 01:53:46] ERROR: failed to post process the configuration [22-Jan-2016 01:53:46] ERROR: FPM initialization failed fcgicli: Could not connect to server(/var/run/php-fpm.socket). Launching the init system...rm: /cf/conf/backup/backup.cache: Read-only file system **Warning**: require_once(pkg-utils.inc): failed to open stream: No such file or directory in **/etc/rc.bootup** on line **56** **Fatal error**: require_once(): Failed opening required 'pkg-utils.inc' (include_path='.:/usr/local/share/pear') in **/etc/rc.bootup** on line **56** Starting CRON... done. fcgicli: Could not connect to server(/var/run/php-fpm.socket). Warning: require_once(config.inc): failed to open stream: No such file or directory in /etc/rc.conf_mount_rw on line 55 Fatal error: require_once(): Failed opening required 'config.inc' (include_path='.:/usr/local/share/pear') in /etc/rc.conf_mount_rw on line 55 pkg: Error accessing the package database Warning: require_once(config.inc): failed to open stream: No such file or directory in /etc/rc.conf_mount_ro on line 55 Fatal error: require_once(): Failed opening required 'config.inc' (include_path='.:/usr/local/share/pear') in /etc/rc.conf_mount_ro on line 55 pfSense (pfSense) 2.3.2-RELEASE (Patch 1) amd64 Fri Sep 30 14:36:56 CDT 2016 Bootup complete rm: /tmp/config.cache: Read-only file system FreeBSD/amd64 (Amnesiac) (ttyu1) login: Jan 22 01:53:48 getty[220]: open /dev/ttyv0: No such file or directory J’ai tenté de redémarrer en single user (option 2 au démarrage), et en ligne de commande j’ai tenté : [code]/sbin/fsck -p /sbin/fsck -y /sbin/reboot [/code] Ce qui n’a rien donné. Auriez-vous une piste ? S’il s’agit d’un bug logiciel, et donc s’il y a des lignes de commandes (lesquelles ?) qui permettrais de débloquer la situation ou alors si c’est matériel avec un problème de stockage (j’ai vu quelques posts là-dessus) ? [/s]</no_6_byte></generic></generic></generic></huawei></huawei></vendor></vendor></intel></intel></enhanced></enhanced></isa></isa></pci-isa></ahci></ahci></intel></ahci></ahci></ahci></ahci></intel></intel></intel(r)></intel(r)></intel(r)></intel(r)></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></acpi></at></at></acpi></acpi></core></software></version></software,></core ></tscadj,smep,erms,nfpusg></lahf,prefetch></syscall,nx,rdtscp,lm></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,est,tm2,ssse3,cx16,xtpr,pdcm,sse4.1,sse4.2,movbe,popcnt,tscdlt,aesni,rdrand></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe> -
Avez vous tenté de vous rapprocher du fournisseur de votre équipement ? Il pourrait y avoir un problème matériel avec la carte flash. Il semble nécessaire de réinstaller Pfsense.
-
Avez vous tenté de vous rapprocher du fournisseur de votre équipement ? Il pourrait y avoir un problème matériel avec la carte flash. Il semble nécessaire de réinstaller Pfsense.
Sur vos conseil, c'est ce que je viens de faire. Cela me rappelle un email tout début février de la part du fournisseur, indiquant que Netgate annonce un composant matériel défectueux sur certains de ces routeurs (sans précision) et que cela peut provoquer le non-redémarrage fatal du routeur dans certains cas. Je me renseigne et vous retient au courant.
-
Bon, a priori une réinstallation du système a suffit.
Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.