rescue:/# cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda3[0] sdb3[1]
730202368 blocks [2/2] [UU]
md1 : active raid1 sda2[0] sdb2[1]
264960 blocks [2/2] [UU]
md0 : active raid1 sda1[0] sdb1[1]
2102464 blocks [2/2] [UU]
unused devices: <none>
rescue:/# chrooten
bash: chrooten: command not found
rescue:/# fdisk -l
Disk /dev/sda: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002a544
Device Boot Start End Blocks Id System
/dev/sda1 3906 4209029 2102562 fd Linux raid autodetect
/dev/sda2 4209030 4739174 265072+ fd Linux raid autodetect
/dev/sda3 4739175 1465144064 730202445 fd Linux raid autodetect
Disk /dev/sdb: 750.2 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders, total 1465149168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0002a544
Device Boot Start End Blocks Id System
/dev/sdb1 3906 4209029 2102562 fd Linux raid autodetect
/dev/sdb2 4209030 4739174 265072+ fd Linux raid autodetect
/dev/sdb3 4739175 1465144064 730202445 fd Linux raid autodetect
Disk /dev/md0: 2152 MB, 2152923136 bytes
2 heads, 4 sectors/track, 525616 cylinders, total 4204928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 271 MB, 271319040 bytes
2 heads, 4 sectors/track, 66240 cylinders, total 529920 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
Disk /dev/md2: 747.7 GB, 747727224832 bytes
2 heads, 4 sectors/track, 182550592 cylinders, total 1460404736 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md2 doesn't contain a valid partition table
Disk doesn't contain a valid partition table
Disk doesn't contain a valid partition table
Hallo, Rootserver startet nach Reboot nicht mehr. Wäre dankbar für euren Rat!
Re: Disk doesn't contain a valid partition table
md1 scheint /boot zu sein, welches aber angeblich eine leere Partitionstabelle enthaelt. Kannst du es als ext2 mounten? Das gilt kann man auch mal fuer md2 probieren, da sollte entweder / drauf sein oder ein LVM. Vielleicht wurde versehentlich fdisk auf md1 angewendet; das wuerde man in der History der Shell sehen, vermutlich der von root.
Ausserdem ist im BIOS die Boot-Reihenfolge zu kontrollieren. Wer schreibt die Meldung (Screenshot!)?
Gruss Cae
Ausserdem ist im BIOS die Boot-Reihenfolge zu kontrollieren. Wer schreibt die Meldung (Screenshot!)?
Gruss Cae
If universal surveillance were the answer, lots of us would have moved to the former East Germany. If surveillance cameras were the answer, camera-happy London, with something like 500,000 of them at a cost of $700 million, would be the safest city on the planet.
—Bruce Schneier
Re: Disk doesn't contain a valid partition table
Beim Versuch ext2 zu mounten bekomme ich folgenden Meldungen:
root@rescue /mnt # mount -t ext2 /dev/md1 /mnt/rescue
mount: /dev/md1 already mounted or /mnt/rescue busy
mount: according to mtab, /dev/md2 is already mounted on /mnt/rescue
root@rescue /mnt # mount -t ext2 /dev/md2 /mnt/rescue
mount: /dev/md2 already mounted or /mnt/rescue busy
mount: according to mtab, /dev/md2 is already mounted on /mnt/rescue
Sieht tatsächlich so aus das fdisk auf md1 angewendet worden ist.
rescue:/# cat /etc/fstab
proc /proc proc defaults 0 0
none /dev/pts devpts gid=5,mode=620 0 0
/dev/md0 none swap sw 0 0
/dev/md1 /boot ext3 defaults 0 0
/dev/md2 / ext3 errors=remount-ro,usrquota,grpquota 0 1
/var/log/ispconfig/httpd/domain_-.com /var/www/clients/client0/web37/log none b ind,nobootwait 0 0
title Debian GNU/Linux, kernel 2.6.32-5-amd64
root (hd0,1)
kernel /vmlinuz-2.6.32-5-amd64 root=/dev/md2 ro
initrd /initrd.img-2.6.32-5-amd64
title Debian GNU/Linux, kernel 2.6.32-5-amd64 (single-user mode)
root (hd0,1)
kernel /vmlinuz-2.6.32-5-amd64 root=/dev/md2 ro single
initrd /initrd.img-2.6.32-5-amd64
title Debian GNU/Linux, kernel 2.6.26-2-amd64
root (hd0,1)
kernel /vmlinuz-2.6.26-2-amd64 root=/dev/md2 ro
initrd /initrd.img-2.6.26-2-amd64
title Debian GNU/Linux, kernel 2.6.26-2-amd64 (single-user mode)
root (hd0,1)
kernel /vmlinuz-2.6.26-2-amd64 root=/dev/md2 ro single
initrd /initrd.img-2.6.26-2-amd64
Re: Disk doesn't contain a valid partition table
If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE