Server Bootproblem

FreeBSD, Gentoo, openSUSE, CentOS, Ubuntu, Debian
3-ranger
Posts: 64
Joined: 2004-03-23 16:17

Server Bootproblem

Post by 3-ranger » 2004-09-26 11:21

Hi,

habe bei S4Y einen Root-Server auf dem, dank CC's Script, Debian 3.1/Sarge installiert ist.
Seit gestern bleibt der Server nach einem "init6" oder "shutdown -r now" einfach hängen, ohne Fehlermeldung. Nur ein Reset /Reboot von S4Y aus, bringt den Server wieder hoch. Aus den Logs kann ich leider nichts ersehen, ausser einem Zeitloch. Dieses entsteht auf das Warten des Reboots von S4Y.

Was mir nur auffällt, bisher hat er immer so rebootet

Code: Select all

Sep 25 14:38:46 denver070 shutdown[15933]: shutting down for system reboot
Sep 25 14:38:52 denver070 exiting on signal 15
Sep 25 14:39:51 denver070 syslogd 1.4.1#15: restart.


Das ist mein Befehl zum rebooten. Um 00:35:13 tut sich nichts mehr
Kann es an einer Biosmeldung oder ähnlichem liegen? Hardwarefehler?

Code: Select all

Sep 26 00:26:08 denver070 -- MARK --
Sep 26 00:35:10 denver070 shutdown[8467]: shutting down for system reboot
Sep 26 00:35:13 denver070 kernel: Kernel logging (proc) stopped.
Sep 26 00:35:13 denver070 kernel: Kernel log daemon terminating.
Sep 26 00:35:13 denver070 exiting on signal 15
um 1:19:51 wird ein Reset von S4Y durchgeführt.

Code: Select all

Sep 26 01:19:51 denver070 syslogd 1.4.1#15: restart.
Sep 26 01:19:51 denver070 kernel: klogd 1.4.1#15, log source = /proc/kmsg started.
Sep 26 01:19:52 denver070 kernel: Inspecting /boot/System.map-2.6.7
Sep 26 01:19:52 denver070 kernel: Loaded 24426 symbols from /boot/System.map-2.6.7.
Sep 26 01:19:52 denver070 kernel: Symbols match kernel version 2.6.7.
Sep 26 01:19:52 denver070 kernel: No module symbols loaded - kernel modules not enabled. 
Sep 26 01:19:52 denver070 kernel: Linux version 2.6.7 (root@denver070.server4you.de) (gcc version 3.3.4 (Debian 1:3.3.4-6sarge1)) #1 Sun Sep 26 00:31:23 CEST 2004
Sep 26 01:19:52 denver070 kernel: BIOS-provided physical RAM map:
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 0000000000100000 - 000000003eff0000 (usable)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 000000003eff0000 - 000000003eff3000 (ACPI NVS)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 000000003eff3000 - 000000003f000000 (ACPI data)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 00000000fec00000 - 00000000fec01000 (reserved)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Sep 26 01:19:52 denver070 kernel:  BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
Sep 26 01:19:52 denver070 kernel: Warning only 896MB will be used.
Sep 26 01:19:52 denver070 kernel: Use a HIGHMEM enabled kernel.
Sep 26 01:19:52 denver070 kernel: 896MB LOWMEM available.
Sep 26 01:19:52 denver070 kernel: found SMP MP-table at 000f6550
Sep 26 01:19:52 denver070 kernel: On node 0 totalpages: 229376
Sep 26 01:19:52 denver070 kernel:   DMA zone: 4096 pages, LIFO batch:1
Sep 26 01:19:52 denver070 kernel:   Normal zone: 225280 pages, LIFO batch:16
Sep 26 01:19:52 denver070 kernel:   HighMem zone: 0 pages, LIFO batch:1
Sep 26 01:19:52 denver070 kernel: DMI 2.3 present.
Sep 26 01:19:52 denver070 kernel: ACPI: RSDP (v000 KM400                                     ) @ 0x000f7f50
Sep 26 01:19:52 denver070 kernel: ACPI: RSDT (v001 KM400  AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3eff3000
Sep 26 01:19:52 denver070 kernel: ACPI: FADT (v001 KM400  AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3eff3040
Sep 26 01:19:52 denver070 kernel: ACPI: MADT (v001 KM400  AWRDACPI 0x42302e31 AWRD 0x00000000) @ 0x3eff7580
Sep 26 01:19:52 denver070 kernel: ACPI: DSDT (v001 KM400  AWRDACPI 0x00001000 MSFT 0x0100000e) @ 0x00000000
Sep 26 01:19:52 denver070 kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Sep 26 01:19:52 denver070 kernel: Processor #0 6:10 APIC version 16
Sep 26 01:19:52 denver070 kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Sep 26 01:19:52 denver070 kernel: Using ACPI for processor (LAPIC) configuration information
Sep 26 01:19:52 denver070 kernel: Intel MultiProcessor Specification v1.4
Sep 26 01:19:52 denver070 kernel:     Virtual Wire compatibility mode.
Sep 26 01:19:52 denver070 kernel: OEM ID: OEM00000 Product ID: PROD00000000 APIC at: 0xFEE00000
Sep 26 01:19:52 denver070 kernel: I/O APIC #2 Version 17 at 0xFEC00000.
Sep 26 01:19:52 denver070 kernel: Enabling APIC mode:  Flat.  Using 1 I/O APICs
Sep 26 01:19:52 denver070 kernel: Processors: 1
Sep 26 01:19:52 denver070 kernel: Built 1 zonelists
Sep 26 01:19:52 denver070 kernel: Kernel command line: auto BOOT_IMAGE=2.6.7 ro root=303
Sep 26 01:19:52 denver070 kernel: Initializing CPU#0
Sep 26 01:19:52 denver070 kernel: PID hash table entries: 4096 (order 12: 32768 bytes)
Sep 26 01:19:52 denver070 kernel: Detected 2081.836 MHz processor.
Sep 26 01:19:52 denver070 kernel: Using tsc for high-res timesource
Sep 26 01:19:52 denver070 kernel: Console: colour VGA+ 80x25
Sep 26 01:19:52 denver070 kernel: Memory: 907116k/917504k available (1430k kernel code, 9644k reserved, 401k data, 328k init, 0k highmem)
Sep 26 01:19:52 denver070 kernel: Checking if this processor honours the WP bit even in supervisor mode... Ok.
Sep 26 01:19:52 denver070 kernel: Calibrating delay loop... 4141.87 BogoMIPS
Sep 26 01:19:52 denver070 kernel: Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Sep 26 01:19:52 denver070 kernel: Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Sep 26 01:19:52 denver070 kernel: Mount-cache hash table entries: 512 (order: 0, 4096 bytes)
Sep 26 01:19:52 denver070 kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Sep 26 01:19:52 denver070 kernel: CPU: L2 Cache: 512K (64 bytes/line)
Sep 26 01:19:52 denver070 kernel: Intel machine check architecture supported.
Sep 26 01:19:52 denver070 kernel: Intel machine check reporting enabled on CPU#0.
Sep 26 01:19:52 denver070 kernel: CPU: AMD Athlon(tm) XP 2800+ stepping 00
Sep 26 01:19:52 denver070 kernel: Enabling fast FPU save and restore... done.
Sep 26 01:19:52 denver070 kernel: Enabling unmasked SIMD FPU exception support... done.
Sep 26 01:19:52 denver070 kernel: Checking 'hlt' instruction... OK.
Sep 26 01:19:52 denver070 kernel: enabled ExtINT on CPU#0
Sep 26 01:19:52 denver070 kernel: ESR value before enabling vector: 00000000
Sep 26 01:19:52 denver070 kernel: ESR value after enabling vector: 00000000
Sep 26 01:19:52 denver070 kernel: Using local APIC timer interrupts.
Sep 26 01:19:52 denver070 kernel: calibrating APIC timer ...
Sep 26 01:19:52 denver070 kernel: ..... CPU clock speed is 2081.2999 MHz.
Sep 26 01:19:52 denver070 kernel: ..... host bus clock speed is 333.0280 MHz.
Sep 26 01:19:52 denver070 kernel: NET: Registered protocol family 16
Sep 26 01:19:52 denver070 kernel: PCI: PCI BIOS revision 2.10 entry at 0xfbcc0, last bus=1
Sep 26 01:19:52 denver070 kernel: PCI: Using configuration type 1
Sep 26 01:19:52 denver070 kernel: PCI: Probing PCI hardware
Sep 26 01:19:52 denver070 kernel: PCI: Probing PCI hardware (bus 00)
Sep 26 01:19:52 denver070 kernel: PCI: Using IRQ router VIA [1106/3177] at 0000:00:11.0
Sep 26 01:19:52 denver070 kernel: spurious 8259A interrupt: IRQ7.
Sep 26 01:19:52 denver070 kernel: VFS: Disk quotas dquot_6.5.1
Sep 26 01:19:52 denver070 kernel: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
Sep 26 01:19:52 denver070 kernel: Initializing Cryptographic API
Sep 26 01:19:52 denver070 kernel: Real Time Clock Driver v1.12
Sep 26 01:19:52 denver070 kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Sep 26 01:19:52 denver070 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Sep 26 01:19:52 denver070 kernel: VP_IDE: IDE controller at PCI slot 0000:00:11.1
Sep 26 01:19:52 denver070 kernel: VP_IDE: chipset revision 6
Sep 26 01:19:52 denver070 kernel: VP_IDE: not 100%% native mode: will probe irqs later
Sep 26 01:19:52 denver070 kernel: VP_IDE: VIA vt8235 (rev 00) IDE UDMA133 controller on pci0000:00:11.1
Sep 26 01:19:52 denver070 kernel:     ide0: BM-DMA at 0xdc00-0xdc07, BIOS settings: hda:DMA, hdb:pio
Sep 26 01:19:52 denver070 kernel:     ide1: BM-DMA at 0xdc08-0xdc0f, BIOS settings: hdc:pio, hdd:pio
Sep 26 01:19:52 denver070 kernel: hda: SAMSUNG SP1203N, ATA DISK drive
Sep 26 01:19:52 denver070 kernel: Using anticipatory io scheduler
Sep 26 01:19:52 denver070 kernel: ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Sep 26 01:19:52 denver070 kernel: hda: max request size: 1024KiB
Sep 26 01:19:52 denver070 kernel: hda: 234493056 sectors (120060 MB) w/2048KiB Cache, CHS=16383/255/63, UDMA(100)
Sep 26 01:19:52 denver070 kernel:  hda: hda1 hda2 hda3 hda4 < hda5 hda6 hda7 hda8 >
Sep 26 01:19:52 denver070 kernel: mice: PS/2 mouse device common for all mice
Sep 26 01:19:52 denver070 kernel: Failed to disable AUX port, but continuing anyway... Is this a SiS?
Sep 26 01:19:52 denver070 kernel: If AUX port is really absent please use the 'i8042.noaux' option.
Sep 26 01:19:52 denver070 kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Sep 26 01:19:52 denver070 kernel: NET: Registered protocol family 2
Sep 26 01:19:52 denver070 kernel: IP: routing cache hash table of 8192 buckets, 64Kbytes
Sep 26 01:19:52 denver070 kernel: TCP: Hash tables configured (established 262144 bind 65536)
Sep 26 01:19:52 denver070 kernel: NET: Registered protocol family 1
Sep 26 01:19:52 denver070 kernel: NET: Registered protocol family 10
Sep 26 01:19:52 denver070 kernel: IPv6 over IPv4 tunneling driver
Sep 26 01:19:52 denver070 kernel: NET: Registered protocol family 17
Sep 26 01:19:52 denver070 kernel: kjournald starting.  Commit interval 5 seconds
Sep 26 01:19:52 denver070 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep 26 01:19:52 denver070 kernel: VFS: Mounted root (ext3 filesystem) readonly.
Sep 26 01:19:52 denver070 kernel: Freeing unused kernel memory: 328k freed
Sep 26 01:19:52 denver070 kernel: Adding 1028152k swap on /dev/hda2.  Priority:-1 extents:1
Sep 26 01:19:52 denver070 kernel: EXT3 FS on hda3, internal journal
Sep 26 01:19:52 denver070 kernel: via-rhine.c:v1.10-LK1.1.20-2.6 May-23-2004 Written by Donald Becker
Sep 26 01:19:52 denver070 kernel: PCI: Found IRQ 11 for device 0000:00:12.0
Sep 26 01:19:52 denver070 kernel: PCI: Sharing IRQ 11 with 0000:00:10.0
Sep 26 01:19:52 denver070 kernel: eth0: VIA VT6102 Rhine-II at 0xe000, 00:0c:76:e9:e6:dc, IRQ 11.
Sep 26 01:19:52 denver070 kernel: eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 41e1.
Sep 26 01:19:52 denver070 kernel: kjournald starting.  Commit interval 5 seconds
Sep 26 01:19:52 denver070 kernel: EXT3 FS on hda1, internal journal
Sep 26 01:19:52 denver070 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep 26 01:19:52 denver070 kernel: kjournald starting.  Commit interval 5 seconds
Sep 26 01:19:52 denver070 kernel: EXT3 FS on hda5, internal journal
Sep 26 01:19:52 denver070 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep 26 01:19:52 denver070 kernel: kjournald starting.  Commit interval 5 seconds
Sep 26 01:19:52 denver070 kernel: EXT3 FS on hda6, internal journal
Sep 26 01:19:52 denver070 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep 26 01:19:52 denver070 kernel: kjournald starting.  Commit interval 5 seconds
Sep 26 01:19:52 denver070 kernel: EXT3 FS on hda7, internal journal
Sep 26 01:19:52 denver070 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep 26 01:19:52 denver070 kernel: kjournald starting.  Commit interval 5 seconds
Sep 26 01:19:52 denver070 kernel: EXT3 FS on hda8, internal journal
Sep 26 01:19:52 denver070 kernel: EXT3-fs: mounted filesystem with ordered data mode.
Sep 26 01:19:52 denver070 kernel: eth0: Setting full-duplex based on MII #1 link partner capability of 41e1.

captaincrunch
Userprojekt
Userprojekt
Posts: 7225
Joined: 2002-10-09 14:30
Location: Dorsten

Re: Server Bootproblem

Post by captaincrunch » 2004-09-26 11:46

Seit gestern bleibt der Server nach einem "init6" oder "shutdown -r now" einfach hängen, ohne Fehlermeldung
Und? Wie oft rebootet man schon einen halbwegs vernünftig gepflegten Unix-Server?

<glaskugel>
komische / falsche Kernelkonfiguration
</glaskugel>
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc

3-ranger
Posts: 64
Joined: 2004-03-23 16:17

Re: Server Bootproblem

Post by 3-ranger » 2004-09-26 12:36

hi,

vielen dank für deine Antwort :wink:

Es ist "deine" Kernel Config :lol: , habe bisher nie Probleme damit gehabt. 2.6.8.1 und andere liefen bisher einwandfrei damit.
auch wenn ich zu einem bisher gut laufendem Kernel switche, bleibt dieser Boothänger :roll: ... Es ist nur seit gestern Mittag so!

Nehme dann doch stark an, daß es zu einem Fehler nach dem Runterfahren kommt oder beim hochfahren. Werde dann den Support von S4Y anschreiben, ansonsten lasse ich das Kernelcompilieren!

Aso, wieso ich ein vernünftiges Unix-System booten muss? Weil ich aus reinem Hobby einige Gameserver betreibe und ein wenig bei den 2.6er/2.4er Kernels am probieren bin, wie sie sich unter Last verhalten.

Latenzzeiten, CPU-Last etc...

danke :)

captaincrunch
Userprojekt
Userprojekt
Posts: 7225
Joined: 2002-10-09 14:30
Location: Dorsten

Re: Server Bootproblem

Post by captaincrunch » 2004-09-26 14:07

Es ist "deine" Kernel Config
Aber nicht im Falle eines 2.6er-Kernels. ;)
DebianHowTo
echo "[q]sa[ln0=aln256%Pln256/snlbx]sb729901041524823122snlbxq"|dc

3-ranger
Posts: 64
Joined: 2004-03-23 16:17

Re: Server Bootproblem

Post by 3-ranger » 2004-09-26 14:26

Hi,

nicht zu 100%, aber deine benutze ich für ein Oldconfig. Den Rest zu 90% mit Enter bestätigen. :)