dual boot ubuntu windows 10, separate SSD, partitioning, laptop

I’ve already used Ubuntu a little bit on a virtual machine before but now I have to have a real Linux system for a college course so I’m trying to prepare in advance for this course by installing it.

However, as I’ve been a windows used thusfar, I still have windows 10 on my main SSD 250GB on the laptop. I will most likely use windows10 for some python programming and games, because all my tools and visual studio are installed on my windows SSD.

So, I decided that since my laptop has a second hard drive bay for another hard drive, I decided to buy a Kingston 960GB SSD for this purpose of having Ubuntu on it.

I haven’t done anything yet, because I don’t have the proper screw driver to install the big Kingston SSD yet.

some questions about dual booting for my case

1.) I was thinking about having a smaller partition for the Ubuntu system if that is possible, so that I would only have about 500 – 600GB for the Ubuntu system on the Kingston SSD. How do I partition that new Kingston SSD?

2.) I would like to have the rest of the Kingston SSD partition available for extra storage space for my windows system (something like 460- 360GB) if that makes any sense, because my main windows SSD is only 250GB and I would like little bit extra space occasionally on the windows side. How do I make the bigger Kingston partition available for Ubuntu, and the smaller partition available for windows10 if that is possible?

3.) windows10 is already installed of course on the smaller current 250GB SSD

4.) I have backed up most of my personal files from the windows10 SSD of course

5.) laptop is acer nitro 5

Cannot partition w/ Boot Camp Assistant on macOS Mojave

Late 2016 Macbook Pro running Mojave 10.14.3, APFS-formatted (ugh).

I have run Disk Utility to verify my disk, and I’ve run fsck -fy from single-user mode several times. Both of these have reported absolutely no errors.

And yet, whenever I try to run Boot Camp Assistant to dual-boot with Windows 10, I get an error that says: “An error occurred while partitioning the disk.”

Thinking I’d be clever, I also tried to create a partition manually through Disk Utility, but that didn’t work either. I also reinstalled macOS in Recovery Mode.

I am starting to suspect that this is a problem with APFS. What other commands could I run to receive more information as to why Boot Camp Assistant won’t let me create a partition to run Windows? Thanks in advance.

How to create dual boot with LUKS/LVM full partition encryption on same disk?

I followed this tutorial from 2014: https://www.oxygenimpaired.com/multiple-linux-distro-installs-on-a-luks-encrypted-harddrive

I am installing Linux Mint 19.1 XFCE and Ubuntu 18.04, both fully encrypted in a single disk. First I installed Linux Mint on /dev/sda5.

After following all steps to install the first Linux, and rebooting the machine, I got into the Boot drops to a (initramfs) prompts/busybox with this error:

  1. enter image description here

When following the tutorial, I ran the following commands:

  1. fdisk /dev/sda, then, created the following partitions:
    • enter image description here
  2. cryptsetup luksFormat /dev/sda5
  3. cryptsetup luksOpen /dev/sda5 sda5_crypt
  4. pvcreate /dev/mapper/sda5_crypt
  5. vgcreate vggroup /dev/mapper/sda5_crypt
  6. lvcreate -L1G -n mint_xfce_swap vggroup
  7. lvcreate -L8.9G -n mint_xfce_root vggroup
    • enter image description here
  8. mkdir /mnt/newroot
  9. mount /dev/mapper/[vg-name]-[root1-lv-name] /mnt/newroot
  10. mount -o bind /proc /mnt/newroot/proc
  11. mount -o bind /dev /mnt/newroot/dev
  12. mount -o bind /dev/pts /mnt/newroot/dev/pts
  13. mount -o bind /sys /mnt/newroot/sys
  14. cd /mnt/newroot
  15. chroot /mnt/newroot
  16. mount /dev/sda1 /boot
  17. blkid /dev/sda5
    • enter image description here
    • enter image description here
    • enter image description here
  18. update-initramfs -u
  19. update-grub
    • enter image description here
    • enter image description here
  20. exit
  21. reboot

Other references:

  1. Ubuntu dual-boot with LVM and LUKS install fails
  2. How can I install Ubuntu encrypted with LUKS with dual-boot?

Grub won’t show Windows 10 but it shows Windows Boot Manager

I’m trying to start using Ubuntu. I already had Windows 10 in my hdd, I made a new partition for Ubuntu 18.04 and then installed it. Both OS are in the same hdd but in different partitions, but when I boot it shows the grub and it won’t show Windows 10 option, it shows Windows Boot Manager (and if I pick this it will let me boot in Windows but it’s slow). I already tried os-prober (from this question: GRUB does not detect Windows) and this is what it shows

/dev/sda2@/EFI/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi 

when I use fdisk -l this is what it shows (in Spanish, I’m sorry)

Disco /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectores Unidades: sectores de 1 * 512 = 512 bytes Tamaño de sector (lógico/físico): 512 bytes / 4096 bytes Tamaño de E/S (mínimo/óptimo): 4096 bytes / 4096 bytes Tipo de etiqueta de disco: gpt Identificador del disco: C271E36A-B1BA-4B61-9C48-B90831A729D5  Dispositivo   Comienzo      Final   Sectores Tamaño Tipo /dev/sda1         2048    1023999    1021952   499M Entorno de recuperación de Windows /dev/sda2      1024000    1226751     202752    99M Sistema EFI /dev/sda3      1226752    1259519      32768    16M Reservado para Microsoft /dev/sda4      1259520 1187666070 1186406551 565.7G Datos básicos de Microsoft /dev/sda5   1187667968 1953523711  765855744 365.2G Sistema de ficheros de Linux 

I’m not sure what should I do or what all of these means, I’m not used to linux.

In BIOS I have secure boot and legacy both disabled. I already made sure hibernate option is disabled in Windows

how to make a volume with a system image on it the Windows 7 boot volume

I’ve created a Windows 7 x64 system partition image on an empty volume on another drive because the original boot drive was throwing errors and SMART BIOS thinks it is “bad” even though the manufacturer’s utility reports it as in good health.

The image is here:

S:\img\imagename

Is there a simple way to make S: the boot volume, change its drive letter to C:, and take the original drive offline, without having to copy the image somewhere else? I don’t have any free space anywhere to put it, and all the SATA cables are in use.

Boot error 0xc00000f, but cant rebuild bcd

Hi Im having boot error 0xc00000f and 0xc00000225 on my windows 10, so I tried the bootrec method, but it returned “requested system device cannot be found” on /rebuildbcd, so I search online and it seems like my PC UEFI can load the USB bootable media, but the windows recovery environment may not, what does this mean? So I search further and it may have to do with mbr or gpt partition?

Securely Mounting a Remote LUKS Partition at Boot

I am having trouble setting up a system to backup a couple of computers, it has several partitions that are LVM on LUKS, and the server has no disk encryption. My computer is encrypted, and I am comfortable with storing the keys on it, but I am not finding any good ways to do so. The partitions are located on a network disk, and should be automatically mounted at boot on the client system. The server should not remember the key outside of RAM if possible. The server and my computer are on 18.10.

Boot Camp: Plugging in an external mouse makes mouse click not work anymore

So this started happening recently, I think after the last OS upgrade. Now if I plug in an external mouse (any mouse, I’ve tested several) while in Windows 10, the mouse click and scroll won’t work anymore. It also disables the mouseclick on the track pad. The really weird thing is that I’m able to click on icons on the desktop, once. So I can’t double click them to open them, but I get that blue highlight when clicking once.

  • I’ve tried rebooting with the mouse Connected, and then it works for like 10 seconds. Which makes me believe some service starts up and messes everything up.
  • I’ve tried running msconfig to disable all non-Windows services, and then rebooting.
  • I’ve tried uninstalling the device from the Device Manager.

Android verified boot and custom ROMs

I’m trying to figure out how exactly works the Android Verified Boot process and its usage with custom ROMs. The documentation I found on it is unclear (or outdated) as there seems to be several ways to do it.

What I understood (please correct me if I’m wrong) is listed below.

Before flashing :

  1. The bootloasder is initially locked, and has to be unlocked through the fastboot command (and a physical confirmation from the end user).
  2. The user data are totally wiped in order to prevent unauthorized access through rooting process (e.g. if a device is theft and the thief tries to access private data).
  3. The custom ROM public key is stored in the user-settable root of trust (alongside with the manufacturer’s one) when the OS is flashed.

Boot process (after flashing) :

  1. The systems is powered on (physical button)
  2. The device embedded BIOS reads the public keys stored in the root of trust (manufacturer and user-settable) and verifies that the kernel image has not been tampered.
  3. If the public key used to check kernel tampering is the user-stable one, then a 10 seconds warning is displayed in order to warn the end-user that the pub. key used to perform these checks is not the manufacturer’s one.
  4. Once the kernel integrity is confirmed, the initial ram image is loaded and the init process is called.
  5. The dm-verity kernel module ensures that the boot process is not tampered through cryptographically signature checks, using a public key.

As I write these lines, several steps are still unclear to me :

  • Why are warnings displayed during boot if integrity checks pass ? I mean, even if the user-settable root of trust is used (instead of the manufacturer’s one), integrity checks are still OK, don’t they ?
  • Is the UNLOCKED state needed in order to set the user-settable root of trust, or is it needed to bypass Android Verified Boot ?
  • How is handled the “tamper evident” feature for the user-settable root of trust ? I mean : the user-settable root of trust should only be set by the end user (and not the manufacturer) but how can we be sure that It did not set one anyway ? Moreover, if the system is rooted, how can we be sure that the “new” OS has not reset the tamper evident flag ? Are one-time programmable memory used ?
  • What public key is used by the dm-verity kernel module in order to perform integrity checks ?

Thanks in advance !

Disable autostart on boot [duplicate]

This question already has an answer here:

  • How can I prevent applications from running on startup? [duplicate] 8 answers
  • how to identify and change apps which are set as startup items [duplicate] 2 answers

Is there any way to disable autostart apps at boot time? I need to disable some of them (not all) like Facebook, etc to get quicker boot time. I’m asking how to do this on Android 9.0.