ARCHIV

Ahoj

Snažím se udělat RAID1 na již běžícím systému, postupuji podle návodu zde: http://www.howtoforge.com/how-to-set-up ... untu-10.04



ale poté co dám instalaci grub na /dev/sda a /dev/sdb a restartuji tak již system nenajede. Zkoušel jsem rady z komentařu pod tím návodem ale nic nepomohlo a už nevím jak dál s tím tak prosím o radu.

Po restartu

error: file "/boot/grub/i386-pc/raid.mod" not found
error: file "/boot/grub/i386-pc/mdraid.mod" not found
Loading Linux....
error: disk "md/0" not found
Loading initial....
Error you need to load the kernel first

Press any key to continue


Zkoušel jsem kombinovat i s navodem zde http://www.pc-pingan.com/index.php?mod= ... ew&id=4451

Napadá mě už snad že by mohla být chyba při vytvoření md0 když mě to upozornuje tímto a dám yes a vytvorit i pres to:

Note: this array has metadata at the start and
may not be suitable as a boot device. If you plan to
store '/boot' on this device please ensure that
your boot-loader understands md/v1.x metadata, or use
--metadata=0.90

Ale moc nechapu co to znamena a jak to vyřešit.


Disk ze kterého načíta Ubuntu je:

Disk /dev/sda: 10.7 GB, 10737418240 bytes
255 heads, 63 sectors/track, 1305 cylinders, total 20971520 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: 0x00023f2d

Device Boot Start End Blocks Id System
/dev/sda1 * 2048 18874367 9436160 83 Linux
/dev/sda2 18876416 20969471 1046528 82 Linux swap / Solaris

Dále přikladam jak mám nakonfigurované soubory:

# definitions of existing MD arrays

# This file was auto-generated on Mon, 28 Jan 2013 09:58:04 -0800
# by mkconf $Id$
ARRAY /dev/md/0 metadata=1.2 UUID=25aade92:6d966ce3:a4149ec3:e6178c63 name=ubuntu:0
ARRAY /dev/md/1 metadata=1.2 UUID=a8736d56:03c40e70:1b0acddc:bb433f78 name=ubuntu:1

fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
/dev/md0 / ext4 errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
/dev/md1 none swap sw 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec,utf8 0 0

mtab

/dev/md0 / ext4 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
udev /dev devtmpfs rw,mode=0755 0 0
devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
tmpfs /run tmpfs rw,noexec,nosuid,size=10%,mode=0755 0 0
none /run/lock tmpfs rw,noexec,nosuid,nodev,size=5242880 0 0
none /run/shm tmpfs rw,nosuid,nodev 0 0
none /run/user tmpfs rw,noexec,nosuid,nodev,size=104857600,mode=0755 0 0
vmware-vmblock /run/vmblock-fuse fuse.vmware-vmblock rw,nosuid,nodev,default_permissions,allow_other 0 0
gvfsd-fuse /run/user/honza/gvfs fuse.gvfsd-fuse rw,nosuid,nodev,user=honza 0 0
/dev/md0 /mnt/md0 ext4 rw 0 0
gvfsd-fuse /run/user/root/gvfs fuse.gvfsd-fuse rw,nosuid,nodev 0 0

a

#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'Ubuntu, with Linux 3.0.0-17-generic' --class ubuntu --class gnu-linux --class gnu --class os {
insmod raid
insmod mdraid
insmod part_msdos
insmod ext2
set root='(md/0)'
echo 'Loading Linux 3.0.0-17-generic ...'
linux /vmlinuz-3.0.0-17-generic root=/dev/md0 ro quiet
echo 'Loading initial ramdisk ...'
initrd /initrd.img-3.0.0-17-generic
}

a nakonec jsem ještě upravil: /etc/default/grub

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
GRUB_DISABLE_LINUX_UUID=true