Root-Server nach reboot tot

opportunist

opportunist

Registered User
Hallo,

seit heute plagt mich ein Fehler, der sich von mir nicht beheben lässt. Leider bin ich mit meinem Latein mehr oder weniger am Ende. Bisher klappte soweit alles immer ganz passabel, nur nach einem Reboot will der Server nicht mehr hochfahren.

Es handelt sich um einen 1&1 L64 Server. Auf diesem ist Debian 3.1 Sarge 32 bit installiert, und es lief auch sehr stabil - bis zum Reboot. Dieses Problem zeigte sich bereits bei einer vorherigen SuSE und Debian- Installation:
gleich nach dem ersten, selbst durchgeführten Reboot, war der Server tot. Bei 1&1 sagt man mir, es könne sich nur um einen Softwarefehler handeln. Ok, ich halte es für unwahrscheinlich, aber nun b in ich hier.

Ich habe die Hoffnung, dass mich vielleicht jemand bei der Lösung des Problems unterstützen kann.

Starte ich den Server im normalen Modus, so ist er nicht erreichbar (absolut nicht anpingbar). Starte ich das Rescue-System, ist er erreichbar. Das Rescuesystem trägt folgendes in die "/var/log/messages" ein:
Code: 
Jan 16 20:00:12 rescue syslogd 1.4.1#17: restart.
Jan 16 20:00:12 rescue kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
Jan 16 20:00:12 rescue kernel: Cannot find map file.
Jan 16 20:00:12 rescue kernel: No module symbols loaded - kernel modules not enabled. 
Jan 16 20:00:12 rescue kernel: Bootdata ok (command line is console=tty0 console=ttyS0,57600 load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=393216 initrd=linux/rescue64-2.6-sarge.gz pw=$1$VMMRlZqg$OleQaOe/zQZfusFD7iZYI1 tz=Europe/Berlin root=/dev/ram0 rw BOOT_IMAGE=linux/kernel64-2.6 )
Jan 16 20:00:12 rescue kernel: Linux version 2.6.16.27-061220a (root@buildd-amd64) (gcc version 3.3.5 (Debian 1:3.3.5-13)) #1 SMP Wed Dec 20 13:49:41 CET 2006
Jan 16 20:00:12 rescue kernel: BIOS-provided physical RAM map:
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 0000000000000000 - 000000000009f400 (usable)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 000000000009f400 - 00000000000a0000 (reserved)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 00000000000e0000 - 0000000000100000 (reserved)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 0000000000100000 - 000000003dee0000 (usable)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 000000003dee0000 - 000000003deef000 (ACPI data)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 000000003deef000 - 000000003df00000 (ACPI NVS)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 000000003df00000 - 0000000040000000 (reserved)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
Jan 16 20:00:12 rescue kernel:  BIOS-e820: 00000000fff00000 - 0000000100000000 (reserved)
Jan 16 20:00:12 rescue kernel: Scanning NUMA topology in Northbridge 24
Jan 16 20:00:12 rescue kernel: Number of nodes 1
Jan 16 20:00:12 rescue kernel: Node 0 MemBase 0000000000000000 Limit 000000003dee0000
Jan 16 20:00:12 rescue kernel: Using node hash shift of 63
Jan 16 20:00:12 rescue kernel: Bootmem setup node 0 0000000000000000-000000003dee0000
Jan 16 20:00:12 rescue kernel: ACPI: PM-Timer IO Port: 0xf008
Jan 16 20:00:12 rescue kernel: ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Jan 16 20:00:12 rescue kernel: Processor #0 15:15 APIC version 16
Jan 16 20:00:12 rescue kernel: ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
Jan 16 20:00:12 rescue kernel: ACPI: IOAPIC (id[0x01] address[0xfec00000] gsi_base[0])
Jan 16 20:00:12 rescue kernel: IOAPIC[0]: apic_id 1, version 20, address 0xfec00000, GSI 0-23
Jan 16 20:00:12 rescue kernel: ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 high edge)
Jan 16 20:00:12 rescue kernel: Setting APIC routing to flat
Jan 16 20:00:12 rescue kernel: Using ACPI (MADT) for SMP configuration information
Jan 16 20:00:12 rescue kernel: Allocating PCI resources starting at 50000000 (gap: 40000000:bec00000)
Jan 16 20:00:12 rescue kernel: Checking aperture...
Jan 16 20:00:12 rescue kernel: CPU 0: aperture @ f8000000 size 64 MB
Jan 16 20:00:12 rescue kernel: Built 1 zonelists
Jan 16 20:00:12 rescue kernel: Kernel command line: console=tty0 console=ttyS0,57600 load_ramdisk=1 prompt_ramdisk=0 ramdisk_size=393216 initrd=linux/rescue64-2.6-sarge.gz pw=$1$VMMRlZqg$OleQaOe/zQZfusFD7iZYI1 tz=Europe/Berlin root=/dev/ram0 rw BOOT_IMAGE=linux/kernel64-2.6 
Jan 16 20:00:12 rescue kernel: Initializing CPU#0
Jan 16 20:00:12 rescue kernel: PID hash table entries: 4096 (order: 12, 131072 bytes)
Jan 16 20:00:12 rescue kernel: time.c: Using 3.579545 MHz WALL PM GTOD PIT/TSC timer.
Jan 16 20:00:12 rescue kernel: time.c: Detected 2000.116 MHz processor.
Jan 16 20:00:12 rescue kernel: Console: colour VGA+ 80x25
Jan 16 20:00:12 rescue kernel: Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Jan 16 20:00:12 rescue kernel: Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Jan 16 20:00:12 rescue kernel: Memory: 901504k/1014656k available (4259k kernel code, 112764k reserved, 1622k data, 256k init)
Jan 16 20:00:12 rescue kernel: Calibrating delay using timer specific routine.. 4004.57 BogoMIPS (lpj=8009159)
Jan 16 20:00:12 rescue kernel: Mount-cache hash table entries: 256
Jan 16 20:00:12 rescue kernel: CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
Jan 16 20:00:12 rescue kernel: CPU: L2 Cache: 512K (64 bytes/line)
Jan 16 20:00:12 rescue kernel: CPU 0(1) -> Node 0 -> Core 0
Jan 16 20:00:12 rescue kernel: Using local APIC timer interrupts.
Jan 16 20:00:12 rescue kernel: result 12500743
Jan 16 20:00:12 rescue kernel: Detected 12.500 MHz APIC timer.
Jan 16 20:00:12 rescue kernel: Brought up 1 CPUs
Jan 16 20:00:12 rescue kernel: testing NMI watchdog ... OK.
Jan 16 20:00:12 rescue kernel: migration_cost=0
Jan 16 20:00:12 rescue kernel: checking if image is initramfs...it isn't (no cpio magic); looks like an initrd
Jan 16 20:00:12 rescue kernel: Freeing initrd memory: 90519k freed
Jan 16 20:00:12 rescue kernel: DMI present.
Jan 16 20:00:12 rescue kernel: NET: Registered protocol family 16
Jan 16 20:00:12 rescue kernel: ACPI: bus type pci registered
Jan 16 20:00:12 rescue kernel: PCI: Using configuration type 1
Jan 16 20:00:12 rescue kernel: ACPI: Subsystem revision 20060127
Jan 16 20:00:12 rescue kernel: ACPI: Interpreter enabled
Jan 16 20:00:12 rescue kernel: ACPI: Using IOAPIC for interrupt routing
Jan 16 20:00:12 rescue kernel: ACPI: PCI Root Bridge [PCI0] (0000:00)
Jan 16 20:00:12 rescue kernel: PCI: Ignoring BAR0-3 of IDE controller 0000:00:02.5
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKA] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKB] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKC] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKD] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKE] (IRQs 3 4 5 6 7 *9 10 11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKF] (IRQs 3 4 5 6 7 9 10 *11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKG] (IRQs 3 4 5 6 7 9 *10 11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt Link [LNKH] (IRQs 3 4 *5 6 7 9 10 11 12 14 15)
Jan 16 20:00:12 rescue kernel: ACPI: Device [PS2M] status [00000008]: functional but not present; setting present
Jan 16 20:00:12 rescue kernel: ACPI: Device [FDC] status [00000008]: functional but not present; setting present
Jan 16 20:00:12 rescue kernel: ACPI: Device [LPT] status [00000008]: functional but not present; setting present
Jan 16 20:00:12 rescue kernel: ACPI: Device [ECP] status [00000008]: functional but not present; setting present
Jan 16 20:00:12 rescue kernel: Generic PHY: Registered new driver
Jan 16 20:00:12 rescue kernel: SCSI subsystem initialized
Jan 16 20:00:12 rescue kernel: PCI: Using ACPI for IRQ routing
Jan 16 20:00:12 rescue kernel: PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
Jan 16 20:00:12 rescue kernel: PCI-DMA: Disabling IOMMU.
Jan 16 20:00:12 rescue kernel: PCI: Ignore bogus resource 6 [0:0] of 0000:01:00.0
Jan 16 20:00:12 rescue kernel: PCI: Bridge: 0000:00:01.0
Jan 16 20:00:12 rescue kernel:   IO window: 2000-2fff
Jan 16 20:00:12 rescue kernel:   MEM window: fa100000-fa1fffff
Jan 16 20:00:12 rescue kernel:   PREFETCH window: f0000000-f7ffffff
Jan 16 20:00:12 rescue kernel: PCI: Bridge: 0000:00:06.0
Jan 16 20:00:12 rescue kernel:   IO window: disabled.
Jan 16 20:00:12 rescue kernel:   MEM window: disabled.
Jan 16 20:00:12 rescue kernel:   PREFETCH window: disabled.
Jan 16 20:00:12 rescue kernel: PCI: Bridge: 0000:00:1f.0
Jan 16 20:00:12 rescue kernel:   IO window: disabled.
Jan 16 20:00:12 rescue kernel:   MEM window: disabled.
Jan 16 20:00:12 rescue kernel:   PREFETCH window: disabled.
Jan 16 20:00:12 rescue kernel: Simple Boot Flag at 0x69 set to 0x80
Jan 16 20:00:12 rescue kernel: IA-32 Microcode Update Driver: v1.14 <tigran@veritas.com>
Jan 16 20:00:12 rescue kernel: IA32 emulation $Id: sys_ia32.c,v 1.32 2002/03/24 13:02:28 ak Exp $
Jan 16 20:00:12 rescue kernel: VFS: Disk quotas dquot_6.5.1
Jan 16 20:00:12 rescue kernel: Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
Jan 16 20:00:12 rescue kernel: NTFS driver 2.1.26 [Flags: R/W].
Jan 16 20:00:12 rescue kernel: JFS: nTxBlock = 7750, nTxLock = 62001
Jan 16 20:00:12 rescue kernel: SGI XFS with ACLs, large block/inode numbers, no debug enabled
Jan 16 20:00:12 rescue kernel: SGI XFS Quota Management subsystem
Jan 16 20:00:12 rescue kernel: Initializing Cryptographic API
Jan 16 20:00:12 rescue kernel: io scheduler noop registered
Jan 16 20:00:12 rescue kernel: io scheduler anticipatory registered (default)
Jan 16 20:00:12 rescue kernel: io scheduler deadline registered
Jan 16 20:00:12 rescue kernel: io scheduler cfq registered
Jan 16 20:00:12 rescue kernel: 0000:00:03.3 EHCI: BIOS handoff failed (BIOS bug ?) 01010001
Jan 16 20:00:12 rescue kernel: pcie_portdrv_probe->Dev[000a:1039] has invalid IRQ. Check vendor BIOS
Jan 16 20:00:12 rescue kernel: assign_interrupt_mode Found MSI capability
Jan 16 20:00:12 rescue kernel: pcie_portdrv_probe->Dev[0004:1039] has invalid IRQ. Check vendor BIOS
Jan 16 20:00:12 rescue kernel: assign_interrupt_mode Found MSI capability
Jan 16 20:00:12 rescue kernel: Real Time Clock Driver v1.12ac
Jan 16 20:00:12 rescue kernel: Non-volatile memory driver v1.2
Jan 16 20:00:12 rescue kernel: WDT driver for Acquire single board computer initialising.
Jan 16 20:00:12 rescue kernel: WDT driver for Advantech single board computer initialising.
Jan 16 20:00:12 rescue kernel: Advantech WDT: initialized. timeout=60 sec (nowayout=0)
Jan 16 20:00:12 rescue kernel: alim7101_wdt: Steve Hill <steve@navaho.co.uk>.
Jan 16 20:00:12 rescue kernel: alim7101_wdt: ALi M7101 PMU not present - WDT not set
Jan 16 20:00:12 rescue kernel: ib700wdt: WDT driver for IB700 single board computer initialising.
Jan 16 20:00:12 rescue kernel: WDT driver for Wafer 5823 single board computer initialising.
Jan 16 20:00:12 rescue kernel: sc1200wdt: build 20020303<3>sc1200wdt: io parameter must be specified
Jan 16 20:00:12 rescue kernel: WDT driver for the Winbond(TM) W83627HF Super I/O chip initialising.
Jan 16 20:00:12 rescue kernel: w83627hf WDT: Watchdog already running. Resetting timeout to 60 sec
Jan 16 20:00:12 rescue kernel: W83977F WDT: W83977F WDT driver, v1.00
Jan 16 20:00:12 rescue kernel: machzwd: MachZ ZF-Logic Watchdog driver initializing.
Jan 16 20:00:12 rescue kernel: 0xffff
Jan 16 20:00:12 rescue kernel: machzwd: Watchdog using action = RESET
Jan 16 20:00:12 rescue kernel: Linux agpgart interface v0.101 (c) Dave Jones
Jan 16 20:00:12 rescue kernel: Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Jan 16 20:00:12 rescue kernel: Hangcheck: Using monotonic_clock().
Jan 16 20:00:12 rescue kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Jan 16 20:00:12 rescue kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Jan 16 20:00:12 rescue kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
Jan 16 20:00:12 rescue kernel: serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
Jan 16 20:00:12 rescue kernel: isa bounce pool size: 16 pages
Jan 16 20:00:12 rescue kernel: floppy0: no floppy controllers found
Jan 16 20:00:12 rescue kernel: RAMDISK driver initialized: 16 RAM disks of 393216K size 1024 blocksize
Jan 16 20:00:12 rescue kernel: loop: loaded (max 8 devices)
Jan 16 20:00:12 rescue kernel: Intel(R) PRO/1000 Network Driver - version 6.3.9-k4-NAPI
Jan 16 20:00:12 rescue kernel: Copyright (c) 1999-2005 Intel Corporation.
Jan 16 20:00:12 rescue kernel: e100: Intel(R) PRO/100 Network Driver, 3.5.10-k2-NAPI
Jan 16 20:00:12 rescue kernel: e100: Copyright(c) 1999-2005 Intel Corporation
Jan 16 20:00:12 rescue kernel: Marvell 88E1101: Registered new driver
Jan 16 20:00:12 rescue kernel: Davicom DM9161E: Registered new driver
Jan 16 20:00:12 rescue kernel: Davicom DM9131: Registered new driver
Jan 16 20:00:12 rescue kernel: Cicada Cis8204: Registered new driver
Jan 16 20:00:12 rescue kernel: LXT970: Registered new driver
Jan 16 20:00:12 rescue kernel: LXT971: Registered new driver
Jan 16 20:00:12 rescue kernel: QS6612: Registered new driver
Jan 16 20:00:12 rescue kernel: forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.49.
Jan 16 20:00:12 rescue kernel: tun: Universal TUN/TAP device driver, 1.6
Jan 16 20:00:12 rescue kernel: tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Jan 16 20:00:12 rescue kernel: r8169 Gigabit Ethernet driver 2.2LK-NAPI loaded
Jan 16 20:00:12 rescue kernel: GSI 16 sharing vector 0xC1 and IRQ 16
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 19 (level, low) -> IRQ 193
Jan 16 20:00:12 rescue kernel: eth0: RTL8169 at 0xffffc2000058e000, 00:30:05:b8:25:51, IRQ 193
Jan 16 20:00:12 rescue kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
Jan 16 20:00:12 rescue kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
Jan 16 20:00:12 rescue kernel: ide-floppy driver 0.99.newide
Jan 16 20:00:12 rescue kernel: Adaptec aacraid driver (1.1-4 Dec 20 2006 13:49:31)
Jan 16 20:00:12 rescue kernel: 3ware Storage Controller device driver for Linux v1.26.02.001.
Jan 16 20:00:12 rescue kernel: 3ware 9000 Storage Controller device driver for Linux v2.26.02.007.
Jan 16 20:00:12 rescue kernel: sata_sis 0000:00:05.0: version 0.5
Jan 16 20:00:12 rescue kernel: GSI 17 sharing vector 0xC9 and IRQ 17
Jan 16 20:00:12 rescue kernel: ACPI: PCI Interrupt 0000:00:05.0[A] -> GSI 17 (level, low) -> IRQ 201
Jan 16 20:00:12 rescue kernel: sata_sis 0000:00:05.0: Detected SiS 182 chipset
Jan 16 20:00:12 rescue kernel: ata1: SATA max UDMA/133 cmd 0x1CB0 ctl 0x1CA6 bmdma 0x1C90 irq 201
Jan 16 20:00:12 rescue kernel: ata2: SATA max UDMA/133 cmd 0x1CA8 ctl 0x1CA2 bmdma 0x1C98 irq 201
Jan 16 20:00:12 rescue kernel: ata1: SATA link up 1.5 Gbps (SStatus 113)
Jan 16 20:00:12 rescue kernel: ata1: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48
Jan 16 20:00:12 rescue kernel: ata1: dev 0 configured for UDMA/133
Jan 16 20:00:12 rescue kernel: scsi0 : sata_sis
Jan 16 20:00:12 rescue kernel: ata2: SATA link up 1.5 Gbps (SStatus 113)
Jan 16 20:00:12 rescue kernel: ata2: dev 0 ATA-6, max UDMA/133, 156301488 sectors: LBA48
Jan 16 20:00:12 rescue kernel: ata2: dev 0 configured for UDMA/133
Jan 16 20:00:12 rescue kernel: scsi1 : sata_sis
Jan 16 20:00:12 rescue kernel:   Vendor: ATA       Model: ST380817AS        Rev: 3.42
Jan 16 20:00:12 rescue kernel:   Type:   Direct-Access                      ANSI SCSI revision: 05
Jan 16 20:00:12 rescue kernel:   Vendor: ATA       Model: ST380817AS        Rev: 3.42
Jan 16 20:00:12 rescue kernel:   Type:   Direct-Access                      ANSI SCSI revision: 05
Jan 16 20:00:12 rescue kernel: SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Jan 16 20:00:12 rescue kernel: sda: Write Protect is off
Jan 16 20:00:12 rescue kernel: SCSI device sda: drive cache: write back
Jan 16 20:00:12 rescue kernel: SCSI device sda: 156301488 512-byte hdwr sectors (80026 MB)
Jan 16 20:00:12 rescue kernel: sda: Write Protect is off
Jan 16 20:00:12 rescue kernel: SCSI device sda: drive cache: write back
Jan 16 20:00:12 rescue kernel:  sda: sda1 sda2 sda4 < sda5 sda6 sda7 >
Jan 16 20:00:12 rescue kernel: sd 0:0:0:0: Attached scsi disk sda
Jan 16 20:00:12 rescue kernel: SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
Jan 16 20:00:12 rescue kernel: sdb: Write Protect is off
Jan 16 20:00:12 rescue kernel: SCSI device sdb: drive cache: write back
Jan 16 20:00:12 rescue kernel: SCSI device sdb: 156301488 512-byte hdwr sectors (80026 MB)
Jan 16 20:00:12 rescue kernel: sdb: Write Protect is off
Jan 16 20:00:12 rescue kernel: SCSI device sdb: drive cache: write back
Jan 16 20:00:12 rescue kernel:  sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 sdb7 >
Jan 16 20:00:12 rescue kernel: sd 1:0:0:0: Attached scsi disk sdb
Jan 16 20:00:12 rescue kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
Jan 16 20:00:12 rescue kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
Jan 16 20:00:12 rescue kernel: mice: PS/2 mouse device common for all mice
Jan 16 20:00:12 rescue kernel: i2c /dev entries driver
Jan 16 20:00:12 rescue kernel: i2c-sis96x version 1.0.0
Jan 16 20:00:12 rescue kernel: hdaps: supported laptop not found!
Jan 16 20:00:12 rescue kernel: hdaps: driver init failed (ret=-6)!
Jan 16 20:00:12 rescue kernel: md: linear personality registered for level -1
Jan 16 20:00:12 rescue kernel: md: raid0 personality registered for level 0
Jan 16 20:00:12 rescue kernel: md: raid1 personality registered for level 1
Jan 16 20:00:12 rescue kernel: md: raid10 personality registered for level 10
Jan 16 20:00:12 rescue kernel: md: faulty personality registered for level -5
Jan 16 20:00:12 rescue kernel: md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
Jan 16 20:00:12 rescue kernel: md: bitmap version 4.39
Jan 16 20:00:12 rescue kernel: device-mapper: 4.5.0-ioctl (2005-10-04) initialised: [EMAIL="dm-devel@redhat.com"]dm-devel@redhat.com[/EMAIL]
Jan 16 20:00:12 rescue kernel: NET: Registered protocol family 2
Jan 16 20:00:12 rescue kernel: IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
Jan 16 20:00:12 rescue kernel: TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
Jan 16 20:00:12 rescue kernel: TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
Jan 16 20:00:12 rescue kernel: TCP: Hash tables configured (established 131072 bind 65536)
Jan 16 20:00:12 rescue kernel: TCP reno registered
Jan 16 20:00:12 rescue kernel: ip_conntrack version 2.4 (3963 buckets, 31704 max) - 264 bytes per conntrack
Jan 16 20:00:12 rescue kernel: ip_conntrack_pptp version 3.1 loaded
Jan 16 20:00:12 rescue kernel: TCP bic registered
Jan 16 20:00:12 rescue kernel: NET: Registered protocol family 1
Jan 16 20:00:12 rescue kernel: NET: Registered protocol family 17
Jan 16 20:00:12 rescue kernel: NET: Registered protocol family 15
Jan 16 20:00:12 rescue kernel: powernow-k8: Found 1 AMD Athlon 64 / Opteron processors (version 1.60.0)
Jan 16 20:00:12 rescue kernel: powernow-k8:    0 : fid 0xc (2000 MHz), vid 0x6 (1400 mV)
Jan 16 20:00:12 rescue kernel: powernow-k8:    1 : fid 0xa (1800 MHz), vid 0x8 (1350 mV)
Jan 16 20:00:12 rescue kernel: powernow-k8:    2 : fid 0x2 (1000 MHz), vid 0x12 (1100 mV)
Jan 16 20:00:12 rescue kernel: cpu_init done, current fid 0xc, vid 0x6
Jan 16 20:00:12 rescue kernel: md: Autodetecting RAID arrays.
Jan 16 20:00:12 rescue kernel: md: autorun ...
Jan 16 20:00:12 rescue kernel: md: considering sdb7 ...
Jan 16 20:00:12 rescue kernel: md:  adding sdb7 ...
Jan 16 20:00:12 rescue kernel: md: sdb6 has different UUID to sdb7
Jan 16 20:00:12 rescue kernel: md: sdb5 has different UUID to sdb7
Jan 16 20:00:12 rescue kernel: md: sdb1 has different UUID to sdb7
Jan 16 20:00:12 rescue kernel: md:  adding sda7 ...
Jan 16 20:00:12 rescue kernel: md: sda6 has different UUID to sdb7
Jan 16 20:00:12 rescue kernel: md: sda5 has different UUID to sdb7
Jan 16 20:00:12 rescue kernel: md: sda1 has different UUID to sdb7
Jan 16 20:00:12 rescue kernel: md: created md7
Jan 16 20:00:12 rescue kernel: md: bind<sda7>
Jan 16 20:00:12 rescue kernel: md: bind<sdb7>
Jan 16 20:00:12 rescue kernel: md: running: <sdb7><sda7>
Jan 16 20:00:12 rescue kernel: raid1: raid set md7 active with 2 out of 2 mirrors
Jan 16 20:00:12 rescue kernel: md: considering sdb6 ...
Jan 16 20:00:12 rescue kernel: md:  adding sdb6 ...
Jan 16 20:00:12 rescue kernel: md: sdb5 has different UUID to sdb6
Jan 16 20:00:12 rescue kernel: md: sdb1 has different UUID to sdb6
Jan 16 20:00:12 rescue kernel: md:  adding sda6 ...
Jan 16 20:00:12 rescue kernel: md: sda5 has different UUID to sdb6
Jan 16 20:00:12 rescue kernel: md: sda1 has different UUID to sdb6
Jan 16 20:00:12 rescue kernel: md: created md6
Jan 16 20:00:12 rescue kernel: md: bind<sda6>
Jan 16 20:00:12 rescue kernel: md: bind<sdb6>
Jan 16 20:00:12 rescue kernel: md: running: <sdb6><sda6>
Jan 16 20:00:12 rescue kernel: raid1: raid set md6 active with 2 out of 2 mirrors
Jan 16 20:00:12 rescue kernel: md: considering sdb5 ...
Jan 16 20:00:12 rescue kernel: md:  adding sdb5 ...
Jan 16 20:00:12 rescue kernel: md: sdb1 has different UUID to sdb5
Jan 16 20:00:12 rescue kernel: md:  adding sda5 ...
Jan 16 20:00:12 rescue kernel: md: sda1 has different UUID to sdb5
Jan 16 20:00:12 rescue kernel: md: created md5
Jan 16 20:00:12 rescue kernel: md: bind<sda5>
Jan 16 20:00:12 rescue kernel: md: bind<sdb5>
Jan 16 20:00:12 rescue kernel: md: running: <sdb5><sda5>
Jan 16 20:00:12 rescue kernel: raid1: raid set md5 active with 2 out of 2 mirrors
Jan 16 20:00:12 rescue kernel: md: considering sdb1 ...
Jan 16 20:00:12 rescue kernel: md:  adding sdb1 ...
Jan 16 20:00:12 rescue kernel: md:  adding sda1 ...
Jan 16 20:00:12 rescue kernel: md: created md1
Jan 16 20:00:12 rescue kernel: md: bind<sda1>
Jan 16 20:00:12 rescue kernel: md: bind<sdb1>
Jan 16 20:00:12 rescue kernel: md: running: <sdb1><sda1>
Jan 16 20:00:12 rescue kernel: raid1: raid set md1 active with 2 out of 2 mirrors
Jan 16 20:00:12 rescue kernel: md: ... autorun DONE.
Jan 16 20:00:12 rescue kernel: RAMDISK: Compressed image found at block 0
Jan 16 20:00:12 rescue kernel: VFS: Mounted root (ext2 filesystem).
Jan 16 20:00:12 rescue kernel: Freeing unused kernel memory: 256k freed
Jan 16 20:00:12 rescue kernel: r8169: eth0: link up
Ich kann dort soweit nichts erkennen, was darauf schließen lässt, weshalb der Server nerreichbar ist. Schreibe ich auf der Konsole allerdings ein "fdisk -l" aus, gibt er mir dies aus:

Code: 
Disk /dev/sda: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               1         123      987966   fd  Linux raid autodetect
/dev/sda2             124         367     1959930   82  Linux swap / Solaris
/dev/sda4             368        9729    75200265    5  Extended
/dev/sda5             368         976     4891761   fd  Linux raid autodetect
/dev/sda6             977        1585     4891761   fd  Linux raid autodetect
/dev/sda7            1586        9729    65416648+  fd  Linux raid autodetect

Disk /dev/sdb: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/track, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               1         123      987966   fd  Linux raid autodetect
/dev/sdb2             124         367     1959930   82  Linux swap / Solaris
/dev/sdb4             368        9729    75200265    5  Extended
/dev/sdb5             368         976     4891761   fd  Linux raid autodetect
/dev/sdb6             977        1585     4891761   fd  Linux raid autodetect
/dev/sdb7            1586        9729    65416648+  fd  Linux raid autodetect

Disk /dev/md7: 66.9 GB, 66986573824 bytes
2 heads, 4 sectors/track, 16354144 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md7 doesn't contain a valid partition table

Disk /dev/md6: 5009 MB, 5009047552 bytes
2 heads, 4 sectors/track, 1222912 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md6 doesn't contain a valid partition table

Disk /dev/md5: 5009 MB, 5009047552 bytes
2 heads, 4 sectors/track, 1222912 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md5 doesn't contain a valid partition table

Disk /dev/md1: 1011 MB, 1011548160 bytes
2 heads, 4 sectors/track, 246960 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

Disk /dev/md1 doesn't contain a valid partition table
Die Meldungen alá "doesnt contain a valid partition table" machen micht etwas stutzig. Kann mir dazu evtl. jemand etwas sagen?

Ich hoffe sehr, dass mir jemand weiterhelfen kann.
Vielen Dank schonmal und liebe Grüße
 
Last edited by a moderator:
Hallo,

bei 1und1 hat man doch eine Serielle Konsole.
Schau dir diese Ausgaben doch mal an ;)
 
HiHo!

Zum ersten solltest Du die Quote tags durch Code tags erstetzen, sonst liest hier bald kaum einer auch nur den zweiten post in dem thread.

Dann solltest Du die Quellen Deines Providers bezueglich Natur und Handhabung des Rescuesystems studieren, das kann schonmal 10-30 Minuten brauchen aber es lohnt sich; Die listings die Du da beigebracht hast sind ganz offensichtlich aus der aktuell laufenden Instanz des Rescuesystem, nicht von dem installierten System und daher nicht sonderlich sachdienlich.

Darueber hinaus moechte ich auch dringend raten, mithilfe der bereits erwaehnten seriellen Konsole das Problem massiv einzugrenzen; Zwischen "System tot" und "System aus dem Internet nicht erreichbar" liegen Ozeane, wenn nicht sogar Welten.

Und dann noch der Hinweis, dass 1&1 so etwas Ominoeses bietet wie eine "1&1 Firewall", will nichts heissen aber klingt im Hinblick auf die Erreichbarkeit aus dem Internet verdaechtig.

Ciao,
Mercy.
 
Hallo,

bei 1und1 hat man doch eine Serielle Konsole.
Schau dir diese Ausgaben doch mal an
Click to expand...
Die Serielle Konsole ist nicht verfügbar, was ich sehr lustig finde. Die Serielle Konsole stürzt ab, sobald man sich versucht im normalen Bootmodus einzuloggen, oder im normalen Bootmodus neuzustarten.

Darueber hinaus moechte ich auch dringend raten, mithilfe der bereits erwaehnten seriellen Konsole das Problem massiv einzugrenzen; Zwischen "System tot" und "System aus dem Internet nicht erreichbar" liegen Ozeane, wenn nicht sogar Welten.
Click to expand...
Es sieht schon aus, als wäre das System tot. Es ist nicht möglich auf irgendeine Weise zuzugreifen. Mittlerweile habe ich erfahren, dass dieses problem wohl schon jemand in ähnlicher Weise war, dort war das Board anscheinend schuld, bzw. ein Controler. Leider ist der 1&1-Support bisher nicht einsichtig und möchte die Schuld auf mich und die Software schieben. Das kann ich jedoch ausschließen, da das selbe Problem auch auf einem frischen Image - egal ob Debian, SuSE oder >Fedora - auftritt. Ich werde nun also weiter mit dem Support sprechen, und einfach mal eine andere Platte auflegen. Es kann ja nicht angehen, dass ich Tage lange Ausfälle hinnehme und nichts unternommen wird, weil man meint ich wäre schuld.

Vielen Dank für eure Antworten,
Oliver

Nachtrag:
Die 1&1-Firewall habe ich als erstes deaktiviert, um dies als Fehlerquelle auszuschließen.
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top