• Willkommen im Linux Club - dem deutschsprachigen Supportforum für GNU/Linux. Registriere dich kostenlos, um alle Inhalte zu sehen und Fragen zu stellen.

kein zugriff mehr auf root server

djsmoke

Newbie
hallo ,

seit gestern abend habe ich kein zugriff mehr auf meinen server. hab direkt bei service center angerufen mir wurde gesagt ich soll es im rescue modus starten. soweit alles in ordnung. nur jetzt komm ich nicht mehr weiter . kann mir einer vielleicht mehr information geben.

auf den server läuft SUSE 10.2 (64bit)


danke für weitere information
 

Z-City

Hacker
Damit man auch nachvollziehen kann um was es hier geht:

http://www.linux-club.de/viewtopic.php?f=70&t=75023
 

nbkr

Guru
Der Rescue Modus ist üblicherweise ein zweites Betriebssystem welches über Netz gebootet wird und dir Zugriff auf die Festplatten deines Servers gibt. Damit kannst Du dann Reparaturen durchführen. Welche das auch immer sind. Wenn als der Rescue Modus läuft verbindest Du dich per SSH zu der IP deines Servers. Username und Passwort sollten im Loginbereich deines Hosters sein. Es sind _nicht_ die deines Servers. Was Du danach machst hängt davon ab was kaputt ist. Die die Maschine "einfach so" ausgefallen ist - also kein Update oder ähnliches gemacht wurde - würde ich zuerst die Platten des Rechners auf Fehler prüfen. Wenn das nichts bringt die Platten mounten und die Logfiles durchsuchen, Backup machen, etc.
 
OP
D

djsmoke

Newbie
danke für deine antwort .

ne verbindung hab ich ja über ssh in rescue mode ich habe ja auf fehler überrüfen lassen kriege diese meldung

Code:
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 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       30401   241248105    5  Extended
/dev/sda5             368         976     4891761   fd  Linux raid autodetect
/dev/sda6             977        1585     4891761   fd  Linux raid autodetect
/dev/sda7            1586        4018    19543041   fd  Linux raid autodetect
/dev/sda8            4019       30401   211921416   fd  Linux raid autodetect

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 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       30401   241248105    5  Extended
/dev/sdb5             368         976     4891761   fd  Linux raid autodetect
/dev/sdb6             977        1585     4891761   fd  Linux raid autodetect
/dev/sdb7            1586        4018    19543041   fd  Linux raid autodetect
/dev/sdb8            4019       30401   211921416   fd  Linux raid autodetect

Disk /dev/md8: 217.0 GB, 217007456256 bytes
2 heads, 4 sectors/track, 52980336 cylinders
Units = cylinders of 8 * 512 = 4096 bytes

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

Disk /dev/md7: 20.0 GB, 20012007424 bytes
2 heads, 4 sectors/track, 4885744 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
 

nbkr

Guru
Sieht nach Problemen mit dem Softraid aus. Lass dir mal von mdadm sagen wie der Zustand und die Konfiguration des Raids ist. Achja: Auf jeden Fall Backup machen, das bringt Extraleben.
 
OP
D

djsmoke

Newbie
ja das versuche ich ja weil meine geschäftseite mit den ganzen daten laufen da drauf und ich Idiot hab vorher kein backup gemacht. hätte ich einen backup von datenbaken usw hätte ich den server einfach neu instalieren lassen.

Kriege ich den in rescue mode irgendwie backup von datenbanken usw.



Hier ist in rescue mode /var/log/messages

Code:
May 27 13:30:16 rescue kernel: NFORCE-MCP51: BIOS didn't set cable bits correctly. Enabling workaround.
May 27 13:30:16 rescue kernel: NFORCE-MCP51: 0000:00:0d.0 (rev f1) UDMA133 controller
May 27 13:30:16 rescue kernel:     ide0: BM-DMA at 0x8c00-0x8c07, BIOS settings: hda:pio, hdb:pio
May 27 13:30:16 rescue kernel: NFORCE-MCP51: IDE port disabled
May 27 13:30:16 rescue kernel: 3ware Storage Controller device driver for Linux v1.26.02.002.
May 27 13:30:16 rescue kernel: 3ware 9000 Storage Controller device driver for Linux v2.26.02.010.
May 27 13:30:16 rescue kernel: Driver 'sd' needs updating - please use bus_type methods
May 27 13:30:16 rescue kernel: ACPI: PCI Interrupt Link [LNKN] enabled at IRQ 22
May 27 13:30:16 rescue kernel: ACPI: PCI Interrupt 0000:00:0e.0[A] -> Link [LNKN] -> GSI 22 (level, high) -> IRQ 22
May 27 13:30:16 rescue kernel: scsi0 : sata_nv
May 27 13:30:16 rescue kernel: scsi1 : sata_nv
May 27 13:30:16 rescue kernel: ata1: SATA max UDMA/133 cmd 0x8c30 ctl 0x8c24 bmdma 0x8c10 irq 22
May 27 13:30:16 rescue kernel: ata2: SATA max UDMA/133 cmd 0x8c28 ctl 0x8c20 bmdma 0x8c18 irq 22
May 27 13:30:16 rescue kernel: ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 27 13:30:16 rescue kernel: ata1.00: ATA-7: ST3250820AS, 3.AAE, max UDMA/133
May 27 13:30:16 rescue kernel: ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
May 27 13:30:16 rescue kernel: ata1.00: configured for UDMA/133
May 27 13:30:16 rescue kernel: ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
May 27 13:30:16 rescue kernel: ata2.00: ATA-7: ST3250820AS, 3.AAE, max UDMA/133
May 27 13:30:16 rescue kernel: ata2.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 0/32)
May 27 13:30:16 rescue kernel: ata2.00: configured for UDMA/133
May 27 13:30:16 rescue kernel: scsi 0:0:0:0: Direct-Access     ATA      ST3250820AS      3.AA PQ: 0 ANSI: 5
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] Write Protect is off
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] 488397168 512-byte hardware sectors (250059 MB)
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] Write Protect is off
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 27 13:30:16 rescue kernel:  sda: sda1 sda2 sda4 < sda5 sda6 sda7 sda8 >
May 27 13:30:16 rescue kernel: sd 0:0:0:0: [sda] Attached SCSI disk
May 27 13:30:16 rescue kernel: sd 0:0:0:0: Attached scsi generic sg0 type 0
May 27 13:30:16 rescue kernel: scsi 1:0:0:0: Direct-Access     ATA      ST3250820AS      3.AA PQ: 0 ANSI: 5
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] 488397168 512-byte hardware sectors (250059 MB)
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] Write Protect is off
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
May 27 13:30:16 rescue kernel:  sdb: sdb1 sdb2 sdb4 < sdb5 sdb6 sdb7 sdb8 >
May 27 13:30:16 rescue kernel: sd 1:0:0:0: [sdb] Attached SCSI disk
May 27 13:30:16 rescue kernel: sd 1:0:0:0: Attached scsi generic sg1 type 0
May 27 13:30:16 rescue kernel: PNP: PS/2 Controller [PNP0303:KEYB,PNP0f13:PS2M] at 0x60,0x64 irq 1,12
May 27 13:30:16 rescue kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
May 27 13:30:16 rescue kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
May 27 13:30:16 rescue kernel: mice: PS/2 mouse device common for all mice
May 27 13:30:16 rescue kernel: I2O subsystem v1.325
May 27 13:30:16 rescue kernel: i2o: max drivers = 8
May 27 13:30:16 rescue kernel: i2c /dev entries driver
May 27 13:30:16 rescue kernel: i2c-adapter i2c-0: nForce2 SMBus adapter at 0x88c0
May 27 13:30:16 rescue kernel: i2c-adapter i2c-1: nForce2 SMBus adapter at 0x8880
May 27 13:30:16 rescue kernel: WDT driver for Acquire single board computer initialising.
May 27 13:30:16 rescue kernel: acquirewdt: probe of acquirewdt failed with error -5
May 27 13:30:16 rescue kernel: WDT driver for Advantech single board computer initialising.
May 27 13:30:16 rescue kernel: advantechwdt: initialized. timeout=60 sec (nowayout=0)
May 27 13:30:16 rescue kernel: alim7101_wdt: Steve Hill <steve@navaho.co.uk>.
May 27 13:30:16 rescue kernel: alim7101_wdt: ALi M7101 PMU not present - WDT not set
May 27 13:30:16 rescue kernel: ib700wdt: WDT driver for IB700 single board computer initialising.
May 27 13:30:16 rescue kernel: ib700wdt: probe of ib700wdt failed with error -5
May 27 13:30:16 rescue kernel: WDT driver for Wafer 5823 single board computer initialising.
May 27 13:30:16 rescue kernel: sc1200wdt: build 20020303
May 27 13:30:16 rescue kernel: WDT driver for the Winbond(TM) W83627HF/THF/HG Super I/O chip initialising.
May 27 13:30:16 rescue kernel: w83627hf/thf/hg WDT: Watchdog already running. Resetting timeout to 60 sec
May 27 13:30:16 rescue kernel: machzwd: MachZ ZF-Logic Watchdog driver initializing.
May 27 13:30:16 rescue kernel: machzwd: no ZF-Logic found
May 27 13:30:16 rescue kernel: md: linear personality registered for level -1
May 27 13:30:16 rescue kernel: md: raid0 personality registered for level 0
May 27 13:30:16 rescue kernel: md: raid1 personality registered for level 1
May 27 13:30:16 rescue kernel: md: raid10 personality registered for level 10
May 27 13:30:16 rescue kernel: raid6: int64x1   1434 MB/s
May 27 13:30:16 rescue kernel: raid6: int64x2   2040 MB/s
May 27 13:30:16 rescue kernel: raid6: int64x4   2435 MB/s
May 27 13:30:16 rescue kernel: raid6: int64x8   1789 MB/s
May 27 13:30:16 rescue kernel: raid6: sse2x1    2813 MB/s
May 27 13:30:16 rescue kernel: raid6: sse2x2    4063 MB/s
May 27 13:30:16 rescue kernel: raid6: sse2x4    4180 MB/s
May 27 13:30:16 rescue kernel: raid6: using algorithm sse2x4 (4180 MB/s)
May 27 13:30:16 rescue kernel: md: raid6 personality registered for level 6
May 27 13:30:16 rescue kernel: md: raid5 personality registered for level 5
May 27 13:30:16 rescue kernel: md: raid4 personality registered for level 4
May 27 13:30:16 rescue kernel: md: faulty personality registered for level -5
May 27 13:30:16 rescue kernel: device-mapper: ioctl: 4.12.0-ioctl (2007-10-02) initialised: dm-devel@redhat.com
May 27 13:30:16 rescue kernel: Netfilter messages via NETLINK v0.30.
May 27 13:30:16 rescue kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
May 27 13:30:16 rescue kernel: ctnetlink v0.93: registering with nfnetlink.
May 27 13:30:16 rescue kernel: ip_tables: (C) 2000-2006 Netfilter Core Team
May 27 13:30:16 rescue kernel: ClusterIP Version 0.8 loaded successfully
May 27 13:30:16 rescue kernel: arp_tables: (C) 2002 David S. Miller
May 27 13:30:16 rescue kernel: TCP cubic registered
May 27 13:30:16 rescue kernel: NET: Registered protocol family 1
May 27 13:30:16 rescue kernel: NET: Registered protocol family 10
May 27 13:30:16 rescue kernel: lo: Disabled Privacy Extensions
May 27 13:30:16 rescue kernel: ip6_tables: (C) 2000-2006 Netfilter Core Team
May 27 13:30:16 rescue kernel: IPv6 over IPv4 tunneling driver
May 27 13:30:16 rescue kernel: sit0: Disabled Privacy Extensions
May 27 13:30:16 rescue kernel: NET: Registered protocol family 17
May 27 13:30:16 rescue kernel: NET: Registered protocol family 15
May 27 13:30:16 rescue kernel: RPC: Registered udp transport module.
May 27 13:30:16 rescue kernel: RPC: Registered tcp transport module.
May 27 13:30:16 rescue kernel: powernow-k8: Found 1 AMD Athlon(tm) 64 X2 Dual Core Processor 4400+ processors (2 cpu cores) (version 2.20.00)
May 27 13:30:16 rescue kernel: powernow-k8:    0 : fid 0xf (2300 MHz), vid 0x9
May 27 13:30:16 rescue kernel: powernow-k8:    1 : fid 0xe (2200 MHz), vid 0xa
May 27 13:30:16 rescue kernel: powernow-k8:    2 : fid 0xc (2000 MHz), vid 0xc
May 27 13:30:16 rescue kernel: powernow-k8:    3 : fid 0xa (1800 MHz), vid 0xe
May 27 13:30:16 rescue kernel: powernow-k8:    4 : fid 0x2 (1000 MHz), vid 0x12
May 27 13:30:16 rescue kernel: md: Autodetecting RAID arrays.
May 27 13:30:16 rescue kernel: md: Scanned 10 and added 10 devices.
May 27 13:30:16 rescue kernel: md: autorun ...
May 27 13:30:16 rescue kernel: md: considering sdb8 ...
May 27 13:30:16 rescue kernel: md:  adding sdb8 ...
May 27 13:30:16 rescue kernel: md: sdb7 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: sdb6 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: sdb5 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: sdb1 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md:  adding sda8 ...
May 27 13:30:16 rescue kernel: md: sda7 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: sda6 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: sda5 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: sda1 has different UUID to sdb8
May 27 13:30:16 rescue kernel: md: created md8
May 27 13:30:16 rescue kernel: md: bind<sda8>
May 27 13:30:16 rescue kernel: md: bind<sdb8>
May 27 13:30:16 rescue kernel: md: running: <sdb8><sda8>
May 27 13:30:16 rescue kernel: raid1: raid set md8 active with 2 out of 2 mirrors
May 27 13:30:16 rescue kernel: md: considering sdb7 ...
May 27 13:30:16 rescue kernel: md:  adding sdb7 ...
May 27 13:30:16 rescue kernel: md: sdb6 has different UUID to sdb7
May 27 13:30:16 rescue kernel: md: sdb5 has different UUID to sdb7
May 27 13:30:16 rescue kernel: md: sdb1 has different UUID to sdb7
May 27 13:30:16 rescue kernel: md:  adding sda7 ...
May 27 13:30:16 rescue kernel: md: sda6 has different UUID to sdb7
May 27 13:30:16 rescue kernel: md: sda5 has different UUID to sdb7
May 27 13:30:16 rescue kernel: md: sda1 has different UUID to sdb7
May 27 13:30:16 rescue kernel: md: created md7
May 27 13:30:16 rescue kernel: md: bind<sda7>
May 27 13:30:16 rescue kernel: md: bind<sdb7>
May 27 13:30:16 rescue kernel: md: running: <sdb7><sda7>
May 27 13:30:16 rescue kernel: raid1: raid set md7 active with 2 out of 2 mirrors
May 27 13:30:16 rescue kernel: md: considering sdb6 ...
May 27 13:30:16 rescue kernel: md:  adding sdb6 ...
May 27 13:30:16 rescue kernel: md: sdb5 has different UUID to sdb6
May 27 13:30:16 rescue kernel: md: sdb1 has different UUID to sdb6
May 27 13:30:16 rescue kernel: md:  adding sda6 ...
May 27 13:30:16 rescue kernel: md: sda5 has different UUID to sdb6
May 27 13:30:16 rescue kernel: md: sda1 has different UUID to sdb6
May 27 13:30:16 rescue kernel: md: created md6
May 27 13:30:16 rescue kernel: md: bind<sda6>
May 27 13:30:16 rescue kernel: md: bind<sdb6>
May 27 13:30:16 rescue kernel: md: running: <sdb6><sda6>
May 27 13:30:16 rescue kernel: raid1: raid set md6 active with 2 out of 2 mirrors
May 27 13:30:16 rescue kernel: md: considering sdb5 ...
May 27 13:30:16 rescue kernel: md:  adding sdb5 ...
May 27 13:30:16 rescue kernel: md: sdb1 has different UUID to sdb5
May 27 13:30:16 rescue kernel: md:  adding sda5 ...
May 27 13:30:16 rescue kernel: md: sda1 has different UUID to sdb5
May 27 13:30:16 rescue kernel: md: created md5
May 27 13:30:16 rescue kernel: md: bind<sda5>
May 27 13:30:16 rescue kernel: md: bind<sdb5>
May 27 13:30:16 rescue kernel: md: running: <sdb5><sda5>
May 27 13:30:16 rescue kernel: raid1: raid set md5 active with 2 out of 2 mirrors
May 27 13:30:16 rescue kernel: md: considering sdb1 ...
May 27 13:30:16 rescue kernel: md:  adding sdb1 ...
May 27 13:30:16 rescue kernel: md:  adding sda1 ...
May 27 13:30:16 rescue kernel: md: created md1
May 27 13:30:16 rescue kernel: md: bind<sda1>
May 27 13:30:16 rescue kernel: md: bind<sdb1>
May 27 13:30:16 rescue kernel: md: running: <sdb1><sda1>
May 27 13:30:16 rescue kernel: raid1: raid set md1 active with 2 out of 2 mirrors
May 27 13:30:16 rescue kernel: md: ... autorun DONE.
May 27 13:30:16 rescue kernel: RAMDISK: Compressed image found at block 0
May 27 13:30:16 rescue kernel: VFS: Mounted root (ext2 filesystem).
May 27 13:30:16 rescue kernel: Freeing unused kernel memory: 264k freed
May 27 13:30:21 rescue kernel: Clocksource tsc unstable (delta = -63645512 ns)
May 27 13:50:16 rescue -- MARK --
May 27 14:10:16 rescue -- MARK --
May 27 14:30:16 rescue -- MARK --
May 27 14:50:16 rescue -- MARK --
May 27 15:10:16 rescue -- MARK --
May 27 15:30:16 rescue -- MARK --
May 27 15:50:16 rescue -- MARK --



MFG
 

nbkr

Guru
Die /var/log/messages des Rescue Systems ist eigentlich uninteressant. Das ist ja vom Livesystem (es sei denn dein Provider macht das mit dem Rescue System anders als der Rest der Welt).

Du kannst auch vom Rescue System aus ein Backup machen. Mounte die entsprechende Festplatte auf der die Daten liegen (am besten read-only) und kopier dann die Daten von dort weg. Ich schätze mal du machst das Backup über FTP, Samba oder SCP. Das Rescue System hat mit Sicherheit entsprechende Clients.
 
OP
D

djsmoke

Newbie
also raid system seh ich keinen fehler

Code:
Version : 00.90.03
  Creation Time : Wed May 21 09:56:30 2008
     Raid Level : raid1
     Array Size : 987840 (964.69 MiB 1011.55 MB)
    Device Size : 987840 (964.69 MiB 1011.55 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1
    Persistence : Superblock is persistent

    Update Time : Mon May 26 20:58:10 2008
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           UUID : e7b7e6b5:cb1a4f05:c20acfd0:59d5d210
         Events : 0.674

    Number   Major   Minor   RaidDevice State
       0       8        1        0      active sync   /dev/sda1
       1       8       17        1      active sync   /dev/sdb1
 
OP
D

djsmoke

Newbie
meiner meinung liegt es an kernel. wie kann ich in rescue mode kernel neu laden und instalieren
 

homer65

Hacker
Gratuliere zum erfolgreichen Debugging. :D :D
Aber ich hoffe es war dir eine lehrreiche Erfahrung und du machst in Zukunft regelmäßig Backups.
 
Der Provider hat doch sicherlich auch eine Backup-Option im Angebot? Das Geld wars mir wert, denn ich weiß eh nicht, wie ich meine GB-Datenbanken anständig sichern soll. Neuer Server? teurer als die option. Nach Hause? Mit DSL-Lite 378) kein Vergnügen und nicht asutomatisch.

deswegen zahl ich lieber 1-2 EUR mehr im Monat und hab ein 10-Tage-Backup.

Grüße
 
Oben