@吕而立.outlier(330741746 )我本来欲直接回复阁下的日志,但是不知不觉写多了,超过500字符不让发。这种总结性质的稿应该发部落格,无奈那里没法圈人。本着一文不两投的精神,我就发到这里来了。-- http :// caowm2001 . blogspot . com
(re)sorted
linux kernel software-raid aka "md" driver identifies windows dynamic disks very well with no need of aseperate programs. the tricky problem is to get grub find the kernel.
'd admit that i have not much ideas of gpt, nither uefi, but for pc-bios/mbr configured windows dynamic disks we can do it pretty clean. my situation, dynamic disk with multiple volumes. the mbr tells 4 primary partitions, all of them windows dynamic disk storage areas. first three can directly be mounted as ntfs. coresponding to the leading 3 dynamic volumes. last being a whole chunk till end of disk, internal structure unknown.
first don't install grub onto the mbr, but place grub image in "C:" and let bcd chainload it. for me, that when grub write certain mbr sectors it will collide into area storing the dynamic disk layout configuration. linux won't read the dynamic disk volumes that way but windows runs seamlessly. the fix is amazingly easy, use bootrec utility of windows recovery cd.
grub cannot identify windows dynamic disks but mbr. nither can the BCD bootloader of windows. i.e. for windows to boot correctly the partitions storing bcd bootloader image and kernel image must always be transparent, which is to say, is the first volume or one in the three leading partitions of the partition table, and has "linear" configuration. windows use "system volume" to store bcd bootloader. apart from "system volume" there is also "boot volume". "system volume" is kinda like the "/boot" partion for linux, windows puts its bcd bootloader there, while "boot volume" is the always "C:" coreponding to "/" aka root partition. naming is confusing that "system"->boot while "boot"->root. like linux "/boot" and "/", the windows "system volume" and "boot volume" can usually be the same partition but sometimes different ones. not yet known if windows kernel image is in "system" or "boot". 'conclude, both "system" volume is of 100percent confidence safe to save the linux kernel. but i can bet "C:" the "boot" volume is of grand probability also safe.
'tell my field exp, grub2win is a very sweet package to manage grub in windows, just unpack it in "C:". an app is provided to adjust both bcd and grub settings. in the linux "/etc/fstab", mounts are established as: "system volume" -> /mnt/winboot "boot volume" aka "C:" -> /mnt/windows thus we have symlinks: /boot -> /mnt/winboot/linux (%system volume%\linux\) /boot/grub/grub.cfg -> /mnt/windows/grub2win/grub.cfg (C:\grub2win\grub.cfg) to my great satisfaction, symlinks in ntfs can be just good. this way, linux kernel updates are installed to "%system volume%\linux\" and update-grub saves config to grub2win.
3。A VERY SHY BOY。这位同志嘛,就是我们的蕾姐负责接待了。话说当时蕾姐一看自己分到的是个黑发黑眼的华裔,那个兴奋啊,心想总算不用秀英语了。笑吟吟的问了一句:CAN YOU SPEAK CHINESE?得到的却是很坚定的回答:NO!于是笑容就僵在了脸上。据称,此子在回答蕾姐的任何问题时有三句万能回答,为期3个小时的吃饭+唠嗑时间中回答总不脱出这三句:YES。NO。I DON’T KNOW。尴尬,标准的尴尬,让我们为蕾姐默哀一下···