View previous topic :: View next topic |
Author |
Message |
Thiemo Tux's lil' helper
Joined: 20 Nov 2002 Posts: 138
|
Posted: Thu Apr 06, 2017 9:24 am Post subject: [abandoned] I am stuck with installation of softraid/lvm at |
|
|
Hi all
I am trying to install a KDE desktop system. I have an ASUS M4N78 PRO mainboard equipped with 2 IDE disks on sda and sdb and 2 SATA disks on sdc and sdd. On the latter pair I setup software raid 1 (mirror) and on top of it lvm to install Gentoo. The former pair is also in software raid. I did not use Gentoo installation media to boot but first Kubuntu (crashed up to a couple of times a day) and now I am on Debian Jessie (its installation provided set up for software raid and lvm). I'll try to be precise without giving too much detail. I am afraid though some code blocks will be quite lengthy. Is there a way to fold those?
Code: | root@antec-debian:~# cat /proc/mdstat
Personalities : [raid1]
md3 : active raid1 sdc1[0] sdd1[1]
488253440 blocks super 1.2 [2/2] [UU]
bitmap: 2/4 pages [8KB], 65536KB chunk
md2 : active (auto-read-only) raid1 sda2[0] sdb2[1]
243566912 blocks super 1.2 [2/2] [UU]
bitmap: 0/2 pages [0KB], 65536KB chunk
md1 : active (auto-read-only) raid1 sda1[0]
497344 blocks super 1.2 [2/1] [U_] |
Please just ignore the degraded state of md1. I do not care right now.
Code: | root@antec-debian:~# fdisk -l
Disk /dev/sdc: 465.8 GiB, 500107862016 bytes, 976773168 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
Disklabel type: dos
Disk identifier: 0xc0b4d476
Device Boot Start End Sectors Size Id Type
/dev/sdc1 * 2048 976771071 976769024 465.8G fd Linux raid autodetect
Disk /dev/sdd: 465.8 GiB, 500107862016 bytes, 976773168 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
Disklabel type: dos
Disk identifier: 0xa3676d5e
Device Boot Start End Sectors Size Id Type
/dev/sdd1 2048 976771071 976769024 465.8G fd Linux raid autodetect
Disk /dev/sdb: 232.9 GiB, 250059350016 bytes, 488397168 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
Disklabel type: dos
Disk identifier: 0x680b680b
Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 63 996029 995967 486.3M fd Linux raid autodetect
/dev/sdb2 996030 488392064 487396035 232.4G fd Linux raid autodetect
Disk /dev/sda: 232.9 GiB, 250059350016 bytes, 488397168 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
Disklabel type: dos
Disk identifier: 0x680b680d
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 997375 995328 486M fd Linux raid autodetect
/dev/sda2 997376 488397167 487399792 232.4G fd Linux raid autodetect
Disk /dev/md1: 485.7 MiB, 509280256 bytes, 994688 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
Disklabel type: dos
Disk identifier: 0x634cc99c
Device Boot Start End Sectors Size Id Type
/dev/md1p1 * 2048 993279 991232 484M 83 Linux
Disk /dev/md2: 232.3 GiB, 249412517888 bytes, 487133824 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 /dev/md3: 465.7 GiB, 499971522560 bytes, 976506880 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 /dev/mapper/vg_raid-root_1: 18.6 GiB, 19998441472 bytes, 39059456 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 /dev/mapper/vg_raid-swap: 22.4 GiB, 23999807488 bytes, 46874624 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 /dev/mapper/vg_raid-boot: 976 MiB, 1023410176 bytes, 1998848 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 /dev/mapper/vg_raid-home: 186.3 GiB, 199996997632 bytes, 390619136 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 /dev/mapper/vg_raid-root_2: 37.3 GiB, 39996882944 bytes, 78118912 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 /dev/mapper/vg_raid-root_3: 18.6 GiB, 19998441472 bytes, 39059456 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 /dev/mapper/vg_raid-var_1: 37.3 GiB, 39996882944 bytes, 78118912 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 /dev/mapper/vg_raid-var_2: 37.3 GiB, 39996882944 bytes, 78118912 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 /dev/mapper/vg_raid-var_3: 37.3 GiB, 39996882944 bytes, 78118912 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 |
[device mounting cut as this is now done by fstab of debian installation]
Code: | root@antec-debian:~# df -T
Dateisystem Typ 1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf
/dev/dm-0 ext4 19092180 3686484 14412828 21% /
udev devtmpfs 10240 0 10240 0% /dev
tmpfs tmpfs 2466484 9344 2457140 1% /run
tmpfs tmpfs 6166208 84 6166124 1% /dev/shm
tmpfs tmpfs 5120 4 5116 1% /run/lock
tmpfs tmpfs 6166208 0 6166208 0% /sys/fs/cgroup
/dev/mapper/vg_raid-var_1 ext4 38315504 739232 35606916 3% /var
/dev/mapper/vg_raid-root_2 ext4 38315504 23392684 12953464 65% /mnt/gentoo
/dev/mapper/vg_raid-home ext4 192112220 90473004 100646288 48% /home
/dev/mapper/vg_raid-boot ext4 967320 75648 825320 9% /boot
/dev/mapper/vg_raid-root_3 ext4 19092180 44996 18054316 1% /mnt/root_3
/dev/mapper/vg_raid-var_3 ext4 38315504 49032 36297116 1% /mnt/root_3/var
/dev/mapper/vg_raid-var_2 ext4 38315504 3016612 33329536 9% /mnt/gentoo/var
tmpfs tmpfs 1233244 12 1233232 1% /run/user/1000 |
What I did to get into chroot. (I read the trick of the run in a arch forum as I initially had problems with grub installation.
Code: | root@antec-debian:~# cp -L /etc/resolv.conf /mnt/gentoo/etcmkdir -p /mnt/gentoo/
mkdir -p /mnt/gentoo/var && mkdir -p /mnt/gentoo/boot && \
mount -t proc /proc /mnt/gentoo/proc && \
mount --rbind /sys /mnt/gentoo/sys && \
mount --make-rslave /mnt/gentoo/sys && \
mount --rbind /dev /mnt/gentoo/dev && \
mount --make-rslave /mnt/gentoo/dev && \
mount --rbind /boot /mnt/gentoo/boot && \
mount --rbind /run/ /mnt/gentoo/run && \
mount --rbind /run/ /mnt/gentoo/run && \
chroot /mnt/gentoo /bin/bash
|
In chroot I did
Code: | antec-debian / # source /etc/profile && export PS1="(chroot) $PS1" |
I followed the installation handbook, took advice in GRUB2 and GRUB2/AdvancedStorage. However, I did deviate in the latter in that I used genkernel for kernel and module compilation too, not only for initramfs. I double checked that CONFIG_FHANDLE variable is switched on.
Code: | (chroot) antec-debian / # ls -l /usr/src/
total 7413608
lrwxrwxrwx 1 root root 21 16. Mär 07:55 linux -> linux-4.9.6-gentoo-r1
drwxr-xr-x 26 root root 4096 5. Apr 13:34 linux-4.9.6-gentoo-r1
-rw-r--r-- 1 root root 7591526400 2. Apr 19:24 linux-4.9.6-gentoo-r1.tgz
(chroot) antec-debian / # grep CONFIG_FHANDLE /usr/src/linux/.config
CONFIG_FHANDLE=y |
As hinted above I initially had warnings when installing grub but could fix it by re-binding /run to the root jail as proposed in an Arch post. I could install to /devb/sda just fine (at least I thought so having no errors or warnings returned).
So I tweaked /etc/default/gub a bit
Code: | (chroot) antec-debian / # grep -vE '^(\s*($|#))' /etc/default/grub
GRUB_DISTRIBUTOR="Gentoo"
GRUB_CMDLINE_LINUX_DEFAULT="dolvm domdadm keymap=de"
GRUB_PRELOAD_MODULES=lvm |
The grub config generation went without errors too. After a reboot, I only get the debian installed grub menu. Does somebody know what I have been missing? I would appreciate some hints.
My fstab essentially is
Code: | (chroot) antec-debian / # grep -vE '^(\s*($|#))' /etc/fstab
/dev/dvd /mnt/dvd auto noauto,ro,users 0 0
UUID=526841f0-e8a0-4932-9240-9fc011cb5904 / ext4 noatime 0 1
UUID=37de9f5f-eec4-4644-a9ca-1baea33f98a9 /home ext4 noatime 0 2
UUID=2e5e6f29-be37-459f-b4b6-bb125f599e95 /boot auto noatime 0 2
UUID=a2f55c3d-55e8-43b8-b97a-f6e4c2a109a0 /var ext4 noatime 0 2
UUID=023fafed-e22a-4422-be08-7247574212c4 /mnt/root_3 ext4 noauto,noatime,users 0 2
UUID=2b1c5e29-b0c6-49be-953b-038eff3784b3 /mnt/root_3/var ext4 noauto,noatime,users 0 2
UUID=cdd212eb-ba7c-4242-a3e4-bafc8020a623 /mnt/root_1 ext4 noauto,noatime,users 0 2
UUID=f04dddc1-1796-406b-8f2d-7ed0685c79c3 /mnt/root_1/var ext4 noauto,noatime,users 0 2
UUID=bb4f53bd-4494-4661-8ef6-d0d533210db3 none swap sw 0 0 |
And my grub.cfg
Code: | (chroot) antec-debian / # grep -vE '^(\s*($|#))' /boot/grub/grub.cfg
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="0"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
if [ x$feature_default_font_path = xy ] ; then
font=unicode
else
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod lvm
insmod ext2
set root='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/YGlBUQ-sb1k-YoX7-G1uO-WFmJ-uGEI-cM6OX9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/YGlBUQ-sb1k-YoX7-G1uO-WFmJ-uGEI-cM6OX9' cdd212eb-ba7c-4242-a3e4-bafc8020a623
else
search --no-floppy --fs-uuid --set=root cdd212eb-ba7c-4242-a3e4-bafc8020a623
fi
font="/usr/share/grub/unicode.pf2"
fi
if loadfont $font ; then
set gfxmode=auto
load_video
insmod gfxterm
set locale_dir=$prefix/locale
set lang=de_CH
insmod gettext
fi
terminal_output gfxterm
if [ "${recordfail}" = 1 ] ; then
set timeout=-1
else
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
else
set timeout=5
fi
fi
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod lvm
insmod ext2
set root='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/YGlBUQ-sb1k-YoX7-G1uO-WFmJ-uGEI-cM6OX9'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/YGlBUQ-sb1k-YoX7-G1uO-WFmJ-uGEI-cM6OX9' cdd212eb-ba7c-4242-a3e4-bafc8020a623
else
search --no-floppy --fs-uuid --set=root cdd212eb-ba7c-4242-a3e4-bafc8020a623
fi
insmod png
if background_image /usr/share/images/desktop-base/lines-grub.png; then
set color_normal=white/black
set color_highlight=black/white
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
function gfxmode {
set gfxpayload="${1}"
}
set linux_gfx_mode=
export linux_gfx_mode
menuentry 'Debian GNU/Linux' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-cdd212eb-ba7c-4242-a3e4-bafc8020a623' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod lvm
insmod ext2
set root='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/hFwSFE-zy5J-9LCc-Zpsk-dIa0-MMhU-okLtPt'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/hFwSFE-zy5J-9LCc-Zpsk-dIa0-MMhU-okLtPt' 2e5e6f29-be37-459f-b4b6-bb125f599e95
else
search --no-floppy --fs-uuid --set=root 2e5e6f29-be37-459f-b4b6-bb125f599e95
fi
echo 'Linux 3.16.0-4-amd64 wird geladen …'
linux /vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_raid-root_1 ro quiet
echo 'Initiale Ramdisk wird geladen …'
initrd /initrd.img-3.16.0-4-amd64
}
submenu 'Erweiterte Optionen für Debian GNU/Linux' $menuentry_id_option 'gnulinux-advanced-cdd212eb-ba7c-4242-a3e4-bafc8020a623' {
menuentry 'Debian GNU/Linux, mit Linux 3.16.0-4-amd64' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-advanced-cdd212eb-ba7c-4242-a3e4-bafc8020a623' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod lvm
insmod ext2
set root='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/hFwSFE-zy5J-9LCc-Zpsk-dIa0-MMhU-okLtPt'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/hFwSFE-zy5J-9LCc-Zpsk-dIa0-MMhU-okLtPt' 2e5e6f29-be37-459f-b4b6-bb125f599e95
else
search --no-floppy --fs-uuid --set=root 2e5e6f29-be37-459f-b4b6-bb125f599e95
fi
echo 'Linux 3.16.0-4-amd64 wird geladen …'
linux /vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_raid-root_1 ro quiet
echo 'Initiale Ramdisk wird geladen …'
initrd /initrd.img-3.16.0-4-amd64
}
menuentry 'Debian GNU/Linux, with Linux 3.16.0-4-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-3.16.0-4-amd64-recovery-cdd212eb-ba7c-4242-a3e4-bafc8020a623' {
load_video
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod part_msdos
insmod diskfilter
insmod mdraid1x
insmod lvm
insmod ext2
set root='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/hFwSFE-zy5J-9LCc-Zpsk-dIa0-MMhU-okLtPt'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint='lvmid/KvKqZ0-3JVR-9los-97BE-5LRq-H7zd-aqqiNn/hFwSFE-zy5J-9LCc-Zpsk-dIa0-MMhU-okLtPt' 2e5e6f29-be37-459f-b4b6-bb125f599e95
else
search --no-floppy --fs-uuid --set=root 2e5e6f29-be37-459f-b4b6-bb125f599e95
fi
echo 'Linux 3.16.0-4-amd64 wird geladen …'
linux /vmlinuz-3.16.0-4-amd64 root=/dev/mapper/vg_raid-root_1 ro single
echo 'Initiale Ramdisk wird geladen …'
initrd /initrd.img-3.16.0-4-amd64
}
}
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi |
Oh, after reading the grub.cfg better, I see Debian entries however I do not see Gentoo entries. This seems to be consistent with my boot experience however I have no clue as to why there are no Gentoo entries and not having got errors/warnings when generating grub.cfg.
Kind regards
Thiemo _________________ root ist die wurzel allen uebels
Last edited by Thiemo on Fri May 05, 2017 1:53 pm; edited 1 time in total |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Thu Apr 06, 2017 12:38 pm Post subject: |
|
|
Just my thoughts.
I never understood guys using lvm wiht other software to get mirror feature
LVM2 already supports "raid feature"
https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html-single/Logical_Volume_Manager_Administration/#mirrored_volumes
Quote: | A mirror maintains identical copies of data on different devices. When data is written to one device, it is written to a second device as well, mirroring the data. |
Less software less fuss
when you use lvm you will end with a /dev/mapper/ ... "link"
From the user perspective there is no real difference
starting point
https://wiki.gentoo.org/wiki/LVM
at the time i converted my very old installation, i had to read the docs from redhat, there was no gentoo docs. I recommend that you stick to the redhat documentation regarding lvm. I recommend that you disassemble genkernels initramfs, adapt it, than repack it and reuse it, as I did. The genkernel initramfs was faulty a while ago, reading it, understanding it, repacking is not that much efforts, when you have read the redhat docs. the genkernel initramfs is jsut a barebone which is a decent starting point to adapt
--
layout according to gentoo handbook. except root is on lvm. initramfs from genkernel. everything build in kernel.
grub installed. hand made, hand written grub.cfg (I never understood why using those grub scripts of mass descrtuctions make sense!)
--
Quote: | Oh, after reading the grub.cfg better, I see Debian entries however I do not see Gentoo entries. This seems to be consistent with my boot experience however I have no clue as to why there are no Gentoo entries and not having got errors/warnings when generating grub.cfg. |
what i remember of using those grub scripts of malfunction (whenever they work or did not work)
osprober
update-grub or what it is called, which just overwrites hole grub.cfg without user intervention (e.g. on linux mint)
fix which works everytime: write your own boot section. later you just will have to move the files, name those files, update the knerel name and hte title. thats it |
|
Back to top |
|
|
frostschutz Advocate
Joined: 22 Feb 2005 Posts: 2977 Location: Germany
|
Posted: Thu Apr 06, 2017 12:48 pm Post subject: |
|
|
It's hard to get two separate Linux installs to cooperate in regards to sharing a single grub.cfg.
I write my grub.cfg manually. Have to anyway since it's an USB stick which also comes with a dozen livecds.
Not updated in a while though - http://termbin.com/ts2x
If you keep Debian around I suggest you let Debian handle the grub side of things and just add a Gentoo entry as other os over there. There's something in /etc/ that lets you add manual stuff. |
|
Back to top |
|
|
Thiemo Tux's lil' helper
Joined: 20 Nov 2002 Posts: 138
|
Posted: Fri Apr 07, 2017 5:10 am Post subject: |
|
|
Thanks for your thoughts.
@Roman: I guess it's plain half knowledge leading to such setup. I was not aware that lvm2 supports mirroring.
I shall think over my setup. _________________ root ist die wurzel allen uebels |
|
Back to top |
|
|
Roman_Gruber Advocate
Joined: 03 Oct 2006 Posts: 3846 Location: Austro Bavaria
|
Posted: Sat Apr 08, 2017 11:30 am Post subject: |
|
|
You are welcome. LEt us know what you did when you are finished. |
|
Back to top |
|
|
szatox Advocate
Joined: 27 Aug 2013 Posts: 3150
|
Posted: Sun Apr 09, 2017 3:03 pm Post subject: |
|
|
Some reasons could be that MDRAID is a bit more mature than LVM RAID.
Consistency could also be a good reason.
Some people have tools that let them do some neat things with automating stuff, but also require some particular setup, because e.g. are not aware of some features that have been added to their dependencies in version X.
Asking questions is good, announcing your sentence based on prejudice not so much. |
|
Back to top |
|
|
frostschutz Advocate
Joined: 22 Feb 2005 Posts: 2977 Location: Germany
|
Posted: Sun Apr 09, 2017 9:48 pm Post subject: |
|
|
LVM can be a bit cranky when disks go missing, mirroring or no. There's nothing wrong with using mdadm for RAID related tasks and LVM on top for regular volumes, snapshots, ... |
|
Back to top |
|
|
Thiemo Tux's lil' helper
Joined: 20 Nov 2002 Posts: 138
|
Posted: Thu Apr 13, 2017 8:06 pm Post subject: |
|
|
OK, I changed my setup to LVM2 using mirroring. However, it did not end in success. When I try to install grub, it tells me not to be able to resolve canonical path of aufs something. It actually does not really matter. Because I will return to the mdadm/lvm setup.
- I have not found any other distribution that I was interested in that supports lvm mirroring and I'd like to be able to try other distributions in parallel
- I read someone compared mdadm raid 1 to lvm2 mirroring. He found that lvm2 wrote faster and was told this was due to caching such that in case of problems, data loss is probable
- The lvm metadata is managed in memory only so that in case of crash or reboot lvm loses information on synch status of the mirrors breaking it all together.
So, return to start. _________________ root ist die wurzel allen uebels |
|
Back to top |
|
|
Thiemo Tux's lil' helper
Joined: 20 Nov 2002 Posts: 138
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|