[es] - Server remote rescue system

Salgeras
Salgeras

Član broj: 21155
Poruke: 180
*.dynamic.sbb.rs.

Profil

^{06.12.2011. u 21:13 - pre 150 meseci}

Pozdrav svima!

Unapred vam se izvinjavam na dugackom postu, trudio sam se da pruzim sto vise info :)

Imam sledecu situaciju: na dedicated serveru koji smo zakupili kod jednog od nemackih ISPova otkazao je jedan od ukupno 2 hard diska u RAID 1. Posto nisam nikako mogao da pridjem masini, morao je hardware restart. Po povratku sistema, pobrisana su sva podesavanja i podaci kreirani dan nakon inicijalnog setupa servera (konkretnije: hard crkao danas, setup servera je bio 16. novembra, izgubljeno je sve od 17. novembra do danas). Problem je prijavljen provajderu i dobili smo pristup njihovom Rescue-systemu. Iz tog rescue-a sada vidim oba diska i kad radim "mount /dev/md2 /mnt" vidim stare podatke.

E sad. Kada sam prvi put restartovao server i logovao se na njega, "fdisk -l" mi je prikazivao samo drugi disk:

Code:

[root@poseidon ~]# fdisk -l

Disk /dev/sdb: 750.2 GB, 750156374016 bytes
64 heads, 32 sectors/track, 715404 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000eb96e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2        2048     2096128   fd  Linux raid autodetect
/dev/sdb2            2049        2560      524288   fd  Linux raid autodetect
/dev/sdb3            2561      715404   729952256   fd  Linux raid autodetect

Disk /dev/md0: 2146 MB, 2146422784 bytes
2 heads, 4 sectors/track, 524029 cylinders
Units = cylinders of 8 * 512 = 4096 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: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/md2: 747.5 GB, 747470970880 bytes
2 heads, 4 sectors/track, 182488030 cylinders
Units = cylinders of 8 * 512 = 4096 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

Po ulasku u Rescue mod, sada su vidljiva oba:

Code:

root@rescue ~ # fdisk -l

Disk /dev/sda: 750.2 GB, 750156374016 bytes
64 heads, 32 sectors/track, 715404 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000de7d4

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1               2        2048     2096128   fd  Linux raid autodetect
/dev/sda2            2049        2560      524288   fd  Linux raid autodetect
/dev/sda3            2561      715404   729952256   fd  Linux raid autodetect

Disk /dev/sdb: 750.2 GB, 750156374016 bytes
64 heads, 32 sectors/track, 715404 cylinders
Units = cylinders of 2048 * 512 = 1048576 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000eb96e

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2        2048     2096128   fd  Linux raid autodetect
/dev/sdb2            2049        2560      524288   fd  Linux raid autodetect
/dev/sdb3            2561      715404   729952256   fd  Linux raid autodetect

Disk /dev/md0: 2146 MB, 2146422784 bytes
2 heads, 4 sectors/track, 524029 cylinders
Units = cylinders of 8 * 512 = 4096 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: 536 MB, 536858624 bytes
2 heads, 4 sectors/track, 131069 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/md2: 747.5 GB, 747470970880 bytes
2 heads, 4 sectors/track, 182488030 cylinders
Units = cylinders of 8 * 512 = 4096 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

Po prvom fdisk-u i dmesg logu zakljucujem da je /dev/sda hdd koji je crkao, a koji je sada dostupan u rescue i ciji su podaci vidljivi. Ono sto ne razumem je - sta dalje sa ovim rescue, kako se ovo koristi za spasavanje podataka? Da li bi neko mogao da mi objasni sta to treba uraditi (ne mora "kako", to mogu i sam :)) da bi, po restart/exit iz rescue sistema svi podaci ostali zabelezeni na /dev/sdb? Trazio sam po googletu, ali tekstovi koje sam nalazio opisuju postupak rada u rescue ukoliko u konfiguraciji zeznete nesto pa server ne moze normalno da se bootuje. Moje pitanje je malo specificnije, nisam uspeo kao takvo da ga nadjem.

Ono sto me buni je to sto oba diska imaju po 3 raid particije, ali samo particije sa /dev/sda se nalaze u raid array-u. Konkretnije:

Code:

root@rescue ~ # cat /proc/mdstat
Personalities : [raid1]
md2 : active raid1 sda3[0]
      729952120 blocks super 1.0 [2/1] [U_]

md1 : active raid1 sda2[0]
      524276 blocks super 1.0 [2/1] [U_]

md0 : active raid1 sda1[0]
      2096116 blocks super 1.0 [2/1] [U_]

Po mom misljenju, s obzirom da je ovo raid 1, podaci bi trebalo da se preslikaju na drugi disk ukoliko njegove particije dodam u raid array, jel tako? Medjutim:

Code:

root@rescue ~ # mdadm --assemble /dev/md2 /dev/sda3 /dev/sdb3
mdadm: /dev/md2 has been started with 1 drive (out of 2).

i ne doda ga u array za md2, tj i dalje stoji da samo sda3 ulazi u md2.

Registered Linux User #460193

Odgovor na temu