I have a Sony Vaio SVS15 with Windows 7 64bits in which I have replaced the optical drive with an SSD on a drive caddy. My goal is to leave windows alone in the original hard drive (which is also SSD) and install Arch Linux on the second drive (in optical drive spot).
The installation of the new SSD went smoothly and it is correctly detected, formateable etc. I have installed Arch Linux there from a USB stick as described in this tutorial:
The problem I have is that when I start the computer it goes straight into Windows, whereas I have installed Arch after Windows. Both drives use GPT and Windows 7 64 bits supports UEFI.
My question is: Do you think the problem comes from the fact that Arch is on a SSD that is where the optical drive was? Or do you think it comes from how I have installed Arch/Grub?
This will help me a lot to search in one direction or another.
NB: In the boot order of the BIOS, there is still "optical drive", that is it didn't get modified when replacing it by an SSD. So the options are (in the order they are set at the moment):
- Internal Optical Disc Drive
- External Device
- Internal Hard Disk Drive
I have re-run the installation process in case I made some silly mistake. While I still can't get it to work, I have noticed a message while configuring Grub2 that might be relevant. The command I entered is:
grub-mkconfig -o boot/grub/grub.cfg
I had executed
arch-chroot previously and had mounted in /boot the 512MiB EFI partition. When running the command I get a couple of warnings and a "bad magic number" message. It then says "done" so I'm not sure whether this is an error or not:
[root@archiso /]# grub-mkconfig -o boot/grub/grub.cfg Generating grub configuration file ... Found linux image: /boot/vmlinuz-linux Found initrd image(s) in /boot: initramfs-linux.img Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img WARNING: Failed to connect to lvmetad. Falling back to device scanning. [ 171.937201] FAT-fs (md126p4): bogus number of reserved sectors [ 171.940041] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on md126p4 [ 171.942729] EXT4-fs (md126p4): VFS: Can't find ext4 filesystem [ 171.945366] EXT4-fs (md126p4): VFS: Can't find ext4 filesystem [ 171.948756] EXT4-fs (md126p4): VFS: Can't find ext4 filesystem [ 171.955360] FAT-fs (md126p4): bogus number of reserved sectors [ 171.957919] ntfs: (device md126p4): read_ntfs_boot_sector(): Primary boot sector is invalid. [ 171.958986] ntfs: (device md126p4): read_ntfs_boot_sector(): Mount option error=recover not used. Aborting without trying to recover. [ 171.960112] ntfs: (device md126p4): ntfs_fill_super(): Not an NTFS volume. [ 171.965184] ufs: You didn't specify the type of your ufs filesystem [ 171.965184] [ 171.965184] mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... [ 171.965184] [ 171.965184] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 171.970303] ufs: ufs_fill_super(): bad magic number done