Problem bei umpartitionierung

samy-delux

samy-delux

New Member
Hey Leute,

Ich habe auf einem meiner Strato Root-Server versucht die System Partition zu verkleinern. Es handelt sich um einen Software Raid.

md0 ist /boot/
und
md1 ist /

Ich versuche neu zu starten, doch ich bekomme in der seriellen Konsole folgendens:

Code: 
Begin: Mounting root file system... ...
Begin: Running /scripts/local-top ...
Begin: Loading MD modules ...
Success: loaded module raid1.
Domd: md1 stopped.
ne.
Begin: Assembling all MD arrays ...
mdadm: no devicemd: md0 stopped.
s found for /dev/md1
md: bind<sdb1>
md: bind<sda1>
raid1: raid set md0 active with 2 out of 2 mirrors
md: bind<sdb3>0 has been started with 2 drives.

/dev/md1: File md: bind<sda3>
exists
raid1: raid set md1 active with 2 out of 2 mirrors
mdadm: /dev/md/1 has been started with 2 drives.
Failure: failed to assemble all arrays.
Done.
Done.
Begin: Running /scripts/local-premount ...
Done.
mount: Mounting /dev/md1 on /root failed: No such device
Begin: Running /scripts/local-bottom ...
Done.
Done.
Begin: Running /scripts/init-bottom ...
mount: Mounting /root/dev on /dev/.static/dev failed: No such file or directory
Done.
mount: Mounting /sys on /root/sys failed: No such file or directory
mount: Mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init

Aber verstehen tue ich das nicht wirklich!
Es werden ja beide Raids die ich habe ordnungsgemäß gemountet!
Kann mir jemand kurz auf die Sprünge helfen? Die beiden Raids, kann ich im Recovery System wunderbar mounten...

so long,
Samy
 
Last edited by a moderator:
Bitte mal den Output von folgendem herzeigen:

Code: 
fdisk -l /dev/sda /dev/sdb
mdadm -E /dev/sda* /dev/sdb*
 
Code: 
# fdisk -l /dev/sda /dev/sdb

Disk /dev/sda: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1           7       56196   fd  Linux raid autodetect
/dev/sda2               8         138     1052257+  82  Linux swap / Solaris
/dev/sda3             139         760     4996215   fd  Linux raid autodetect

Disk /dev/sdb: 400.0 GB, 400088457216 bytes
255 heads, 63 sectors/track, 48641 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *           1           7       56196   fd  Linux raid autodetect
/dev/sdb2               8         138     1052257+  82  Linux swap / Solaris
/dev/sdb3             139         760     4996215   fd  Linux raid autodetect
und
Code: 
# mdadm -E /dev/sda* /dev/sdb*
/dev/sda1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 304c6a4b:f96c8028:5b986ce4:e45840f9
  Creation Time : Tue Jul 10 13:14:08 2007
     Raid Level : raid1
    Device Size : 56128 (54.82 MiB 57.48 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0

    Update Time : Wed Jul 11 22:36:21 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 9ffe6c8b - correct
         Events : 0.10


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

   0     0       8        1        0      active sync   /dev/sda1
   1     1       8       17        1      active sync   /dev/sdb1
mdadm: cannot open /dev/sda10: No such device or address
mdadm: cannot open /dev/sda11: No such device or address
mdadm: cannot open /dev/sda12: No such device or address
mdadm: cannot open /dev/sda13: No such device or address
mdadm: cannot open /dev/sda14: No such device or address
mdadm: cannot open /dev/sda15: No such device or address
/dev/sda3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : a3b0f5d2:611482ee:44e306cf:83fdc072
  Creation Time : Wed Jul 11 20:31:21 2007
     Raid Level : raid1
    Device Size : 4996096 (4.76 GiB 5.12 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1

    Update Time : Wed Jul 11 22:38:39 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 4482d7e - correct
         Events : 0.6


      Number   Major   Minor   RaidDevice State
this     0       8        3        0      active sync   /dev/sda3

   0     0       8        3        0      active sync   /dev/sda3
   1     1       8       19        1      active sync   /dev/sdb3
mdadm: cannot open /dev/sda4: No such device or address
mdadm: cannot open /dev/sda5: No such device or address
mdadm: cannot open /dev/sda6: No such device or address
mdadm: cannot open /dev/sda7: No such device or address
mdadm: cannot open /dev/sda8: No such device or address
mdadm: cannot open /dev/sda9: No such device or address
/dev/sdb1:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : 304c6a4b:f96c8028:5b986ce4:e45840f9
  Creation Time : Tue Jul 10 13:14:08 2007
     Raid Level : raid1
    Device Size : 56128 (54.82 MiB 57.48 MB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 0

    Update Time : Wed Jul 11 22:36:21 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 9ffe6c9d - correct
         Events : 0.10


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

   0     0       8        1        0      active sync   /dev/sda1
   1     1       8       17        1      active sync   /dev/sdb1
mdadm: cannot open /dev/sdb10: No such device or address
mdadm: cannot open /dev/sdb11: No such device or address
mdadm: cannot open /dev/sdb12: No such device or address
mdadm: cannot open /dev/sdb13: No such device or address
mdadm: cannot open /dev/sdb14: No such device or address
mdadm: cannot open /dev/sdb15: No such device or address
/dev/sdb3:
          Magic : a92b4efc
        Version : 00.90.00
           UUID : a3b0f5d2:611482ee:44e306cf:83fdc072
  Creation Time : Wed Jul 11 20:31:21 2007
     Raid Level : raid1
    Device Size : 4996096 (4.76 GiB 5.12 GB)
   Raid Devices : 2
  Total Devices : 2
Preferred Minor : 1

    Update Time : Wed Jul 11 22:38:39 2007
          State : clean
 Active Devices : 2
Working Devices : 2
 Failed Devices : 0
  Spare Devices : 0
       Checksum : 4482d90 - correct
         Events : 0.6


      Number   Major   Minor   RaidDevice State
this     1       8       19        1      active sync   /dev/sdb3

   0     0       8        3        0      active sync   /dev/sda3
   1     1       8       19        1      active sync   /dev/sdb3
mdadm: cannot open /dev/sdb4: No such device or address
mdadm: cannot open /dev/sdb5: No such device or address
mdadm: cannot open /dev/sdb6: No such device or address
mdadm: cannot open /dev/sdb7: No such device or address
mdadm: cannot open /dev/sdb8: No such device or address
mdadm: cannot open /dev/sdb9: No such device or address

Ich hoffe das hilft!
 
Nochmal der "Beweis" das die Filesystemem ok sind:

Code: 
# fsck -f /dev/md1 
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/: 23443/524288 files (0.1% non-contiguous), 97785/1048576 blocks

# fsck -f /dev/md0 
fsck 1.37 (21-Mar-2005)
e2fsck 1.37 (21-Mar-2005)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
/boot: 36/14056 files (5.6% non-contiguous), 6293/56128 blocks
root@h1314632:~#
 
Bei RAIDs ist /proc/mdstat interessanter als fsck.
Die Superblocks sehen soweit eigentlich gut aus.
 
Dann hier die Ausgabe davon:

Code: 
# cat /proc/mdstat 
Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5] [raid4] 
md1 : active raid1 sdb3[1] sda3[0]
      4996096 blocks [2/2] [UU]
      
md0 : active raid1 sdb1[1] sda1[0]
      56128 blocks [2/2] [UU]
      
unused devices: <none>

Alle Ausgaben stammen überigens vom gebooteten Rettungssystem!
 
Guten Morgen

Wie hast du die MD Disks in der fstab eingebunden? Stimmt da alles oder steht da aus versehen noch die Original Partition zum mounten, also nicht /dev/md0 usw.?

Beispiel:
Ist
/dev/sda1 ...

Soll
/dev/md0 ...
 
Last edited by a moderator:
You must log in or register to reply here.
Back
Top