![]() I have an MSI GT60 and it comes with 1 SSD and 1 HDD from the factory, however it has 3 MSATA ports and is designed to accept up to 3 MSATA devices in RAID1/0 (marketed as up to 1500MB/s disk performance). # This configuration was auto-generated on Sat, 20:33:32 -0500 by mkconf # automatically tag new arrays as belonging to the local system alternatively, specify devices to scan, using # by default (built-in), scan all partitions (/proc/partitions) and all # Please refer to nf(5) for information about this file. # !NB! This will ensure that initramfs has an uptodate copy. # !NB! Run update-initramfs -u after updating this file. Is it possible if I have something set up wrong in mdadm and that's why it shows up as a virtual device? My mdadm conf is as follows:.Is there a reason I shouldn't just comment this out (or make it smarter by checking for 'md' in the path with grep)?.I know that all code is written for a reason and this was put here at some point. ![]() This allows os-prober to correctly find the Windows EFI files and populate the menus in grub correctly, the machine can now boot windows and ubuntu from grub successfully. ![]() Open /usr/lib/os-probes/mounted/05efi in vim and comment out line 34. Which means it won't look for EFI files on this partition because it is a virtual disk. Upon running the udevadm command in the condititional it spits out. Upon further investigation of why I stumbled across lines 31-35 of /usr/lib/os-probes/mounted/05efi and the debug line there showing up in the logs. OS prober does not find the windows installation on the Intel RST Raid despite being able to mount the partition with the EFI files. ![]() Windows 10 on a Intel RST Raid across 2 SSDs.Last but not least, if you have some sensitive files containing passwords like IPsec secrets or pf configurations it may be good to put them into an encrypted partition, like /home, and symlink them to their official location.I have a Desktop with the following drive configuration: # umount partitions related to crypto device in reverse order of mount output add the following to the /etc/rc.shutdown file: for device in $mounted doĮcho $device is a crypto device, umounting its partitions and delete crypto volume To avoid this we will create a script that unmount the partitions located on the crypted device and then destroy the crypted disk before the sd3 devices gets removed.ġ8. The next reboot will say that the sd4 device was not correctly unmounted and may request a fsck. “sd3” gets shutdown before sd4, hence sd4 will be unable to write metadata to the underlying sd3 device. The last “problem” we have is when we shutdown your system, OpenBSD will remove the devices approximately in the same order they are created. Next step is only required for OpenBSD 5.3, it has been corrected since reboot and check if the passphrase is asked and working, if not redo the step “17”. In theory I should have put it in /etc/rc.securelevel, the problem is that rc.securelevel is called too late in the boot process, after the mount of the partitions.ġ7. The location of my script is a bit tricky. This script will hang the boot process until the passphrase for the encrypted device is entered, then it will be able to mount the system partitions that are on the crypted sd4 device (/tmp, /usr, …). drop to a (S)hell in the installation program boot an install media (I used PXE here)Ģ. As it’s not yet possible I decided to create one softraid1 partition containing “/” and a second softraid1/encrypted partition containing some mount points: /tmp, /var, /usr, /usr/X11R6, /usr/local, /usr/src, /usr/objīelow, I’ll describe the steps to obtain such setup.ġ. Sadly it doesn’t supports booting from raid+encrypted volumes yet (they’re working on it).įor my setup I want to have redundancy (meaning RAID1) and, ideally, crypto everywhere. It also supports booting from encrypted volumes. Before that, the way to have redundancy for the root partition was to place /altroot on a second disk and to manually switch to it in the case of failure of the first disk. OpenBSD supports booting from a raid volume since version 5.3. It may be useful as these features are quite new and not heavily documented on the net. ![]() DISCLAIMER: This how-to must be taken as is, it should not replace the official documentation and is not meant to do so. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |