thomasreischer
Goto Top

PFSense Appliance SG-4860 1U startet nicht mehr nach ordnungsgemäßem Shutdown

Hallo,

ich habe heute die SG-4860 1U erhalten. Die Einrichtung ging ohne Probleme - ich bin nach Anleitung vorgegangen. Am Ende der Konfiguration wollte ich die Pfsense neustarten.
Ich habe also über das Webinterface einen System Halt durchgeführt - das ging auch alles ohne Probleme, die Appliance ging nach ein paar SEkunden aus.

Ich habe rein gar nichts verändert und wollte die PfSense nun manuell wieder hochfahren- mit dem Start Button auf der Rückseite. Nur leider tut sich jetzt gar nichts mehr. Weder leuchten die Ports noch ist das Webinterface zu erreichen. Den Voleatech Support habe ich schon kontaktiert - ist das hier schon mal jemandem passiert? Wird vermutlich ein Hardware Fehler sein..

Grüße

Content-Key: 295791

Url: https://administrator.de/contentid/295791

Ausgedruckt am: 29.03.2024 um 11:03 Uhr

Mitglied: 119944
119944 10.02.2016 um 17:42:35 Uhr
Goto Top
Moin,

klingt für mich auch sehr stark nach einem Hardware Fehler.
Hast du das System mal eine Weile vom Strom abgetrennt und es dann nochmal versucht?

Würde mich echt mal interessieren wie voleatech damit umgeht, halt uns bitte auf dem laufenden.

VG
Val
Mitglied: thomasreischer
thomasreischer 10.02.2016 um 17:51:19 Uhr
Goto Top
Mach ich..

Hast du eigentich irgendeine spezielle Beziehung zu PfSense? Unter so ziemlich jedem PfSense bezogenen Beitrag findet man dich :P
Mitglied: thomasreischer
thomasreischer 10.02.2016 um 17:55:51 Uhr
Goto Top
Der Mitarbeiter vom Voleatech Support hat uns nun ebenfalls empfohlen das Gerät für ein paar Minuten vom Strom zu trennen..
Das werden wir dann morgen versuchen.
Mitglied: aqui
aqui 10.02.2016 um 19:21:14 Uhr
Goto Top
Hat das gerät einen serielle Schnittstelle ??
Unbedingt anschliessen und die Bootmessages kontrollieren !!!
Siehe hier:
Preiswerte, VPN fähige Firewall im Eigenbau oder als Fertiggerät
und auch hier:
WLAN oder LAN Gastnetz einrichten mit einem Captive Portal (Hotspot Funktion)
Mitglied: thomasreischer
thomasreischer 11.02.2016 um 07:37:31 Uhr
Goto Top
Also mittlerweile läuft die PfSense wieder - wir haben sie ca 10 min vom Strom getrennt..

In den Logs kann ich nichts erkennen. Wenn du Zeit und Lust hast kannst du gerne einen Blick darauf werfen..

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2016.02.11 07:34:31 =~=~=~=~=~=~=~=~=~=~=~=
À
Google, Inc.
Serial Graphics Adapter 01/27/15
SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (wenwang@localhost.localdomain) Tue Jan 27 18:10:24 UTC 2015
Term: 80x24
O4 0

SeaBIOS (version SageBIOS-20160122_083040-localhost.localdomain)


iPXE (http://ipxe.org) 00:14.0 C100 PCI2.10 PnP PMM+7FB7AF80+7FADAF80 C100


Press Ctrl-B to configure iPXE (PCI 00:14.0)...


iPXE (http://ipxe.org) 00:14.1 C200 PCI2.10 PnP PMM 7FB7AF80 7FADAF80 C200


iPXE (http://ipxe.org) 00:14.2 C300 PCI2.10 PnP PMM 7FB7AF80 7FADAF80 C300


iPXE (http://ipxe.org) 00:14.3 C400 PCI2.10 PnP PMM 7FB7AF80 7FADAF80 C400


Press F12 for boot menu.


F1 pfSense


F5 Drive 1


F6 PXE


Boot: F1


-
\
|
/
-
\
|
/
-
\
|-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-    ______  / \  _____/ f \  / \ /  / p \______/ Sense  \ / \  \_____/ \  \ /  \______/    __ ____  _ __ / _/ ___| ___ _ __ ___ ___  | '_ \| |_\___ \ / _ \ '_ \/ __|/ _ \  | |_) | _|___) | __/ | | \__ \ __/  | .__/|_| |____/ \___|_| |_|___/\___|  |_|  ||||||||||||||||||||||||----------------------------------------------------------------------------------++++\|/-\|/-\|/-\|Welcome to pfSense1 .Boot Multi User [Enter]2 .Boot [S]ingle User3 .[Esc]ape to loader prompt4 .RebootOptions:5 .[K]ernel: kernel (1 of 2)6 .Configure Boot [O]ptions...Autoboot in 2 seconds. [Space] to pauseAutoboot in 1 seconds. [Space] to pause /-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\/boot/kernel/kernel text=0x1223e30 |/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|data=0x881b00+0x3576a0 /-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-\|/-syms=[0x8+0x16f050\|/-\|/-\|/-\+0x8+0x16c491|/-\|/-\|/-]
Booting...
\|/-\|/KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2014 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.1-RELEASE-p25 c39b63e(releng/10.1)-dirty: Mon Dec 21 15:20:02 CST 2015
root@factory22-amd64-builder.pfmechanics.com:/usr/obj.RELENG_2_2.amd64/usr/pfSensesrc/src.RELENG_2_2/sys/pfSense_SMP.10 amd64
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
CPU: Intel(R) Atom(TM) CPU C2558 @ 2.40GHz (2400.06-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>
VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID
TSC: P-state invariant, performance statistics
real memory = 10737418240 (10240 MB)
avail memory = 8235651072 (7854 MB)
Event timer "LAPIC" quality 600
ACPI APIC Table: <CORE COREBOOT>
FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs
FreeBSD/SMP: 1 package(s) x 4 core(s)
cpu0 (BSP): APIC ID: 0
cpu1 (AP): APIC ID: 2
cpu2 (AP): APIC ID: 4
cpu3 (AP): APIC ID: 6
random device not loaded; using insecure entropy
ioapic0 <Version 2.0> irqs 0-23 on motherboard
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, 0xffffffff806345e0, 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, 0xffffffff80634690, 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, 0xffffffff80634740, 0) error 1
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, 0xffffffff8060ce10, 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, 0xffffffff8060cec0, 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, 0xffffffff8060cf70, 0) error 1
random: <Software, Yarrow> initialized
module_register_init: MOD_LOAD (vesa, 0xffffffff80fc4290, 0) error 19
kbd0 at kbdmux0
cryptosoft0: <software crypto> on motherboard
padlock0: No ACE support.
acpi0: <CORE COREBOOT> on motherboard
acpi0: Power Button (fixed)
hpet0: <High Precision Event Timer> iomem 0xfed03000-0xfed033ff on acpi0
hpet0: invalid period
device_attach: hpet0 attach returned 6
cpu0: <ACPI CPU> on acpi0
cpu1: <ACPI CPU> on acpi0
cpu2: <ACPI CPU> on acpi0
cpu3: <ACPI CPU> on acpi0
hpet0: <High Precision Event Timer> iomem 0xfed03000-0xfed033ff 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 0xdfe00000-0xdfe1ffff irq 16 at device 1.0 on pci0
pci1: <ACPI PCI bus> on pcib1
pcib2: <ACPI PCI-PCI bridge> mem 0xdfe20000-0xdfe3ffff irq 19 at device 2.0 on pci0
pci2: <ACPI PCI bus> on pcib2
pcib3: <ACPI PCI-PCI bridge> mem 0xdfe40000-0xdfe5ffff irq 20 at device 3.0 on pci0
pci3: <ACPI PCI bus> on pcib3
igb0: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x1000-0x101f mem 0xdfc00000-0xdfc1ffff,0xdfc20000-0xdfc23fff irq 18 at device 0.0 on pci3
igb0: Using MSIX interrupts with 3 vectors
igb0: Ethernet address: 00:08:a2:09:a7:f9
igb0: Bound queue 0 to cpu 0
igb0: Bound queue 1 to cpu 1
pcib4: <ACPI PCI-PCI bridge> mem 0xdfe60000-0xdfe7ffff irq 23 at device 4.0 on pci0
pci4: <ACPI PCI bus> on pcib4
igb1: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x2000-0x201f mem 0xdfd00000-0xdfd1ffff,0xdfd20000-0xdfd23fff irq 19 at device 0.0 on pci4
igb1: Using MSIX interrupts with 3 vectors
igb1: Ethernet address: 00:08:a2:09:a7:fa
igb1: Bound queue 0 to cpu 2
igb1: Bound queue 1 to cpu 3
pci0: <processor> at device 11.0 (no driver attached)
pci0: <base peripheral, IOMMU> at device 15.0 (no driver attached)
igb2: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x3000-0x301f mem 0xdfea0000-0xdfebffff,0xdff24000-0xdff27fff irq 18 at device 20.0 on pci0
igb2: Using MSIX interrupts with 5 vectors
igb2: Ethernet address: 00:08:a2:09:a7:f5
igb2: Bound queue 0 to cpu 0
igb2: Bound queue 1 to cpu 1
igb2: Bound queue 2 to cpu 2
igb2: Bound queue 3 to cpu 3
igb3: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x3020-0x303f mem 0xdfec0000-0xdfedffff,0xdff28000-0xdff2bfff irq 19 at device 20.1 on pci0
igb3: Using MSIX interrupts with 5 vectors
igb3: Ethernet address: 00:08:a2:09:a7:f6
igb3: Bound queue 0 to cpu 0
igb3: Bound queue 1 to cpu 1
igb3: Bound queue 2 to cpu 2
igb3: Bound queue 3 to cpu 3
igb4: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x3040-0x305f mem 0xdfee0000-0xdfefffff,0xdff2c000-0xdff2ffff irq 20 at device 20.2 on pci0
igb4: Using MSIX interrupts with 5 vectors
igb4: Ethernet address: 00:08:a2:09:a7:f7
igb4: Bound queue 0 to cpu 0
igb4: Bound queue 1 to cpu 1
igb4: Bound queue 2 to cpu 2
igb4: Bound queue 3 to cpu 3
igb5: <Intel(R) PRO/1000 Network Connection version - 2.4.0> port 0x3060-0x307f mem 0xdff00000-0xdff1ffff,0xdff30000-0xdff33fff irq 21 at device 20.3 on pci0
igb5: Using MSIX interrupts with 5 vectors
igb5: Ethernet address: 00:08:a2:09:a7:f8
igb5: Bound queue 0 to cpu 0
igb5: Bound queue 1 to cpu 1
igb5: Bound queue 2 to cpu 2
igb5: Bound queue 3 to cpu 3
ehci0: <Intel Avoton USB 2.0 controller> mem 0xdff35400-0xdff357ff irq 22 at device 22.0 on pci0
usbus0: EHCI version 1.0
usbus0 on ehci0
ahci0: <Intel Avoton AHCI SATA controller> port 0x30c0-0x30c7,0x30e0-0x30e3,0x30c8-0x30cf,0x30e4-0x30e7,0x3080-0x309f mem 0xdff34000-0xdff347ff 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 0x30d0-0x30d7,0x30e8-0x30eb,0x30d8-0x30df,0x30ec-0x30ef,0x30a0-0x30bf mem 0xdff34800-0xdff34fff 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
p4tcc0: <CPU Frequency Thermal Control> on cpu0
est1: <Enhanced SpeedStep Frequency Control> on cpu1
p4tcc1: <CPU Frequency Thermal Control> on cpu1
est2: <Enhanced SpeedStep Frequency Control> on cpu2
p4tcc2: <CPU Frequency Thermal Control> on cpu2
est3: <Enhanced SpeedStep Frequency Control> on cpu3
p4tcc3: <CPU Frequency Thermal Control> on cpu3
Timecounters tick every 1.000 msec
IPsec: Initialized Security Association Processing.
random: unblocking device.
usbus0: 480Mbps High Speed USB v2.0
ugen0.1: <Intel> at usbus0
uhub0: <Intel EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
uhub0: 8 ports with 8 removable, self powered
ugen0.2: <vendor 0x8087> at usbus0
uhub1: <vendor 0x8087 product 0x07db, class 9/0, rev 2.00/0.02, addr 2> on usbus0
uhub1: 4 ports with 4 removable, self powered
ugen0.3: <Generic> at usbus0
umass0: <Generic Ultra Fast Media, class 0/0, rev 2.00/1.98, addr 3> on usbus0
da0 at umass-sim0 bus 0 scbus6 target 0 lun 0
da0: <Generic Ultra HS-COMBO 1.98> Removable Direct Access SCSI-0 device
da0: Serial Number 000000225001
da0: 40.000MB/s transfers
da0: 3648MB (7471104 512 byte sectors: 255H 63S/T 465C)
da0: quirks=0x2<NO_6_BYTE>
ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
ada0: <INTEL SSDMCEAC030B3 LLLi> ATA-9 SATA 3.x device
ada0: Serial Number CVLI5263016N030H
ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
ada0: Command Queueing enabled
ada0: 28626MB (58626288 512 byte sectors: 16H 63S/T 16383C)
ada0: Previously was known as ad4
SMP: AP CPU #2 Launched!
SMP: AP CPU #1 Launched!
SMP: AP CPU #3 Launched!
Timecounter "TSC-low" frequency 1200029952 Hz quality 1000
Trying to mount root from ufs:/dev/ufsid/56b9d7754cfce8e3 [rw]...
Configuring crash dumps...
Using /dev/label/swap0 for dump device.
/dev/ufsid/56b9d7754cfce8e3: FILE SYSTEM CLEAN; SKIPPING CHECKS
/dev/ufsid/56b9d7754cfce8e3: clean, 4970862 free (430 frags, 621304 blocks, 0.0% fragmentation)
Filesystems are clean, continuing...
Mounting filesystems...
Disabling APM on /dev/ad4

___
___/ f \
/ p \___/ Sense
\___/ \
\___/

Welcome to pfSense 2.2.6-RELEASE ...

No core dumps found.
Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib
32-bit compatibility ldconfig path: /usr/lib32
done.
External config loader 1.0 is now starting...
Launching the init system... done.
Initializing...................... done.
Starting device manager (devd)...done.
Loading configuration......done.
Updating configuration...done.
Cleaning backup cache............................done.
Setting up extended sysctls...done.
padlock0: No ACE support.
aesni0: <AES-CBC,AES-XTS,AES-GCM> on motherboard
Setting timezone...done.
Configuring loopback interface...done.
Starting syslog...done.
Starting Secure Shell Services...done.
Setting up polling defaults...done.
Setting up interfaces microcode...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...done.
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting DNS Resolver...done.
Starting NTP time client...done.
Configuring firewall......done.
Generating RRD graphs...done.
Starting syslog...done.
Starting CRON... done.
pfSense (pfSense) 2.2.6-RELEASE amd64 Mon Dec 21 15:23:01 CST 2015
Bootup complete


FreeBSD/amd64 (pfSense.aichach.local) (ttyu1)


* Welcome to pfSense 2.2.6-RELEASE-pfSense (amd64) on pfSense *

WAN (wan) -> pppoe0 ->
LAN (lan) -> igb0 -> v4: 192.168.1.50/24
OPT1 (opt1) -> igb2 ->
OPT2 (opt2) -> igb3 ->
OPT3 (opt3) -> igb4 ->
OPT4 (opt4) -> igb5 ->
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) pfSense Developer Shell
4) Reset to factory defaults 13) Upgrade 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) Shell


Enter an option:
Mitglied: 119944
119944 11.02.2016 aktualisiert um 08:41:50 Uhr
Goto Top
Zitat von @thomasreischer:
Hast du eigentich irgendeine spezielle Beziehung zu PfSense? Unter so ziemlich jedem PfSense bezogenen Beitrag findet man dich :P
Nö ich mag es nur ganz gern face-wink

Du sollst natürlich im Log von PfSense schauen und nicht den Bootprozess hier rein posten.

Was passiert wenn du das Gerät nochmal genauso ausschaltest? Würde ich nochmal ordentlich durch testen bevor ich das System produktiv nehme...
Aber häng dich dabei per Console an das Gerät und schau was es dabei macht und ob eine Fehlermeldung auftaucht.

VG
Val