You are not logged in.
Pages: 1
Howdy,
I'm trying to install GRUB in an extended partition (later to be joined by Kali) on a drive it will share with Windows 10, and because it shares this drive with Windows the latter insists on the partitioning scheme being MBR. My partition layout, created via
fdisk, is:
sda1: Windows 10 loader
sda2: Windows 10
sda3: 64GB Extended partition
sda4: NTFS Mass storage partition
sda5: 32GB ext4 partition for Arch
sda6: 32GB ext4 partition for Kali
I'd never had problems doing similar (virtually identical, except for Windows being W7) setups before, but for the past few days when I get to the point of running
grub-mkconfig -o /boot/grub/grub.cfgit terminates thusly:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Found fallback initramfs image: /boot/initramfs-linux-fallback.img
/run/lvm/lvmetad.socket: connect failed: No such file or directory
WARNING: Failed to connect to lvmetad. Falling back to internal scanning.
[Timestamp] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda3
[Timestamp] EXT4-fs (sda3): unable to read superblock
[Timestamp] EXT4-fs (sda3): unable to read superblock
[Timestamp] EXT4-fs (sda3): unable to read superblock
[Timestamp] FAT-fs (sda3): bogus number of reserved sectors
[Timestamp] FAT-fs (sda3): bogus number of reserved sectors
[Timestamp] ntfs: (device sda3): read_ntfs_boot_sector(): primary boot sector is invalid.
[Timestamp] ntfs: (device sda3): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[Timestamp] ntfs: (device sda3): ntfs_fill_super(): Not an NTFS volume
[Timestamp] ufs: You didn't specificy the type of your ufs filesystem
[Timestamp]
[Timestamp] mount -t ufs -o ufstype=[a bunch of different types] . . .
[Timestamp]
[Timestamp] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[Timestamp] squashfs: SQUASHFS error: Can't find a SQUASHFS superblock on sda4
[Timestamp] EXT4-fs (sda4): VFS: Can't find ext4 filesystem
[Timestamp] EXT4-fs (sda4): VFS: Can't find ext4 filesystem
[Timestamp] EXT4-fs (sda4): VFS: Can't find ext4 filesystem
[Timestamp] FAT-fs (sda4): bogus number of reserved sectors
[Timestamp] FAT-fs (sda4): bogus number of reserved sectors
[Timestamp] ntfs: (device sda4): read_ntfs_boot_sector(): primary boot sector is invalid.
[Timestamp] ntfs: (device sda4): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover.
[Timestamp] ntfs: (device sda4): ntfs_fill_super(): Not an NTFS volume
[Timestamp] ufs: You didn't specificy the type of your ufs filesystem
[Timestamp]
[Timestamp] mount -t ufs -o ufstype=[a bunch of different types] . . .
[Timestamp]
[Timestamp] >>>WARNING<<< Wrong ufstype may corrupt your filesystem, default is ufstype=old
[Timestamp] ufs: ufs_fill_super(): bad magic number
Found Windows 10 (loader) on /dev/sda1
done
Could this have something to do with alignment or something? I used
fdiskbecause when I would try to do the extended partition in
parted, the latter would yell at me about sectors being misaligned, so I switched to the former because I'm more comfortable with it.
Last edited by reddfloyd (2016-01-08 16:34:28)
Offline
Welcome to the forums,
What is the output of:
parted /dev/sda print?Offline
Sorry for the late reply. The output is as follows:
Model: ATA WDC WD5000BPVT-2 (scsi)
Disk /dev/sda: 500GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 525MB 524MB primary ntfs boot
2 525MB 69.2GB 68.7GB primary ntfs
3 69.2GB 138GB 68.7GB extended
5 69.2GB 104GB 34.4GB logical ext4
6 104GB 138GB 34.4GB logical ext4
4 138GB 500GB 362GB primary
Offline
Not a problem. How did you run
grub-installand where there any errors?
Last edited by tyrannis (2016-01-21 00:24:03)
Offline
Pages: 1