Dotaz: opnSUSE 11.1 po instalaci na RAID1 zhavaruje pri bootovani

[Petr]

Pokousim se nainstalovat opensuse 11.1 na RAID1

md0 RAID1 swap
md1 RAID1 /

Boot po instalaci skonci v tomto bode:

md: md1:raid array is not clean -- starting backround c
raid1: raid set md1 active with 2 out of 2 mirrors
md1: bitmap initialized from dist: read 30/30 pages, set 700520 bits
created bitmap (465 pages) for md1
mdadm: /dev/md/1 hashem started with 2 drives
Trying normal resume from /dev/md0
resume device /dev/md0 not found (ignor
Trying normal resume from /dev/md0
resume device /dev/md0 not found (ignor
Waiting for device /dev/md1 to appear: ok
invalid root file system -- exiting to /bin/sh
$

Odpovědi

[Dušan Hokův]

Swap nedelejte jako raid.

[Petr]

Swap na RAIDu nema s vyse uvednym zadnou souvislost.

[Michal Kubeček]

No, úplně jistý bych si tím nebyl, protože podle těch hlášek jsou problémy jen s /dev/md0. S parametrem noresume to taky nenabootuje?

[Petr]

Ani s noresume nejde nabootovat. Zadna zmena.

[Michal Kubeček]

Když nabootujete rescue system z instalačního DVD, tak se vám ta pole složí dobře? Jak jsou konkrétně sestavena?

[Petr]

server3:~ # mdadm --detail /dev/md0
/dev/md0:
        Version : 1.00
  Creation Time : Sun Dec 21 23:59:58 2008
     Raid Level : raid1
     Array Size : 2104500 (2.01 GiB 2.16 GB)
  Used Dev Size : 2104500 (2.01 GiB 2.16 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Mon Dec 22 00:17:09 2008
          State : active
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

           Name : linux:0
           UUID : 76a8e1d7:67c5eee5:38d2763a:35e65bc2
         Events : 4

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





server3:~ # mdadm --detail /dev/md1
/dev/md1:
        Version : 1.00
  Creation Time : Sun Dec 21 23:59:59 2008
     Raid Level : raid1
     Array Size : 974647348 (929.50 GiB 998.04 GB)
  Used Dev Size : 1949294696 (1858.99 GiB 1996.08 GB)
   Raid Devices : 2
  Total Devices : 2
    Persistence : Superblock is persistent

  Intent Bitmap : Internal

    Update Time : Mon Dec 22 00:18:14 2008
          State : active, resyncing
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0

 Rebuild Status : 6% complete

           Name : linux:1
           UUID : 34d671c8:c0aa1484:bc9d66af:5e963bbd
         Events : 5

    Number   Major   Minor   RaidDevice State
       0       8        2        0      active sync   /dev/sda2
       1       8       18        1      active sync   /dev/sdb2





server3:~ #  cat /proc/mdstat
Personalities : [raid1] [raid0] [raid6] [raid5] [raid4]
md0 : active  raid1 sda1[0] sdb1[1]
      2104500 blocks super 1.0 [2/2] [UU]
      bitmap: 0/9 pages [0KB], 128KB chunk

md1 : active raid1 sda2[0] sdb2[1]
      974647348 blocks super 1.0 [2/2] [UU]
      [=>...................]  resync =  6.3% (61884032/974647348) finish=234.8min speed=64774K/sec
      bitmap: 436/465 pages [1744KB], 1024KB chunk

unused devices: <none>






server3:~ # fdisk -l

Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00041969

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           2         263     2104515   fd  Linux raid autodetect
/dev/sda2             264      121601   974647485   fd  Linux raid autodetect

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00052e3b

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1               2         263     2104515   fd  Linux raid autodetect
/dev/sdb2             264      121601   974647485   fd  Linux raid autodetect

Disk /dev/sdc: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x35125939

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

Disk /dev/md1: 998.0 GB, 998038884352 bytes
2 heads, 4 sectors/track, 243661837 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

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

Disk /dev/md0: 2155 MB, 2155008000 bytes
2 heads, 4 sectors/track, 526125 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000

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

[linuxik]

Ahoj,

To vypada ze je problem s filesystemem na md1, zkus znovu nabootovat z CD a pripojit ho nekam do adresare `mount /dev/md1  /mnt/nekam`  a podivej se co obsahuje.

 

[Petr]

Souborovy system na md1 vypada dobre.

 # e2fsck /dev/md1
e2fsck 1.41.1 (01-Sep-2008)
/dev/md1: clean, 56103/60915712 files, 4159180/243661837 blocks

 

 

 # dumpe2fs /dev/md1                                                    
dumpe2fs 1.41.1 (01-Sep-2008)                                                  
Filesystem volume name:   <none>                                               
Last mounted on:          <not available>                                      
Filesystem UUID:          da5cdf7f-025e-4c48-8493-45a4f2c36602                 
Filesystem magic number:  0xEF53                                               
Filesystem revision #:    1 (dynamic)                                          
Filesystem features:      has_journal ext_attr resize_inode dir_index filetype sparse_super large_file                                                         
Filesystem flags:         signed_directory_hash                                
Default mount options:    (none)                                               
Filesystem state:         clean                                                
Errors behavior:          Continue                                             
Filesystem OS type:       Linux                                                
Inode count:              60915712                                             
Block count:              243661837                                            
Reserved block count:     12183091                                             
Free blocks:              239502657                                            
Free inodes:              60859609
First block:              0
Block size:               4096
Fragment size:            4096
Reserved GDT blocks:      965
Blocks per group:         32768
Fragments per group:      32768
Inodes per group:         8192
Inode blocks per group:   512
Filesystem created:       Sun Dec 21 23:00:01 2008
Last mount time:          Mon Dec 22 00:30:06 2008
Last write time:          Mon Dec 22 00:33:11 2008
Mount count:              3
Maximum mount count:      -1
Last checked:             Sun Dec 21 23:00:01 2008
Check interval:           0 (<none>)
Reserved blocks uid:      0 (user root)
Reserved blocks gid:      0 (group root)
First inode:              11
Inode size:               256
Required extra isize:     28
Desired extra isize:      28
Journal inode:            8
Default directory hash:   half_md4
Directory Hash Seed:      671f60a8-0a11-417e-a548-99caad3271f4
Journal backup:           inode blocks
Journal size:             128M

[linuxik]

No, ted me jeste napadlo, co mas  v grubu  jako root device  zkus tam dopsat  (klavesa e) root=/dev/md1

[Petr]

To tam mam.

# Modified by YaST2. Last modification on Ne pro 21 16:22:46 UTC 2008
default 0
timeout 8
gfxmenu (hd0,1)/boot/message
##YaST - activate

###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 11.1 - 2.6.27.7-9
    root (hd0,1)
    kernel /boot/vmlinuz-2.6.27.7-9-pae root=/dev/md1 resume=/dev/md0 splash=silent showopts vga=0x317
    initrd /boot/initrd-2.6.27.7-9-pae

[linuxik]

Tak to uz zbyva snad jen to ze by jsi v initrd nemel podporu pro raid, zkus ho znovu vytvorit a pridat tam potrebne moduly. Uz si nepamatuji jaky je na to v opensuse prikaz mkinitrd nebo tak nejak, ale bude to trochu slozitejsi. Nabootuj z cd udelej adresar treba /mnt/md1, pripoj do nej  /dev/md1 a potom pomoc mount -o  bind pripoj adresare /dev /proc a /sys do adresaru v /mnt/md1 (mount -o bind /proc /mnt/md1/proc) a nakonec udelej chroot /mnt/md1 . Tim  se dostanes do systemu na md1 a muzes si zacit hrat s initrd.

ps. K cemu potrebujes pae? Mas vic jak 3GB RAM na 32bit  masine?

[Petr]

To take nepomohlo. V initrd podpora pro raid je.

 

 

# mkinitrd -f -k -v

Kernel image:   /boot/vmlinuz-2.6.27.7-9-pae
Initrd image:   /boot/initrd-2.6.27.7-9-pae
Root device:    /dev/md1 (mounted on / as ext3)
Resume device:  /dev/md0
[BLOCK] /dev/sda -> pata_via
[BLOCK] /dev/sda -> sd_mod
[BLOCK] /dev/sdb -> pata_via
[BLOCK] /dev/sdb -> sd_mod
[MODULES]       02-start.sh: processor thermal pata_via ata_generic via82cxxx ide_pci_generic fan jbd ext3 raid1 edd
[MODULES]       03-storage.sh: ext3
[MODULES]       11-block.sh: pata_via sd_mod
[MODULES]       11-usb.sh: usbcore
[MODULES]       11-usb.sh: ohci_hcd
[MODULES]       11-usb.sh: uhci-hcd
[MODULES]       11-usb.sh: ehci_hcd
[MODULES]       11-usb.sh: usbhid
[MODULES]       51-md.sh: raid0
[MODULES]       51-md.sh: raid1
[MODULES]       51-md.sh: raid456
Kernel Modules: hwmon thermal_sys processor thermal dock scsi_mod libata pata_via ata_generic ide-core via82cxxx ide-pci-generic fan jbd mbcache ext3 raid1 edd crc-t10dif sd_mod usbcore ohci-hcd uhci-hcd ehci-hcd ff-memless hid usbhid raid0 xor async_tx async_memcpy async_xor raid456
[MOUNT] Root:   /dev/md1
Features:       block usb md resume.userspace resume.kernel
Bootsplash:     openSUSE (1024x768)
Shared libs:    lib/ld-2.9.so lib/libacl.so.1.1.0 lib/libattr.so.1.1.0 lib/libblkid.so.1.0 lib/libc-2.9.so lib/libcom_err.so.2.1 lib/libdl-2.9.so lib/libe2p.so.2.3 lib/libext2fs.so.2.4 lib/libgcc_s.so.1 lib/libgcrypt.so.11.4.4 lib/libgpg-error.so.0.4.0 lib/liblzo2.so.2.0.0 lib/libncurses.so.5.6 lib/libpthread-2.9.so lib/libreadline.so.5.2 lib/librt-2.9.so lib/libselinux.so.1 lib/libsepol.so.1 lib/libutil-2.9.so lib/libuuid.so.1.2 lib/libvolume_id.so.1.0.1 lib/libz.so.1.2.3 usr/lib/libdirect-1.2.so.0.3.0 usr/lib/libdirectfb-1.2.so.0.3.0 usr/lib/libfusion-1.2.so.0.3.0 usr/lib/libglib-2.0.so.0.1800.2 usr/lib/libpcre.so.0.0.1 usr/lib/libsplashy.so.1.0.0 usr/lib/libsplashycnf.so.1.0.0 lib/libnss_dns-2.9.so lib/libnss_dns.so.2 lib/libnss_files-2.9.so lib/libnss_files.so.2 lib/libgcc_s.so.1
23919 blocks

[Zdeněk Štěpánek]

Zdravim

Swap na RAID-1 smysl ma, kdyz to nemas a odejde ti disk, ztratis pulku swapu a bezici programy muzou jit do kytek.

Ja bych asi nejprve po vytvoreni pole pockal az se sesynchronizuje a az to bude hotovy tak formatoval. Zrejme na to necekas a jak se to formatuje a restartuje a zase restartuje tak je to pole v dost nedefinovatelnym stavu.

Jinak ty hlasky co pises je pokus o resume ze suspend-to-disk, pridej kernelovej parametr noresume, pokud to nechces pouzivat, jinak ty hlasky ignoruj. Akorat mi neni jasny proc jsou tam dvakrat. Relevantni k popisovane chybe je prvnich 5 a posledni 2 radky.

Zdenek

[R]

Vobec netreba cakat na synchronizaciu pola. Hned po vytvoreni pola sa s nim da normalne robit, tzn. vytvorit filesystem. A ked sa to medzitym restartuje, tak nebude nic v nedefinovanom stave. Jednoducho sa spusti synchronizacia od zaciatku, ale vsetko normalne bezi. Inak by to nebol RAID, ale nejaky shit, kde by si nikto data nedal.

[arno3t]

Vsiml jsem si, ze disky jsou docela velke. Nemuze mit system problem s nactenim initrd? Mel jsem nedavno podobny problem na HPw9400 (asi) s 300MB disky a byl to urcite problem BIOS a grubu. Zkuste dat adresar /boot na misto swapu a samozrejme upravit podle toho grub i fstab. Nevnucuji vam toto reseni, samozrejme cokoli, kde adresar /boot je na prvnich cylindrech disku by mohlo stacit.

[arno3t]

Samozrejme misto 300MB melo byt 300GB

[Petr]

Zkousel jsem konfiguraci zmenit takhle:

sda1 swap

sdb1 /boot

md1 (sda2,sdb2) /

Ale to nijak nepomohlo

 

[Petr]

Teprve ted jsem si vsiml, ze kdyz za

.

.

invalid root file system -- exiting to /bin/sh
$

 

napisu exit, dam enter tak bootovani pokracuje.

[Petr]

Ví někdo co s tím?

[Zdeněk Štěpánek]

blbej zapis v /etc/fstab?

Zdenek

[Petr]

Takhle vypada /etc/fstab

/dev/md1             /                    ext3       acl,user_xattr        1 1
proc                 /proc                proc       defaults              0 0
sysfs                /sys                 sysfs      noauto                0 0
debugfs              /sys/kernel/debug    debugfs    noauto                0 0
usbfs                /proc/bus/usb        usbfs      noauto                0 0
devpts               /dev/pts             devpts     mode=0620,gid=5       0 0
/dev/md0             swap                 swap       defaults              0 0

[Zdeněk Štěpánek]

Zmenil bych to takhle:

/dev/md1 / ext3 defaults,acl,user_xattr 1 1

Jeste muzes zkusit konec prepsat na 0 0, pak se filesystem nebude kontrolovat pri startu, treba to pomuze odhalit pricinu problemu. Potom doporucuju vratit zpet na 1 1.

Sice se ti system snazi sestavit pole sam od sebe, ale vetsinou jsem videl ze je potreba jadru predat parametry: "md=0,/dev/sda1,/dev/sdb1 md=1,/dev/sda2,/dev/sdb2". Alespon v archu to tak musim napsat.

Zdenek

[Petr]

Vyzkouseno a bohuzel vsechno pri starem.

[Petr]

Vypis logu po nabootovani.

Boot logging started on /dev/tty1(/dev/console) at Mon Dec 22 19:53:43 2008

mdadm: /dev/md/1 has been started with 2 drives.
Trying manual resume from /dev/md0
resume device /dev/md0 not found (ignoring)
Trying manual resume from /dev/md0
resume device /dev/md0 not found (ignoring)
Waiting for device /dev/md1 to appear:  ok
invalid root filesystem -- exiting to /bin/sh
$
$
$
$
$ exit
exit
Mounting root /dev/md1

Boot logging started on /dev/tty1(/dev/console (deleted)) at Mon Dec 22 19:54:04 2008

done
Starting udevd: done
Loading drivers, configuring devices: done
Loading required kernel modules
doneActivating swap-devices in /etc/fstab...
failedChecking root file system...
fsck 1.41.1 (01-Sep-2008)
/dev/md1: clean, 131929/60915712 files, 4692702/243661837 blocks
doneSetting up the hardware clockdone
Activating device mapper...
done
Starting MD Raid mdadm: /dev/md/0 has been started with 2 drives.
failed
Checking file systems...
fsck 1.41.1 (01-Sep-2008)
donedone
Mounting local file systems...
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
nothing was mounted
doneLoading fuse module done

 

Problem se swapem

 

# cat /proc/mdstat
Personalities : [raid1] [raid0] [raid6] [raid5] [raid4]
md0 : active (auto-read-only) raid1 sda1[0] sdb1[1]
      2112504 blocks super 1.0 [2/2] [UU]
      bitmap: 0/9 pages [0KB], 128KB chunk

md1 : active raid1 sda2[0] sdb2[1]
      974647348 blocks super 1.0 [2/2] [UU]
      bitmap: 320/465 pages [1280KB], 1024KB chunk

unused devices: <none

# swapon -s
Filename                                Type            Size    Used    Priority
/dev/md0                                partition       2112496 0       -1

 

 

[Petr]

Jeste jednou o neco delsi log. Nevi nekdo o co jde?

<3>Unable to find swap-space signature
<6>EXT3 FS on md1, internal journal
<6>device-mapper: uevent: version 1.0.3
<6>device-mapper: ioctl: 4.14.0-ioctl (2008-04-23) initialised: dm-devel@redhat.com
<6>md: md0 stopped.
<6>md: bind<sdb1>
<6>md: bind<sda1>
<6>raid1: raid set md0 active with 2 out of 2 mirrors
<6>md0: bitmap initialized from disk: read 1/1 pages, set 0 bits
<6>created bitmap (9 pages) for device md0
<6>loop: module loaded
<4>fuse init (API version 7.9)
Kernel logging (ksyslog) stopped.
Kernel log daemon terminating.

Boot logging started on /dev/tty1(/dev/console) at Tue Dec 23 09:49:47 2008

mdadm: /dev/md/1 has been started with 2 drives.
Trying manual resume from /dev/md0
resume device /dev/md0 not found (ignoring)
Trying manual resume from /dev/md0
resume device /dev/md0 not found (ignoring)
Waiting for device /dev/md1 to appear:  ok
invalid root filesystem -- exiting to /bin/sh
$
$ exit
exit
Mounting root /dev/md1

Boot logging started on /dev/tty1(/dev/console (deleted)) at Tue Dec 23 09:51:15 2008

done
Starting udevd: done
Loading drivers, configuring devices: done
Loading required kernel modules
doneActivating swap-devices in /etc/fstab...
failedChecking root file system...
fsck 1.41.1 (01-Sep-2008)
/dev/md1: clean, 131936/60915712 files, 4692702/243661837 blocks
doneSetting up the hardware clockdone
Activating device mapper...
done
Starting MD Raid mdadm: /dev/md/0 has been started with 2 drives.
failed
Checking file systems...
fsck 1.41.1 (01-Sep-2008)
donedone
Mounting local file systems...
/proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
nothing was mounted
doneLoading fuse module done
Mounting fuse control filesystemdone
<notice>killproc: kill(614,29)
Creating /var/log/boot.msg
doneSetting current sysctl status from /etc/sysctl.conf
net.ipv4.icmp_echo_ignore_broadcasts = 1
net.ipv4.conf.all.rp_filter = 1
fs.inotify.max_user_watches = 65536
net.ipv4.conf.default.promote_secondaries = 1
net.ipv4.conf.all.promote_secondaries = 1
done
Activating remaining swap-devices in /etc/fstab...
doneMounting securityfs on /sys/kernel/security done
Loading AppArmor profiles Enabling syn flood protectiondone
Disabling IP forwardingdone
done
Setting up hostname 'server3'done
Setting up loopback interface     lo       
    lo        IP address: 127.0.0.1/8  
              IP address: 127.0.0.2/8  
done
done
System Boot Control: The system has been set up
Failed features: boot.md
Skipped features: boot.cycle
System Boot Control: Running /etc/init.d/boot.local

[Petr]

Jak odstranim toto?

<3>Unable to find swap-space signature

[linuxik]

Tak to vim prikaz mkswap

[Petr]

To sice pomuze, ale po dalsim nabootovani je to znovu v puvodnim stavu.

[Petr]

Problem stale nevyresen, ale zde jsem nasel neco podobneho.

bugzilla.novell.com/show_bug.cgi?id=445490

[trolo_vk]

zdravim, viem ze je to stare vlakno ale mam ten isty problem, po restarte som mal vzdy ten swap v raide1 ako auto-read, a tak som googlil az som nasiel toto: http://linux.derkeiler.com/Newsgroups/comp.os.linux.misc/2007-11/msg00009.html

ten prikaz: Try "mdadm --readwrite /dev/md1" mi od zakladov zmenil moj dosavadny zivot :))))

Snad to niekomu pomoze, cafte ;)