1&1 Root Server Bootet nicht mehr

Serverdienste ohne eigene Kategorie
quax
Posts: 27
Joined: 2008-11-27 22:48
 

1&1 Root Server Bootet nicht mehr

Post by quax »

Hallo,

hab heute meinen Root Server von 1&1 per yast aktualisiert, leider hat er auch ein kernel update durchgeführt, und nun bootet er nicht mehr. ich hab nun schon einiges versucht den alten kernel wieder zum booten zu bewegen, aber leider fehlt mir dann doch irgendwas!?

nun ja ich hoffe auf eure hilfe!

zunächst hab ich mit hilfe des rescue systems und serial console zugriff auf den server.

ich kann die platten wieder mounten

mount /dev/md1 /mnt
mount /dev/md6 /mnt/var
mount /dev/md5 /mnt/usr
mount /dev/md7 /mnt/home
mount /dev/md8 /mnt/srv

chroot /mnt

danach auf /boot
ls- la

Code: Select all

drwxr-xr-x  4 root root    4096 Nov 27 16:19 .
drwxr-xr-x 22 root root    4096 Nov 27 10:49 ..
-rw-r--r--  1 root root  954312 Nov  6 20:10 System.map-2.6.18.8-0.13-default
-rw-r--r--  1 root root 1290771 Nov  8  2007 System.map-2.6.20.21-071108a
-rw-r--r--  1 root root 1357530 Mar  3  2008 System.map-2.6.23.17-20080303a
-rw-------  1 root root     512 Sep 19  2007 backup_mbr
lrwxrwxrwx  1 root root       1 Apr  1  2008 boot -> .
-rw-r--r--  1 root root     512 Apr  1  2008 boot.0800
-rw-r--r--  1 root root     512 Apr  1  2008 boot.0810
-rw-r--r--  1 root root   64134 Nov  6 20:13 config-2.6.18.8-0.13-default
-rw-r--r--  1 root root   34910 Nov  8  2007 config-2.6.20.21-071108a
-rw-r--r--  1 root root   35586 Mar  3  2008 config-2.6.23.17-20080303a
drwxr-xr-x  2 root root    4096 Nov 27 16:36 grub
lrwxrwxrwx  1 root root      24 Nov 27 16:19 initrd -> initrd-2.6.20.21-071108a
-rw-r--r--  1 root root 3180441 Nov 27 16:19 initrd-2.6.18.8-0.13-default
-rw-r--r--  1 root root 2544530 Nov 27 16:19 initrd-2.6.20.21-071108a
-rw-r--r--  1 root root 2544560 Nov 27 16:19 initrd-2.6.23.17-20080303a
drwx------  2 root root   49152 Apr  1  2008 lost+found
-rw-------  1 root root  147968 Nov 27 11:15 map
-rw-------  1 root root  379904 Sep 19  2007 message
-rw-r--r--  1 root root  121087 Nov  6 20:14 symsets-2.6.18.8-0.13-default.tar.gz
-rw-r--r--  1 root root  338752 Nov  6 20:14 symtypes-2.6.18.8-0.13-default.gz
-rw-r--r--  1 root root   99327 Nov  6 20:13 symvers-2.6.18.8-0.13-default.gz
-rwxr-xr-x  1 root root 2114694 Nov  6 20:12 vmlinux-2.6.18.8-0.13-default.gz
lrwxrwxrwx  1 root root      25 Nov 27 14:58 vmlinuz -> vmlinuz-2.6.20.21-071108a
-rw-r--r--  1 root root 1618576 Nov  6 20:10 vmlinuz-2.6.18.8-0.13-default
-rw-r--r--  1 root root 2875376 Nov  8  2007 vmlinuz-2.6.20.21-071108a
-rw-r--r--  1 root root 2687480 Mar  3  2008 vmlinuz-2.6.23.17-20080303a
lrwxrwxrwx  1 root root      25 Apr  1  2008 vmlinuz.old -> vmlinuz-2.6.20.21-071108a
bootloader ist Grub

die datei /boot/grub/menu.ist schaut so aus "und verweist auf die falsche kernel Version"

Code: Select all

# Modified by YaST2. Last modification on Tue Sep 18 10:23:59 UTC 2007
default 0
timeout 8

##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
    root (hd0,6)
    kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda7 resume=/dev/sda2 splash=silent showopts console=tty1 console=ttyS0,57000
    initrd /boot/initrd-2.6.18.2-34-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.2
    root (hd0,6)
    kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda7 showopts ide=nodma apm=off acpi=off noresume edd=off 3
    initrd /boot/initrd-2.6.18.2-34-default
mein versuch folgende änderungen zu machen haben nix gebracht

Code: Select all

# Modified by YaST2. Last modification on Tue Sep 18 10:23:59 UTC 2007
default 0
timeout 8

##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
    root (hd0,6)
    kernel /boot/vmlinuz-2.6.20.21-071108a root=/dev/sda7 resume=/dev/sda2 spll
ash=silent showopts console=tty1 console=ttyS0,57000
    initrd /boot/initrd-2.6.20.21-071108a

###Don't change this comment - YaST2 identifier: Original name: linux###
#title openSUSE 10.2
#    root (hd0,6)
#    kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda7 resume=/dev/sda2 splash=silent showopts console=tty1 console=ttyS0,57000
#    initrd /boot/initrd-2.6.18.2-34-default

###Don't change this comment - YaST2 identifier: Original name: failsafe###
title Failsafe -- openSUSE 10.2
    root (hd0,6)
    kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/sda7 showopts ide=nodma apm=off acpi=off noresume edd=off 3
    initrd /boot/initrd-2.6.18.2-34-default
den symlink auf die die richitge vmlinuz version hab ich geändert

von

lrwxrwxrwx 1 root root 25 Nov 27 14:58 vmlinuz -> vmlinuz-2.6.18.8-0.13-default

nach

lrwxrwxrwx 1 root root 25 Nov 27 14:58 vmlinuz -> vmlinuz-2.6.20.21-071108a

ich komm einfach nciht mehr weiter, evtl. seh ich vor lauter bäumen den wald nimmer, bin aber auch noch nicht so tief in der materie drinne, bemühe mich aber weiter rein zu kommen. was ich noch dazu sagen kann, es sind hier nicht alle kernels lauffähig, 1&1 bietet hier selber kernel zum downlaod an, und ja es war keine absicht, den kernel mit zu aktualisieren, dass sollte nicht passieren, ich dachte ich hätte ihn ausgeklammert!?

hoffe es kann mir jemand helfen
Last edited by quax on 2008-11-28 08:24, edited 1 time in total.
Top
Roger Wilco
Posts: 5923
Joined: 2004-05-23 12:53
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Roger Wilco »

Benutze das nächste mal den CODE-Tag um deine Beiträge übersichtlicher zu gestalten.
quax wrote:bootloader ist Grub
Sicher? Früher[tm] wurde LILO als Bootloader genutzt und GRUB war ggf. einfach zusätzlich installiert. Schau mal auf deiner Festplatte, ob eine /etc/lilo.conf existiert. Falls ja, musst du den MBR durch LILO durch einfachen Aufruf von `lilo` neu schreiben lassen.
Ob die Maßnahmen erfolgreich waren, kannst du anhand der seriellen Konsole deines Servers prüfen.

Benutze auch die hervorragende Suchfunktion dieses Forums. Dann findest du zahlreiche ähnliche (um nicht zu sagen identische) Beiträge anderer Benutzer zu dem Thema...
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

danke, werd mir das mit dem code zu herzen nehmen!

ok, hab mit find -iname "lilo.conf" folgenden eintrag gefunden

Code: Select all

./lilo.conf
der inhalt sieht so aus:

Code: Select all

# Modified by YaST2. Last modification on Thu Nov 27 11:49:00 EST 2008
root = /dev/md1
install = /boot/boot.b
vga = normal
timeout = 60
prompt
lba32
read-only
default = lx
serial = 0,57600n8
append = "console=ttyS0,57600 console=tty0"


image = /boot/vmlinuz-2.6.18.8-0.13-default
###Don't change this comment - YaST2 identifier: Original name: linux###
    label = Linux
    append = " console=tty0 console=ttyS0,57600 panic=30"
    initrd = /boot/initrd-2.6.18.8-0.13-default
    root = /dev/md1


image = /boot/vmlinuz-2.6.18.8-0.13-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
demnach bootet lilo also den falschen kernel und nicht grup ^^

muss ich nun wirklich nur lilo neu aufrufen? vorausgesetzt ich hab den symlink auf die alte vmlinuz gesetzt, denke ich mal?

ich frage bewust zuerst nochmal nach!
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

sorry, hatte vergessen:

hab lilo ausgeführt

Code: Select all

rescue:/boot# lilo
Warning: RAID1 install implied by omitted 'boot='
Warning: '/proc/partitions' does not exist, disk scan bypassed
Added Linux
Added Failsafe
Added lxser
Added lx *

geändert hat er die lilo.conf aber nicht!

/etc/lilo.conf

Code: Select all

# Modified by YaST2. Last modification on Thu Nov 27 11:49:00 EST 2008
root = /dev/md1
install = /boot/boot.b
vga = normal
timeout = 60
prompt
lba32
read-only
default = lx
serial = 0,57600n8
append = "console=ttyS0,57600 console=tty0"


image = /boot/vmlinuz-2.6.18.8-0.13-default
###Don't change this comment - YaST2 identifier: Original name: linux###
    label = Linux
    append = " console=tty0 console=ttyS0,57600 panic=30"
    initrd = /boot/initrd-2.6.18.8-0.13-default
    root = /dev/md1


image = /boot/vmlinuz-2.6.18.8-0.13-default
###Don't change this comment - YaST2 identifier: Original name: failsafe###
kann ich diese den manuel anpassen?
Top
wgot
Posts: 1675
Joined: 2003-07-06 02:03
 

Re: 1&1 Root Server Bootet nicht mehr

Post by wgot »

Hallo,

der Aufruf von lilo ändert die lilo.conf nicht (sondern den Bootsektor). lilo.conf muss von Hand korrigiert werden oder die alte wieder eingespielt. Schau mal nach, ob im gleichen Verzeichnis eine lilo.conf.yastsaved (oder ähnlich) liegt, das ist die alte.

Hast Du die ganze lilo.conf im Forum gezeigt, sieht unvollständig aus.

Gruß, Wolfgang
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

hallo,

oh hattest recht, der editor hatte ein teil ausgeblendet, hier nochmals die ganze

Code: Select all

# Modified by YaST2. Last modification on Fri Nov 28 02:53:16 EST 2008
root = /dev/md1
install = /boot/boot.b
vga = normal
timeout = 60
prompt
lba32
read-only
default = Linux
serial = 0,57600n8
append = "console=ttyS0,57600 console=tty0"
boot = /dev/md1

image = /boot/vmlinuz-2.6.20.21-071108a
###Don't change this comment - YaST2 identifier: Original name: linux###
    label = Linux
    append = " console=tty0 console=ttyS0,57600 panic=30"
    initrd = /boot/initrd-2.6.20.21-071108a
    root = /dev/md1

image = /boot/vmlinuz-2.6.20.21-071108a
###Don't change this comment - YaST2 identifier: Original name: failsafe###
    label = Failsafe
    append = "showopts ide=nodma apm=off acpi=off noresume edd=off 3"
    initrd = /boot/initrd-2.6.20.21-071108a
    root = /dev/md1

image = /boot/vmlinuz
    label = lxser
    append = " console=tty0 console=ttyS0,57600 panic=30"

image = /boot/vmlinuz
    label = lx
leider kommt ich so nicht weiter, auch die sufu hilft mir da nicht wirklich, hab ja doch schon einiges versucht, aber mir fehlt wohl irgend was dazwischen ](*,)
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

ok, mann will ja nicht untätig sein, hab wieder mal ein wenig gestöbert und noch was ausprobiert, ich hab in yast den bootloader zunächst auf grup gestellt und dann wieder auf lilo und ihn denke neu aktviert!?

danach hat er jedenfalls die lilo.conf neu geschrieben und neu gebootet, aber nun hat er wohl ein platten prob mit dem raid???

hier mal der bootscreen

Code: Select all

LILO 22.7 boot:
Loading Linux........................................................................................................
BIOS data check successful
Linux version 2.6.20.21-071108a (root@buildd-amd64) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 SMP Thu Nov 8 13:04:34 CET 2007
Command line: BOOT_IMAGE=Linux ro root=901 console=tty0 console=ttyS0,57600 panic=30
BIOS-provided physical RAM map:
 BIOS-e820: 0000000000000000 - 000000000009e000 (usable)
 BIOS-e820: 000000000009e000 - 00000000000a0000 (reserved)
 BIOS-e820: 00000000000d0000 - 0000000000100000 (reserved)
 BIOS-e820: 0000000000100000 - 000000003df10000 (usable)
 BIOS-e820: 000000003df10000 - 000000003df16000 (ACPI data)
 BIOS-e820: 000000003df16000 - 000000003df80000 (ACPI NVS)
 BIOS-e820: 000000003df80000 - 0000000040000000 (reserved)
 BIOS-e820: 00000000fc000000 - 00000000fe000000 (reserved)
 BIOS-e820: 00000000fec00000 - 00000000fec10000 (reserved)
 BIOS-e820: 00000000fee00000 - 00000000fee01000 (reserved)
 BIOS-e820: 00000000fff80000 - 0000000100000000 (reserved)
end_pfn_map = 1048576
DMI present.
Scanning NUMA topology in Northbridge 24
Number of nodes 1
Node 0 MemBase 0000000000000000 Limit 000000003df10000
Using node hash shift of 63
Bootmem setup node 0 0000000000000000-000000003df10000
Zone PFN ranges:
  DMA             0 ->     4096
  DMA32        4096 ->  1048576
  Normal    1048576 ->  1048576
early_node_map[2] active PFN ranges
    0:        0 ->      158
    0:      256 ->   253712
Nvidia board detected. Ignoring ACPI timer override.
If you got timer trouble try acpi_use_timer_override
ACPI: PM-Timer IO Port: 0x1008
ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled)
Processor #0 (Bootup-CPU)
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled)
Processor #1
ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: IOAPIC (id[0x02] address[0xfec00000] gsi_base[0])
IOAPIC[0]: apic_id 2, address 0xfec00000, GSI 0-23
Setting APIC routing to flat
Using ACPI (MADT) for SMP configuration information
Nosave address range: 000000000009e000 - 00000000000a0000
Nosave address range: 00000000000a0000 - 00000000000d0000
Nosave address range: 00000000000d0000 - 0000000000100000
Allocating PCI resources starting at 50000000 (gap: 40000000:bc000000)
PERCPU: Allocating 33728 bytes of per cpu data
Built 1 zonelists.  Total pages: 247837
Kernel command line: BOOT_IMAGE=Linux ro root=901 console=tty0 console=ttyS0,57600 panic=30
Initializing CPU#0
PID hash table entries: 4096 (order: 12, 32768 bytes)
Console: colour VGA+ 80x25
Dentry cache hash table entries: 131072 (order: 8, 1048576 bytes)
Inode-cache hash table entries: 65536 (order: 7, 524288 bytes)
Checking aperture...
CPU 0: aperture @ 238c000000 size 32 MB
Aperture too small (32 MB)
No AGP bridge found
Memory: 989652k/1014848k available (4127k kernel code, 24804k reserved, 1635k data, 380k init)
Calibrating delay using timer specific routine.. 4223.00 BogoMIPS (lpj=8446017)
Mount-cache hash table entries: 256
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 0/0 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 0
Freeing SMP alternatives: 36k freed
ACPI: Core revision 20060707
Using local APIC timer interrupts.
result 12557501
Detected 12.557 MHz APIC timer.
Booting processor 1/2 APIC 0x1
Initializing CPU#1
Calibrating delay using timer specific routine.. 4219.49 BogoMIPS (lpj=8438994)
CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
CPU: L2 Cache: 512K (64 bytes/line)
CPU 1/1 -> Node 0
CPU: Physical Processor ID: 0
CPU: Processor Core ID: 1
AMD Athlon(tm) X2 Dual Core Processor BE-2350 stepping 02
CPU 1: Syncing TSC to CPU 0.
CPU 1: synchronized TSC with CPU 0 (last diff 1 cycles, maxerr 581 cycles)
Brought up 2 CPUs
testing NMI watchdog ... OK.
Disabling vsyscall due to use of PM timer
time.c: Using 3.579545 MHz WALL PM GTOD PM timer.
time.c: Detected 2109.657 MHz processor.
migration_cost=255
NET: Registered protocol family 16
ACPI: bus type pci registered
PCI: Using configuration type 1
ACPI: Interpreter enabled
ACPI: Using IOAPIC for interrupt routing
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Transparent bridge - 0000:00:10.0
ACPI: Device [TPM] status [00000008]: functional but not present; setting present
ACPI: PCI Interrupt Link [LNKA] (IRQs 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKB] (IRQs 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKC] (IRQs 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKD] (IRQs 5 7 10 11 14 15) *0, disabled.
ACPI: PCI Interrupt Link [LNKE] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LNKF] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LNKG] (IRQs 16 17 18 19 20 21 22 23) *10
ACPI: PCI Interrupt Link [LNKH] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LNKI] (IRQs 16 17 18 19 20 21 22 23) *7
ACPI: PCI Interrupt Link [LNKJ] (IRQs 16 17 18 19 20 21 22 23) *11
ACPI: PCI Interrupt Link [LNKK] (IRQs 16 17 18 19 20 21 22 23) *10
ACPI: PCI Interrupt Link [LNKL] (IRQs 16 17 18 19 20 21 22 23) *11
ACPI: PCI Interrupt Link [LNKM] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LNKN] (IRQs 16 17 18 19 20 21 22 23) *5
ACPI: PCI Interrupt Link [LNKO] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: PCI Interrupt Link [LNKP] (IRQs 16 17 18 19 20 21 22 23) *0, disabled.
ACPI: Device [FDC] status [00000008]: functional but not present; setting present
ACPI: Device [LPT] status [00000008]: functional but not present; setting present
ACPI: Device [ECP] status [00000008]: functional but not present; setting present
ACPI: Device [COM2] status [00000008]: functional but not present; setting present
Generic PHY: Registered new driver
SCSI subsystem initialized
PCI: Using ACPI for IRQ routing
PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a report
PCI: Bridge: 0000:00:02.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:03.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
PCI: Bridge: 0000:00:10.0
  IO window: disabled.
  MEM window: disabled.
  PREFETCH window: disabled.
NET: Registered protocol family 2
IP route cache hash table entries: 32768 (order: 6, 262144 bytes)
TCP established hash table entries: 131072 (order: 9, 2097152 bytes)
TCP bind hash table entries: 65536 (order: 8, 1048576 bytes)
TCP: Hash tables configured (established 131072 bind 65536)
TCP reno registered
checking if image is initramfs... it is
Freeing initrd memory: 2484k freed
Simple Boot Flag at 0x36 set to 0x80
microcode: CPU0 not a capable Intel processor
microcode: CPU1 not a capable Intel processor
IA-32 Microcode Update Driver: v1.14a <tigran@aivazian.fsnet.co.uk>
audit: initializing netlink socket (disabled)
audit(1227877809.048:1): initialized
VFS: Disk quotas dquot_6.5.1
Dquot-cache hash table entries: 512 (order 0, 4096 bytes)
SGI XFS with ACLs, security attributes, large block/inode numbers, no debug enabled
SGI XFS Quota Management subsystem
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
assign_interrupt_mode Found MSI capability
assign_interrupt_mode Found MSI capability
Real Time Clock Driver v1.12ac
hpet_acpi_add: no address or irqs in _CRS
Non-volatile memory driver v1.2
WDT driver for Acquire single board computer initialising.
Acquire WDT: I/O address 0x0043 already in use
WDT driver for Advantech single board computer initialising.
Advantech WDT: initialized. timeout=60 sec (nowayout=0)
alim7101_wdt: Steve Hill <steve@navaho.co.uk>.
alim7101_wdt: ALi M7101 PMU not present - WDT not set
sc520_wdt: cannot register miscdev on minor=130 (err=-16)
eurwdt: can't misc_register on minor=130
ib700wdt: WDT driver for IB700 single board computer initialising.
ib700wdt: failed to register misc device
WDT driver for Wafer 5823 single board computer initialising.
Wafer 5823 WDT: I/O address 0x0443 already in use
sc1200wdt: build 20020303
sc1200wdt: io parameter must be specified
sbc60xxwdt: I/O address 0x0443 already in use
sbc8360: failed to register misc device
cpu5wdt: misc_register failed
WDT driver for the Winbond(TM) W83627HF Super I/O chip initialising.
w83627hf WDT: Watchdog already running. Resetting timeout to 60 sec
w83627hf WDT: cannot register miscdev on minor=130 (err=-16)
w83877f_wdt: I/O address 0x0443 already in use
W83977F WDT: W83977F WDT driver, v1.00
W83977F WDT: cannot register miscdev on minor=130 (err=-16)
machzwd: MachZ ZF-Logic Watchdog driver initializing.
machzwd: no ZF-Logic found
SoftDog: cannot register miscdev on minor=130 (err=-16)
Linux agpgart interface v0.101 (c) Dave Jones
Hangcheck: starting hangcheck timer 0.9.0 (tick is 180 seconds, margin is 60 seconds).
Hangcheck: Using monotonic_clock().
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
RAMDISK driver initialized: 16 RAM disks of 65536K size 1024 blocksize
loop: loaded (max 8 devices)
Intel(R) PRO/1000 Network Driver - version 7.3.15-k2-NAPI
Copyright (c) 1999-2006 Intel Corporation.
e100: Intel(R) PRO/100 Network Driver, 3.5.17-k2-NAPI
e100: Copyright(c) 1999-2006 Intel Corporation
Marvell 88E1101: Registered new driver
Davicom DM9161E: Registered new driver
Davicom DM9131: Registered new driver
Cicada Cis8204: Registered new driver
Cicada Cis8201: Registered new driver
LXT970: Registered new driver
LXT971: Registered new driver
QS6612: Registered new driver
Broadcom BCM5411: Registered new driver
Broadcom BCM5421: Registered new driver
Broadcom BCM5461: Registered new driver
forcedeth.c: Reverse Engineered nForce ethernet driver. Version 0.59.
ACPI: PCI Interrupt Link [LNKL] enabled at IRQ 23
ACPI: PCI Interrupt 0000:00:14.0[A] -> Link [LNKL] -> GSI 23 (level, high) -> IRQ 23
forcedeth: using HIGHDMA
eth0: forcedeth.c: subsystem: 01734:10c6 bound to 0000:00:14.0
tun: Universal TUN/TAP device driver, 1.6
tun: (C) 1999-2004 Max Krasnyansky <maxk@qualcomm.com>
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
NFORCE-MCP51: IDE controller at PCI slot 0000:00:0d.0
NFORCE-MCP51: chipset revision 241
NFORCE-MCP51: not 100% native mode: will probe irqs later
NFORCE-MCP51: BIOS didn't set cable bits correctly. Enabling workaround.
NFORCE-MCP51: 0000:00:0d.0 (rev f1) UDMA133 controller
    ide0: BM-DMA at 0x8c00-0x8c07, BIOS settings: hda:pio, hdb:pio
Adaptec aacraid driver (1.1-5[2423]-mh3)
3ware Storage Controller device driver for Linux v1.26.02.002.
3ware 9000 Storage Controller device driver for Linux v2.26.02.009.
PCI: Enabling device 0000:00:0e.0 (0005 -> 0007)
ACPI: PCI Interrupt Link [LNKN] enabled at IRQ 22
ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKN] -> GSI 22 (level, high) -> IRQ 22
ata1: SATA max UDMA/133 cmd 0x8C30 ctl 0x8C26 bmdma 0x8C10 irq 22
ata2: SATA max UDMA/133 cmd 0x8C28 ctl 0x8C22 bmdma 0x8C18 irq 22
scsi0 : sata_nv
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
scsi1 : sata_nv
ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata2.00: ATA-7, max UDMA/133, 312581808 sectors: LBA48 NCQ (depth 0/32)
ata2.00: ata2: dev 0 multi count 16
ata2.00: configured for UDMA/133
scsi 0:0:0:0: Direct-Access     ATA      ST3160215AS      3.AA PQ: 0 ANSI: 5
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sda: 312581808 512-byte hdwr sectors (160042 MB)
sda: Write Protect is off
SCSI device sda: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sda: sda1 sda2 sda4 < sda5 sda6 sda7 sda8 >
sd 0:0:0:0: Attached scsi disk sda
sd 0:0:0:0: Attached scsi generic sg0 type 0
scsi 1:0:0:0: Direct-Access     ATA      ST3160215AS      3.AA PQ: 0 ANSI: 5
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
SCSI device sdb: 312581808 512-byte hdwr sectors (160042 MB)
sdb: Write Protect is off
SCSI device sdb: write cache: enabled, read cache: enabled, doesn't support DPO or FUA
 sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 sdb7 sdb8 >
sd 1:0:0:0: Attached scsi disk sdb
sd 1:0:0:0: Attached scsi generic sg1 type 0
kvm: no hardware support
serio: i8042 KBD port at 0x60,0x64 irq 1
serio: i8042 AUX port at 0x60,0x64 irq 12
mice: PS/2 mouse device common for all mice
I2O subsystem v1.325
i2o: max drivers = 8
i2c /dev entries driver
i2c_adapter i2c-0: nForce2 SMBus adapter at 0x88c0
i2c_adapter i2c-1: nForce2 SMBus adapter at 0x8880
hdaps: supported laptop not found!
hdaps: driver init failed (ret=-19)!
md: linear personality registered for level -1
md: raid0 personality registered for level 0
md: raid1 personality registered for level 1
md: raid10 personality registered for level 10
md: faulty personality registered for level -5
device-mapper: ioctl: 4.11.0-ioctl (2006-10-12) initialised: dm-devel@redhat.com
nf_conntrack version 0.5.0 (3964 buckets, 31712 max)
ip_tables: (C) 2000-2006 Netfilter Core Team
ClusterIP Version 0.8 loaded successfully
arp_tables: (C) 2002 David S. Miller
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
NET: Registered protocol family 15
powernow-k8: Found 2 AMD Athlon(tm) X2 Dual Core Processor BE-2350 processors (version 2.00.00)
powernow-k8:    0 : fid 0xd (2100 MHz), vid 0xe
powernow-k8:    1 : fid 0xc (2000 MHz), vid 0xf
powernow-k8:    2 : fid 0xa (1800 MHz), vid 0x11
powernow-k8:    3 : fid 0x2 (1000 MHz), vid 0x16
Freeing unused kernel memory: 380k freed
Boot logging started on /dev/ttyS0(/dev/console) at Fri Nov 28 13:10:12 2008
Creating device nodes with udev
md: md1 stopped.
md: bind<sdb1>
md: bind<sda1>
modprobe: FATAL:raid1: raid set md1 active with 2 out of 2 mirrors
 Could not load /lib/modules/2.6.20.21-071108a/modules.dep: No such file or directory

mdadm: /dev/md1 has been started with 2 drives.
Waiting for device /dev/root to appear:  ok
showconsole: Warning: the ioctl TIOCGDEV is not known by the kernel
fsck 1.39 (29-May-2006)
[/bin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/root
/ (/dev/root): recovering journal
/ (/dev/root) has been mounted 22 times without being checked, check forced.
/ (/dev/root): 6434/123648 files (1.3% non-contiguous), 147194/246960 blocks
fsck succeeded. Mounting root device read-only.
Mounting root /dev/root
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
INIT: version 2.86 booting
System Boot Control: Running /etc/init.d/boot
Mounting procfs at /proc                                              done
Mounting sysfs at /sys                                                done
Initializing /dev                                                     done
Mounting devpts at /dev/pts                                           done
Starting udevd                                                        done
Activating swap-devices in /etc/fstab...
Adding 1959920k swap on /dev/sda2.  Priority:-1 extents:1 across:1959920k
Adding 1959920k swap on /dev/sdb2.  Priority:-2 extents:1 across:19599done
showconsole: Warning: the ioctl TIOCGDEV is not known by the kernel
EXT3 FS on md1, internal journal
Loading required kernel modules                                       done
                                                                      done
Activating device mapper...
FATAL: Module dm_mod not found.
                                                                      failed
Starting MD Raid mdadm: No arrays found in config file
md: md0 stopped.
md: bind<sdb5>
md: bind<sda5>
raid1: raid set md0 active with 2 out of 2 mirrors
mdadm: /dev/md0 has been started with 2 drives.
md: md2 stopped.
md: bind<sdb6>
md: bind<sda6>
raid1: raid set md2 active with 2 out of 2 mirrors
mdadm: /dev/md2 has been started with 2 drives.
md: md3 stopped.
md: bind<sdb7>
md: bind<sda7>
raid1: raid set md3 active with 2 out of 2 mirrors
mdadm: /dev/md3 has been started with 2 drives.
md: md4 stopped.
md: bind<sdb8>
md: bind<sda8>
raid1: raid set md4 active with 2 out of 2 mirrors
mdadm: /dev/md4 has been started with 2 drives.
                                                                      failed
Waiting for udev to settle...
Scanning for LVM volume groups...
  Reading all physical volumes.  This may take a while...
  No volume groups found
  No volume groups found
Activating LVM volume groups...
  No volume groups found
                                                                      done
Waiting for none .
no more events
showconsole: Warning: the ioctl TIOCGDEV is not known by the kernel
Checking file systems...
fsck 1.39 (29-May-2006)
Checking all file systems.
[/sbin/fsck.xfs (1) -- /usr] fsck.xfs -a /dev/md5
/sbin/fsck.xfs: XFS file system.
[/sbin/fsck.xfs (1) -- /var] fsck.xfs -a /dev/md6
/sbin/fsck.xfs: XFS file system.
[/sbin/fsck.xfs (1) -- /home] fsck.xfs -a /dev/md7
/sbin/fsck.xfs: XFS file system.
[/sbin/fsck.xfs (1) -- /srv] fsck.xfs -a /dev/md8
/sbin/fsck.xfs: XFS file system.                                      done
                                                                      done
Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
mount: /dev/md5: can't read superblock
mount: /dev/md6: can't read superblock
mount: /dev/md7: can't read superblock
mount: /dev/md8: can't read superblock
none on /tmp type tmpfs (rw)                                          failed
Setting up the hardware clock                                         done
Creating /var/log/boot.msg
Can't open or create /var/run/klogd.pid.                              failed
/etc/init.d/boot.d/S09boot.klog: line 38: /var/log/boot.msg: No such file or directory
Setting current sysctl status from /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
                                                                      done
Retry device configuration                                            done
Enabling syn flood protection                                         done
Disabling IP forwarding                                               done
                                                                      done
                                                                      done
Activating remaining swap-devices in /etc/fstab...                    done
/etc/init.d/boot.d/S13boot.cleanup: line 48: /var/run/utmp: No such file or directory
Setting up hostname 's15293006'                                       done
Setting up loopback interface     lo
    lo        IP address: 127.0.0.1/8
                                                                      done
System Boot Control: The system has been                              set up
Failed features:                                              boot.md boot.cleanup
Skipped features:                                                       boot.cycle
System Boot Control: Running /etc/init.d/boot.local                   done
INIT: Entering runlevel: 3
blogd: Warning: the ioctl TIOCGDEV is not known by the kernel
Boot logging started on /dev/ttyS0(/dev/console) at Fri Nov 28 08:10:34 2008
Master Resource Control: previous runlevel: N, switching to runlevel: 3
modprobe: FATAL: Module ac not found.

modprobe: FATAL: Module battery not found.

modprobe: FATAL: Module button not found.

modprobe: FATAL: Module fan not found.

modprobe: FATAL: Module processor not found.

modprobe: FATAL: Module thermal not found.

psa-firewall: service is disabled
psa-vpn: OpenVPN is disabled
Initializing random number generator/etc/init.d/random: line 40: /var/lib/misc/random-seed: No such file or directory
chmod: cannot access `/var/lib/misc/random-seed': No such file or directory
                                                                      failed
modprobe: FATAL: Module asus_acpi not found.

modprobe: FATAL: Module ibm_acpi not found.

modprobe: FATAL: Module toshiba_acpi not found.

modprobe: FATAL: Module sony_acpi not found.

modprobe: FATAL: Module pcc_acpi not found.

Starting resource manager/etc/init.d/resmgr: line 68: cd: /var/run/resmgr/classes: No such file or directory
startproc:  exit status of parent of /sbin/resmgrd: 1
                                                                      failed
acpid: loading ACPI modules ( )                                       failed
acpid: will not skip unsupported modules
acpid: probing laptop ACPI modules
touch: cannot touch `/var/lib/acpi/laptop_modules': No such file or directory
acpid: added /etc/init.d/acpid: line 88: /var/lib/acpi/laptop_modules: No such file or directory
to /var/lib/acpi/laptop_modules                                       done
Starting acpid acpid: can't open socket /var/run/acpid.socket: No such file or directory
startproc:  exit status of parent of /sbin/acpid: 1
                                                                      failed
/etc/init.d/kbd: line 41: locale: command not found
/etc/init.d/kbd: line 138: find: command not found
Can not find a keymap for us, trying fallback.
Loading keymap Loading /etc/defkeymap.map                             failed
no /usr/sbin -> Numlock off.
Loading compose table winkeys shiftctrl latin1.add                    failed
Stop Unicode mode                                                     done
Setting up network interfaces:
    lo
    lo        IP address: 127.0.0.1/8                                 done
    eth0      device: Unknown device 10de:0268 (rev a3)
    eth0      configuration: eth-id-00:19:99:26:fa:66
    eth0      (DHCP) . IP/Netmask: 87.106.212.48 / 255.255.255.255 ('s15293006')
    eth0:1    IP address: 212.227.250.134/32                          done
Setting up service network  .  .  .  .  .  .  .  .  .  .  .  .  .  .  done
/etc/init.d/syslog: line 93: mkfifo: command not found
chown: cannot access `/dev/xconsole': No such file or directory
Starting syslog services/etc/init.d/syslog: line 110: /var/lock/subsys/syslogd: No such file or directory
                                                                      done
Starting ZENworks Management Daemon/etc/init.d/novell-zmd: line 86: /usr/sbin/zmd: No such file or directory
                                                                      failed
/usr/sbin/nscd not installed
Starting Courier-IMAP server:
   Starting imapd/etc/init.d/courier-imap: line 63: /usr/lib/courier-imap/imapd.rc: No such file or directory
                                                                      failed
   Starting pop3/etc/init.d/courier-imap: line 63: /usr/lib/courier-imap/pop3d.rc: No such file or directory
                                                                      failed

/etc/init.d/courier-imap: line 185: dirname: command not found
Mount CIFS File Systems                                               unused
touch: cannot touch `/var/lock/subsys/smbfs': No such file or directory
/etc/init.d/qmail: line 120: dirname: command not found
start-stop-daemon: stat /var/qmail/bin/qmail-send: No such file or directory
Starting qmail:                                                       failed
/etc/init.d/psa: line 111: perl: command not found
Starting xinetd service...                                            failed
Starting named service...                                             failed
Starting mysql service...                                             failed
Starting qmail service...                                             failed
Starting courier-imap service...                                      done
Starting postgresql service...                                        not installed
Starting psa-spamassassin service...                                  done
/etc/init.d/psa: line 263: /usr/bin/mysql: No such file or directory
/etc/init.d/psa: line 275: /usr/local/psa/admin/sbin/websrvmng: No such file or directory
/etc/init.d/psa: line 140: /usr/bin/mysql: No such file or directory
Starting Plesk...                                                     failed
/etc/init.d/psa: line 149: /usr/bin/mysql: No such file or directory
blogd: no message logging because /var file system is not accessible
Master Resource Control: runlevel 3 has been                          reached
Failed services in runlevel 3: acpid kbd psa-firewall random resmgr novell-zmd qmail
Skipped services in runlevel 3: dbus irq_balancer policykitd haldaemon sshd xinetd nscd powersaved smbfs cron mailman


Welcome to openSUSE 10.2 (X86-64) - Kernel 2.6.20.21-071108a (ttyS0).


s1xxxxxxx login:
please Help :(
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

kann oder will mir hier keiner mehr weiter helfen? bitte leute ich brauche da nen tip was ich machen kann
Top
Roger Wilco
Posts: 5923
Joined: 2004-05-23 12:53
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Roger Wilco »

quax wrote:

Code: Select all

Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
mount: /dev/md5: can't read superblock
mount: /dev/md6: can't read superblock
mount: /dev/md7: can't read superblock
mount: /dev/md8: can't read superblock
none on /tmp type tmpfs (rw)                                          failed
Hast du an deiner /etc/fstab herumgespielt? Kannst du die genannten Partitionen im Rescue-System einbinden?
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11190
Joined: 2003-02-27 01:00
Location: Hamburg
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Joe User »

Es wird noch immer der falsche Kernel geladen:

Code: Select all

modprobe: FATAL:raid1: raid set md1 active with 2 out of 2 mirrors
Could not load /lib/modules/2.6.20.21-071108a/modules.dep: No such file or directory
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

ok, super, danke, dann versuch ich den letzen möglichen, wobei ich schon dachte, dass es der richtige sein muss!???
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

Roger Wilco wrote:
quax wrote:

Code: Select all

Mounting local file systems...
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
mount: /dev/md5: can't read superblock
mount: /dev/md6: can't read superblock
mount: /dev/md7: can't read superblock
mount: /dev/md8: can't read superblock
none on /tmp type tmpfs (rw)                                          failed
Hast du an deiner /etc/fstab herumgespielt? Kannst du die genannten Partitionen im Rescue-System einbinden?
nein, höchstens durch den aufruf des yast um den bootloader neu zu installieren wäre das passiert?!

ich werde nochmals versuchen die lilo.conf mit dem dritten kernel der auf dem system liegt zu konfiguerieren und dann nochmals zu booten, hoffe das wars dann, ich melde mich wieder (heute noch)
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

ok, hab den server mit der rescue nochmals gebootet, kan die md1 mounten und komme auf /boot

hab mit vi in der lilo.conf den eintrag auf den kernel vmlinuz-2.6.23.17-20080303a geändert und gespeichert

den verweis "vmlinuz" neu gemacht ebenfalls auf vmlinuz-2.6.23.17-20080303a

danach auch nochmals lilo eingegeben und umount /dev/md1

dann neustart.

offensichtlich hat er aber den alten kernel behalten, gleicher fehler!

modprobe: FATAL:raid1: raid set md1 active with 2 out of 2 mirrors
Could not load /lib/modules/2.6.20.21-071108a/modules.dep: No such file or directory


noch jemand nen tip???
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11190
Joined: 2003-02-27 01:00
Location: Hamburg
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Joe User »

Code: Select all

ls -alh /boot /lib/modules
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

rescue:/# ls -alh /boot /lib/modules

Code: Select all

/boot:
total 22M
drwxr-xr-x  4 root root 4.0K Nov 29 10:08 .
drwxr-xr-x 22 root root 4.0K Nov 28 08:48 ..
-rw-r--r--  1 root root 932K Nov  6 20:10 System.map-2.6.18.8-0.13-default
-rw-r--r--  1 root root 1.3M Nov  8  2007 System.map-2.6.20.21-071108a
-rw-r--r--  1 root root 1.3M Mar  3  2008 System.map-2.6.23.17-20080303a
-rw-------  1 root root  512 Nov 28 07:38 backup_mbr
lrwxrwxrwx  1 root root    1 Apr  1  2008 boot -> .
-rw-r--r--  1 root root  512 Apr  1  2008 boot.0800
-rw-r--r--  1 root root  512 Apr  1  2008 boot.0810
-rw-r--r--  1 root root  512 Nov 28 02:25 boot.0901
-rw-r--r--  1 root root  63K Nov  6 20:13 config-2.6.18.8-0.13-default
-rw-r--r--  1 root root  35K Nov  8  2007 config-2.6.20.21-071108a
-rw-r--r--  1 root root  35K Mar  3  2008 config-2.6.23.17-20080303a
drwxr-xr-x  2 root root 4.0K Nov 28 07:36 grub
lrwxrwxrwx  1 root root   24 Nov 28 07:38 initrd -> initrd-2.6.20.21-071108a
-rw-r--r--  1 root root 3.1M Nov 28 07:38 initrd-2.6.18.8-0.13-default
-rw-r--r--  1 root root 2.5M Nov 28 07:38 initrd-2.6.20.21-071108a
-rw-r--r--  1 root root 2.5M Nov 28 07:38 initrd-2.6.23.17-20080303a
drwx------  2 root root  48K Apr  1  2008 lost+found
-rw-------  1 root root 173K Nov 29 10:08 map
-rw-------  1 root root 371K Nov 28 07:38 message
-rw-r--r--  1 root root 119K Nov  6 20:14 symsets-2.6.18.8-0.13-default.tar.gz
-rw-r--r--  1 root root 331K Nov  6 20:14 symtypes-2.6.18.8-0.13-default.gz
-rw-r--r--  1 root root  97K Nov  6 20:13 symvers-2.6.18.8-0.13-default.gz
-rwxr-xr-x  1 root root 2.1M Nov  6 20:12 vmlinux-2.6.18.8-0.13-default.gz
lrwxrwxrwx  1 root root   27 Nov 29 10:06 vmlinuz -> vmlinuz-2.6.23.17-20080303a
-rw-r--r--  1 root root 1.6M Nov  6 20:10 vmlinuz-2.6.18.8-0.13-default
-rw-r--r--  1 root root 2.8M Nov  8  2007 vmlinuz-2.6.20.21-071108a
-rw-r--r--  1 root root 2.6M Mar  3  2008 vmlinuz-2.6.23.17-20080303a
lrwxrwxrwx  1 root root   25 Apr  1  2008 vmlinuz.old -> vmlinuz-2.6.20.21-071108a

/lib/modules:
total 20K
drwxr-xr-x 5 root root 4.0K Nov 27 10:42 .
drwxr-xr-x 7 root root 4.0K Nov 27 10:38 ..
drwxr-xr-x 3 root root 4.0K Nov 27 10:43 2.6.18.8-0.13-default
drwxr-xr-x 3 root root 4.0K Nov  8  2007 2.6.20.21-071108a
drwxr-xr-x 3 root root 4.0K Mar  3  2008 2.6.23.17-20080303a
und gleich noch die aktuelle lilo.conf, die ich von hand geändert habe!

Code: Select all

# Modified by YaST2. Last modification on Fri Nov 28 02:53:16 EST 2008
root = /dev/md1
install = /boot/boot.b
vga = normal
timeout = 60
prompt
lba32
read-only
default = Linux
serial = 0,57600n8
append = "console=ttyS0,57600 console=tty0"
boot = /dev/md1

image = /boot/vmlinuz-2.6.23.17-20080303a
###Don't change this comment - YaST2 identifier: Original name: linux###
    label = Linux
    append = " console=tty0 console=ttyS0,57600 panic=30"
    initrd = /boot/initrd-2.6.23.17-20080303a
    root = /dev/md1

image = /boot/vmlinuz-2.6.23.17-20080303a
###Don't change this comment - YaST2 identifier: Original name: failsafe###
    label = Failsafe
    append = "showopts ide=nodma apm=off acpi=off noresume edd=off 3"
    initrd = /boot/initrd-2.6.23.17-20080303a
    root = /dev/md1

image = /boot/vmlinuz
    label = lxser
    append = " console=tty0 console=ttyS0,57600 panic=30"

image = /boot/vmlinuz
    label = lx
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11190
Joined: 2003-02-27 01:00
Location: Hamburg
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Joe User »

Code: Select all

rm -f /boot/*{18,20}*
rm -rf /lib/modules/*{18,20}*

rm -f /boot/{vmlinuz,initrd,System.map}
ln -sf /boot/initrd-2.6.23.17-20080303a initrd
ln -sf /boot/vmlinuz-2.6.23.17-20080303a vmlinuz
ln -sf /boot/System.map-2.6.23.17-20080303a System.map

cat > /etc/lilo.conf << "EOF"
root = /dev/md1
install = /boot/boot.b
vga = normal
timeout = 60
prompt
lba32
read-only
default = Linux
serial = 0,57600n8
append = "console=ttyS0,57600 console=tty0"
boot = /dev/md1

image = /boot/vmlinuz
	label = Linux
	append = " console=tty0 console=ttyS0,57600 panic=30"
	initrd = /boot/initrd
	root = /dev/md1
EOF

/sbin/lilo
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

rescue:/etc# /sbin/lilo
Warning: '/proc/partitions' does not exist, disk scan bypassed
Fatal: open /boot/vmlinuz: No such file or directory
rescue:/etc#

oh, hab vergessen

mount /proc

dann nochmal

/sbin/lilo und folgender fehler

Fatal: open /boot/vmlinuz: No such file or directory

in /boot schauts nun so aus????

rescue:/boot# ls -la
total 632
drwxr-xr-x 4 root root 4096 Nov 29 14:10 .
drwxr-xr-x 22 root root 4096 Nov 28 08:48 ..
-rw------- 1 root root 512 Nov 28 07:38 backup_mbr
lrwxrwxrwx 1 root root 1 Apr 1 2008 boot -> .
-rw-r--r-- 1 root root 512 Apr 1 2008 boot.0800
-rw-r--r-- 1 root root 512 Apr 1 2008 boot.0810
-rw-r--r-- 1 root root 512 Nov 28 02:25 boot.0901
drwxr-xr-x 2 root root 4096 Nov 28 07:36 grub
drwx------ 2 root root 49152 Apr 1 2008 lost+found
-rw------- 1 root root 176640 Nov 29 11:20 map
-rw------- 1 root root 379904 Nov 28 07:38 message
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11190
Joined: 2003-02-27 01:00
Location: Hamburg
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Joe User »

Da hast Du falsch abgetippt und alle Kernel gelöscht. Installiere den Provider-Kernel bitte neu und dann:

Code: Select all

cd /boot
rm -f {vmlinuz,initrd,System.map}
ln -sf initrd-2.6.23.17-20080303a initrd
ln -sf vmlinuz-2.6.23.17-20080303a vmlinuz
ln -sf System.map-2.6.23.17-20080303a System.map

cat > /etc/lilo.conf << "EOF"
root = /dev/md1
install = /boot/boot.b
vga = normal
timeout = 60
prompt
lba32
read-only
default = Linux
serial = 0,57600n8
append = "console=ttyS0,57600 console=tty0"
boot = /dev/md1

image = /boot/vmlinuz
	label = Linux
	append = " console=tty0 console=ttyS0,57600 panic=30"
	initrd = /boot/initrd
	root = /dev/md1
EOF

/sbin/lilo
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

[quote="Joe User"]Da hast Du falsch abgetippt und alle Kernel gelöscht. Installiere den Provider-Kernel bitte neu und dann:

Code: Select all


kann ich dann auch grad den aktuellsten verwenden? wenn schon den schon?
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11190
Joined: 2003-02-27 01:00
Location: Hamburg
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Joe User »

Ja, ich bitte darum ;) Vergiss aber nicht die Versionen in den Befehlen anzupassen...
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

sodele ^^^

also hab den aktuellen kernel runter geladen und entpackt, dann in /boot rein und die befehle der reihe nach abgearbeitet.

/sbin/lilo funtz net "mount /proc" hab ich gemacht

Code: Select all

Warning: '/proc/partitions' does not exist, disk scan bypassed
Fatal: open /boot/initrd: No such file or directory
bei lilo -v bekomme ich ne genauere meldung

Code: Select all

LILO version 22.7, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2005 John Coffman
Released 12-Apr-2005, and compiled at 23:46:22 on Nov 27 2006

Warning: '/proc/partitions' does not exist, disk scan bypassed
Using BIOS device code 0x80 for RAID boot blocks
Reading boot sector from /dev/md1
Using MENU secondary loader
Calling map_insert_data

Boot image: /boot/vmlinuz -> vmlinuz-2.6.27.7-20081121a
Mapping RAM disk /boot/initrd -> initrd-2.6.27.7-20081121a
Fatal: open /boot/initrd: No such file or directory
es fehlt mir noch die initrd-2.6.27.7-20081121a

hm, sorry aber wie bekomme ich die?
Top
wgot
Posts: 1675
Joined: 2003-07-06 02:03
 

Re: 1&1 Root Server Bootet nicht mehr

Post by wgot »

Hallo,

wenn der 1&1-Kernel eine initrd benötigt, dann ist die mit reingepackt und nach dem Auspacken in /boot/. Allerdings sind die Kernel bei 1&1 häufig ohne initrd gebaut, dann muß in der lilo.conf die zeile für initrd raus und lilo nochmal aufgerufen werden.

Bist Du sicher, daß Du vom 1&1-Server den richtigen Kernel geholt hast, also einen für deine Serverhardware bestimmten?

Gruß, Wolfgang
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

also die initrd ist nicht im kernel packet das ich vom support genannt bekommen hab. das paket ist für mein server, hab ein mit amd64 proz. und das aktuelle kernel paket ist "linux-image-2.6.27.7-20081121a-rootserver.1_AMD64.tgz"

also auskommentieren?

also dann

Code: Select all

cat > /etc/lilo.conf << "EOF"
> root = /dev/md1
> install = /boot/boot.b
> vga = normal
> timeout = 60
> prompt
> lba32
> read-only
> default = Linux
> serial = 0,57600n8
> append = "console=ttyS0,57600 console=tty0"
> boot = /dev/md1
> 
> image = /boot/vmlinuz
>    label = Linux
>    append = " console=tty0 console=ttyS0,57600 panic=30"
>    root = /dev/md1
> EOF
rescue:/boot# /sbin/lilo 
Warning: '/proc/partitions' does not exist, disk scan bypassed
Added Linux *
The boot record of  /dev/md1  has been updated.
Top
User avatar
Joe User
Project Manager
Project Manager
Posts: 11190
Joined: 2003-02-27 01:00
Location: Hamburg
 

Re: 1&1 Root Server Bootet nicht mehr

Post by Joe User »

Jupp, jetzt sollte er auch booten.
PayPal.Me/JoeUser ● FreeBSD Remote Installation
Wings for Life ● Wings for Life World Run

„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
Top
quax
Posts: 27
Joined: 2008-11-27 22:48
 

Re: 1&1 Root Server Bootet nicht mehr

Post by quax »

bekomme keine anzeige auf der console, kann das sein dass es etwas dauert? oder hab ich jetzt ein fehler in der ausgabe ?
Top

Return to “Serverdienste”