Error no such device press any key to continue

Arch Linux

You are not logged in.

#1 2016-03-21 17:18:18

Grub: error: no such device:

G’day mates! I’ve got a bit of trouble installing Arch, first to my laptop and then to a VM. The same trouble seems to haunt both attempts. Immediately after installation is finished, I reboot, and I select the first option in Grub, I’m greeted with a warning:

error: no such device: string-of-characters
Loading Linux core repo kernel.
error: no such partition.
Loading initial ramdisk.
error: you need to load the kernel first.
Press any key to continue.

after which it returns to the grub menu.

After a bit of online searching, it appeared that my fstab is not configured properly. So I booted up a live Arch install, mounted the / partition (sda1), and checked fstab. Sure enough, fstab is completely empty. This is a bit weird because I’m positive I ran

So I reformatted swap, made sure that sda1 was mounted in /mnt, and reran genfstab. It appeared to execute correctly, but «cat /mnt/etc/fstab» once again revealed an empty fstab.

At this point I think it would be best to ask for help. I’ve checked the permissions of /mnt/etc/fstab; it is indeed -rw-r—r— and owned by root. I’ve checked the arch iso (v. 2016.02.01) and the checksums are good too.

My entire installation script is at http://pastebin.com/XAavu1nz

Thanks for any help!
Fred

Last edited by Fred Barclay (2016-03-21 20:56:49)

Источник

Linux Mint Forums

Welcome to the Linux Mint forums!

[SOLVED] Grub error no such device and no such partition

[SOLVED] Grub error no such device and no such partition

Post by patrick.landry2 » Sat Jul 30, 2011 6:40 pm

I need help to figure out why I cannot boot into Windows XP

When I attempt to boot from the Grub menu I get:

ERROR: No Such Device
ERROR: No Such Partition

Press any key to continue

When I press any key it send me back to the Grub Menu

The system will boot into MintLinux 9 from the Grub menu without issue.
I have searched and searched the forums trying several fixes to no avail.

What I have tried:
From LiveCD — grub-install, update-grub — No Joy
From Mint 9 — grub-install, update-grub — No Joy
From Mint 9 — apt-get purge grub-common, apt-get install grub-pc, grub-install, update-grub — No Joy

My system:
AMD Phenom II 1100T
Asus Crosshair V Formula
nVidia GT 520
Seagate 320GB SATA HDD (sda)
Seagate 2TB SATA HDD (sdb)
LG BD Rewriter

Relevant Boot data:
Boot Info Script 0.60 from 17 May 2011

=> Grub2 (v1.97-1.98) is installed in the MBR of /dev/sda and looks at sector
1 of the same hard drive for core.img. core.img is at this location and
looks in partition 1 for /boot/grub.
=> No boot loader is installed in the MBR of /dev/sdb.

File system: ntfs
Boot sector type: Windows XP
Boot sector info: No errors found in the Boot Parameter Block.
Operating System: Windows XP
Boot files: /boot.ini /ntldr /NTDETECT.COM

File system: vfat
Boot sector type: Unknown
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /boot.ini /ntldr /NTDETECT.COM

File system: ext4
Boot sector type: —
Boot sector info:
Operating System: Linux Mint 9 Isadora
Boot files: /boot/grub/grub.cfg /etc/fstab /boot/grub/core.img

File system: swap
Boot sector type: —
Boot sector info:

File system: ext4
Boot sector type: —
Boot sector info:
Operating System:
Boot files:

Drive: sda _____________________________________________________________________

Disk /dev/sda: 320.1 GB, 320072933376 bytes
240 heads, 63 sectors/track, 41345 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 63 606,644,639 606,644,577 7 NTFS / exFAT / HPFS
/dev/sda2 606,644,640 625,136,399 18,491,760 c W95 FAT32 (LBA)

Drive: sdb _____________________________________________________________________

Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders, total 3907029168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 1 3,907,029,167 3,907,029,167 ee GPT

GUID Partition Table detected.

Partition Start Sector End Sector # of Sectors System
/dev/sdb1 2,048 39,065,599 39,063,552 Data partition (Windows/Linux)
/dev/sdb2 39,065,600 54,691,839 15,626,240 Swap partition (Linux)
/dev/sdb3 54,691,840 3,907,026,943 3,852,335,104 Data partition (Windows/Linux)

«blkid» output: ________________________________________________________________

Device UUID TYPE LABEL

/dev/sda1 FE88DF3088DEE5E5 ntfs HP_PAVILION
/dev/sda2 4C85-50CF vfat HP_RECOVERY
/dev/sdb1 e1a23d21-f756-4de8-8862-6ec1a3ae851e ext4
/dev/sdb2 7332b096-709b-4c1c-ae33-e5ebc1409dd2 swap
/dev/sdb3 12b960d0-1954-4fb1-8af8-f381a92e3a58 ext4

Device Mount_Point Type Options

/dev/sdb1 / ext4 (rw,errors=remount-ro)
/dev/sdb3 /home ext4 (rw)

multi(0)disk(0)rdisk(0)partition(1)WINDOWS=»Windows XP Media Center Edition» /noexecute=optin /fastdetect /usepmtimer

C:CMDCONSBOOTSECT.DAT=»Microsoft Windows Recovery Console» /cmdcons

multi(0)disk(0)rdisk(0)partition(1)WINDOWS=»Microsoft Windows XP Professional» /fastdetect

C:CMDCONSBOOTSECT.DAT=»Microsoft Windows Recovery Console» /cmdcons

———————————————————————————
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by /usr/sbin/grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default=»0″
if [ $ ]; then
set saved_entry=$save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault <
if [ -z $ ]; then
saved_entry=$
save_env saved_entry
fi
>

function recordfail <
set recordfail=1
if [ -n $ ]; then if [ -z $ ]; then save_env recordfail; fi; fi
>
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640×480
insmod gfxterm
insmod vbe
if terminal_output gfxterm ; then true ; else
# For backward compatibility with versions of terminal.mod that don’t
# understand terminal_output
terminal gfxterm
fi
fi
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
if [ $ = 1 ]; then
set timeout=-1
else
set timeout=10
fi
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/06_mint_theme ###
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
insmod png
if background_image /boot/grub/linuxmint.png ; then
set color_normal=white/black
set color_highlight=white/light-gray
else
set menu_color_normal=white/black
set menu_color_highlight=white/light-gray
fi
### END /etc/grub.d/06_mint_theme ###

### BEGIN /etc/grub.d/10_linux ###
menuentry «Linux Mint 9, 2.6.32-21-generic (/dev/sdb1)» —class linuxmint —class gnu-linux —class gnu —class os <
recordfail
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=e1a23d21-f756-4de8-8862-6ec1a3ae851e ro quiet splash
initrd /boot/initrd.img-2.6.32-21-generic
>
menuentry «Linux Mint 9, 2.6.32-21-generic (/dev/sdb1) — recovery mode» —class linuxmint —class gnu-linux —class gnu —class os <
recordfail
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
echo ‘Loading Linux 2.6.32-21-generic . ‘
linux /boot/vmlinuz-2.6.32-21-generic root=UUID=e1a23d21-f756-4de8-8862-6ec1a3ae851e ro single
echo ‘Loading initial ramdisk . ‘
initrd /boot/initrd.img-2.6.32-21-generic
>
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/10_lupin ###
### END /etc/grub.d/10_lupin ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry «Memory test (memtest86+)» <
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
linux16 /boot/memtest86+.bin
>
menuentry «Memory test (memtest86+, serial console 115200)» <
insmod ext2
set root='(hd1,1)’
search —no-floppy —fs-uuid —set e1a23d21-f756-4de8-8862-6ec1a3ae851e
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
>
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry «Windows XP Media Center Edition (on /dev/sda1)» <
insmod ntfs
set root='(hd0,1)’
search —no-floppy —fs-uuid —set fe88df3088dee5e5
drivemap -s (hd0) $
chainloader +1
>
menuentry «Windows NT/2000/XP (on /dev/sda2)» <
insmod fat
set root='(hd0,2)’
search —no-floppy —fs-uuid —set 4c85-50cf
drivemap -s (hd0) $
chainloader +1
>
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the ‘exec tail’ line above.
### END /etc/grub.d/40_custom ###
———————————————————————————

———————————————————————————
# /etc/fstab: static file system information.
#
# Use ‘blkid -o value -s UUID’ to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).
#
#

proc /proc proc nodev,noexec,nosuid 0 0
# / was on /dev/sdb1 during installation
UUID=e1a23d21-f756-4de8-8862-6ec1a3ae851e / ext4 errors=remount-ro 0 1
# /home was on /dev/sdb3 during installation
UUID=12b960d0-1954-4fb1-8af8-f381a92e3a58 /home ext4 defaults 0 2
# swap was on /dev/sdb2 during installation
UUID=7332b096-709b-4c1c-ae33-e5ebc1409dd2 none swap sw 0 0
———————————————————————————

Источник

Thread: no such device: error from boot but Nautilus sees it OK

Thread Tools

Display

no such device: error from boot but Nautilus sees it OK

I have an external usb disc which contains some operating systems and user data. Having tried various methods from this forum and google followed by update-grub etc. the boot menu shows the os details but gives the following error messages when selected:

The disc is mounted when logged in to the internal disc Maverick and I can access the files for read and write from there.

Here is the latest RESULTS.txt

It may be in a peculiar state after my abortive attempts to resolve this.

I shall be grateful for advice which enables me to boot into the external disc os(s).

Re: no such device: error from boot but Nautilus sees it OK

Re: no such device: error from boot but Nautilus sees it OK

I still don’t know why, but my new desktop has trouble with grub2 trying to boot a partition farther out on a 500 GB USB hard drive (which boots fine on different laptops from 2006), even though the desktop boots Ubuntu fine from the far end of its 1 TB internal drive. Although, the error I got in the past from grub rescue was: unknown filesystem (for ext3 or ext4). The desktop works fine booting Ubuntu on a partition closer to the beginning an identical 500 GB USB hd (or anywhere on 160 GB USB hd), but I don’t know where the cutoff point is that works. Note:

262.4GB: boot/grub/core.img
284.5GB: boot/grub/grub.cfg
222.7GB: boot/initrd.img-2.6.32-26-generic
222.9GB: boot/initrd.img-2.6.35-23-generic
262.4GB: boot/vmlinuz-2.6.32-26-generic
262.5GB: boot/vmlinuz-2.6.35-23-generic
222.9GB: initrd.img
222.7GB: initrd.img.old
262.5GB: vmlinuz
262.4GB: vmlinuz.old

Maybe it would help to have a separate /boot partition at the beginning of the drive. Was Maverick able to boot from USB before installing Natty?

But you also have older kernels than current kernels in Natty, so not sure if that is an issue. Although, I use 64-bit, so my current uname -a is: Linux natty-ssd 2.6.37-11-generic #25-Ubuntu SMP Tue Dec 21 23:42:56 UTC 2010 x86_64 GNU/Linux

I don’t have Natty on USB hard drive, but I did have Natty on 8 GB USB stick, and now have Kubuntu Natty regular install on that stick. I currently boot Natty from internal SSD with grub2 on that /dev/sdb as boot drive (Win7 & Maverick are on 1 TB hda).

Re: no such device: error from boot but Nautilus sees it OK

From what you’ve posted so far I assume you can boot the 10.10 on sda2, eh? If so the very first thing I’d do is boot into it and run:

Wait for it to say done and see what happens. If the Natty on sdb1 and 10.10 on sdb6 still fail to boot read on.

I see your drives are as follows:

Disk /dev/sda: 30.0 GB
Disk /dev/sdb: 320.1 GB

And the MBR’s are assigned as follows:

So the next thing I’d try is changing the hard drive boot order in BIOS and see if either sdb1 or sdb6 will boot.

If things are still a no-go on both sdb1 and sdb6 I’d like to see the output of:

I should also mention that you appear to have mixed grub2 and legacy grub files on Natty, but I’d not worry about that until we can get the 10.10 on sdb6 booting

Re: no such device: error from boot but Nautilus sees it OK

From what you’ve posted so far I assume you can boot the 10.10 on sda2, eh? If so the very first thing I’d do is boot into it and run:

Yes 10.10 on sda boots as did the sdb installs prior to the last two updates to 10.10 on sda. No change from sudo update-grub.

I see your drives are as follows:

Disk /dev/sda: 30.0 GB
Disk /dev/sdb: 320.1 GB

And the MBR’s are assigned as follows:

So the next thing I’d try is changing the hard drive boot order in BIOS and see if either sdb1 or sdb6 will boot.

The Acer is eight years old and only offers Hard Disk, CD/DVD, Floppy Disk and Networks boot options — it does not have a USB Disk option.

If things are still a no-go on both sdb1 and sdb6 I’d like to see the output of:

Since my first post I installed another 10.10 in sdb8 (10Gb of 90 Gb that I use for additional installs or attempted repairs) in the hope it might sort it for me but no change.

Re: no such device: error from boot but Nautilus sees it OK

Re: no such device: error from boot but Nautilus sees it OK

I am no expert regarding grub2, Linux or anything in particular

Perhaps a tenable temporary workaround could be to roll back the updates to grub2 and post a bug report ( https://help.ubuntu.com/community/Sy. kage%20version https://help.ubuntu.com/community/ReportingBugs — no doubt you knew exactly where these are )

I haven’t researched, I’m guessing that you can access it in nautilus because a module for the kernel that takes care of USB storage in older PCs, where the BIOS doesn’t take care of USB storage access, is being loaded as it ought and perhaps they’ve dropped similar functionality (ie., a similar module(/part of) grub2 has been dropped) rendering the loader blind to your USB storage till a kernel is up and running with it’s module — if I’m right then it will never boot off a USB device using that(/these) version(s) of grub2 in a PC that doesn’t ‘connect’ USB storage in BIOS(/low level).

Being accessible once a kernel is actually booted, ‘update-grub’ and similar utilities can ‘see’ the USB storage and so can happily have it/them listed in the boot menu but if grub2 has been treated/borked as I’ve guessed then it cannot ‘see’ them.

I decided to at least check the changelog for grub2 under 10.10 before posting it is attached, I found the odd entry that made me wonder if that was what borked it for you, but I didn’t come across an entry that made me think that my guess is right for sure.

(I have subscribed this thread)

Источник

[gparted photo]

I had windows 10 alongside Ubuntu 14.04 on the same hard drive.

When I switch on and the list of options to boot appears I can boot into Ubuntu ok and access all windows files, but can not boot into windows 10.

When I choose windows 10 to boot I get the message:

error: no such device: 27795F9B69145D5C.
press any key to continue...

Then the screen goes blank

I am new to Ubuntu.

vuletic@vuletic-Aspire-5735:~$ sudo blkid
[sudo] password for vuletic: 
/dev/sda1: LABEL="PQSERVICE" UUID="EAEE-EB49" TYPE="vfat" 
/dev/sda2: UUID="a03c32da-1e8d-4c37-8aa7-b8e8e501f63b" TYPE="ext4" 
/dev/sda3: LABEL="C:/" UUID="27795F9B69145D5C" TYPE="ntfs" 
/dev/sda4: UUID="323C3EB83C3E7747" TYPE="ntfs" 
vuletic@vuletic-Aspire-5735:~$ 

vuletic@vuletic-Aspire-5735:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
#                
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sda2 during installation
UUID=a03c32da-1e8d-4c37-8aa7-b8e8e501f63b /               ext4    errors=remount-ro 0       1
vuletic@vuletic-Aspire-5735:~$ 

vuletic@vuletic-Aspire-5735:~$ sudo fdisk -l

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xc637a1a9

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048    20482047    10240000   27  Hidden NTFS WinRE
/dev/sda2        20482048    79077375    29297664   83  Linux
/dev/sda3   *    79079424   975055575   447988076    7  HPFS/NTFS/exFAT
/dev/sda4       975056896   976054271      498688   27  Hidden NTFS WinRE
vuletic@vuletic-Aspire-5735:~$ 

vuletic@vuletic-Aspire-5735:~$ sudo add-apt-repository ppa:yannubuntu/boot-repair
[sudo] password for vuletic: 
 Simple tool to repair frequent boot problems.

Website: https://sourceforge.net/p/boot-repair/home
 More info: https://launchpad.net/~yannubuntu/+archive/ubuntu/boot-repair
Press [ENTER] to continue or ctrl-c to cancel adding it

gpg: keyring `/tmp/tmphj6oekac/secring.gpg' created
gpg: keyring `/tmp/tmphj6oekac/pubring.gpg' created
gpg: requesting key 60D8DA0B from hkp server keyserver.ubuntu.com
gpg: /tmp/tmphj6oekac/trustdb.gpg: trustdb created
gpg: key 60D8DA0B: public key "Launchpad PPA for YannUbuntu" imported
gpg: Total number processed: 1
gpg:               imported: 1  (RSA: 1)
OK
vuletic@vuletic-Aspire-5735:~$ 
14.04 

vuletic@vuletic-Aspire-5735:~$ sudo update-grub
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-3.13.0-106-generic
Found initrd image: /boot/initrd.img-3.13.0-106-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found linux image: /boot/vmlinuz-3.5.0-49-generic
Found initrd image: /boot/initrd.img-3.5.0-49-generic
Found Windows Recovery Environment (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda3
Found linux image: /boot/vmlinuz-3.13.0-106-generic
Found initrd image: /boot/initrd.img-3.13.0-106-generic
Found linux image: /boot/vmlinuz-3.13.0-49-generic
Found initrd image: /boot/initrd.img-3.13.0-49-generic
Found linux image: /boot/vmlinuz-3.13.0-48-generic
Found initrd image: /boot/initrd.img-3.13.0-48-generic
Found linux image: /boot/vmlinuz-3.5.0-49-generic
Found initrd image: /boot/initrd.img-3.5.0-49-generic
Found memtest86+ image: /boot/memtest86+.elf
Found memtest86+ image: /boot/memtest86+.bin
Found Windows Recovery Environment (loader) on /dev/sda1
Found Windows 10 (loader) on /dev/sda3
done
vuletic@vuletic-Aspire-5735:~$ 

Да, без проблем

Нет, материнская плата Asus Prime Z390-p

Добавлено через 6 минут

Disk /dev/loop0: 956 KiB, 978944 bytes, 1912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop1: 134,1 MiB, 140652544 bytes, 274712 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop2: 198,9 MiB, 208551936 bytes, 407328 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop3: 131,9 MiB, 138330112 bytes, 270176 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop4: 4,2 MiB, 4403200 bytes, 8600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop5: 173,5 MiB, 181915648 bytes, 355304 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop6: 14,8 MiB, 15462400 bytes, 30200 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop7: 54,7 MiB, 57294848 bytes, 111904 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/nvme0n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 0DF5F3CC-A798-4FA5-8E1D-AE86D877B593

Device Start End Sectors Size Type
/dev/nvme0n1p1 2048 1085439 1083392 529M Windows recovery environment
/dev/nvme0n1p2 1085440 1290239 204800 100M EFI System
/dev/nvme0n1p3 1290240 1323007 32768 16M Microsoft reserved
/dev/nvme0n1p4 1323008 1000214527 998891520 476,3G Microsoft basic data

Disk /dev/nvme1n1: 477 GiB, 512110190592 bytes, 1000215216 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: C53E20EF-33E7-473E-AED2-24E26D945B8F

Device Start End Sectors Size Type
/dev/nvme1n1p1 2048 1050623 1048576 512M EFI System
/dev/nvme1n1p2 1050624 1000214527 999163904 476,4G Linux filesystem

Disk /dev/loop8: 44,9 MiB, 47063040 bytes, 91920 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop9: 89,1 MiB, 93417472 bytes, 182456 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop10: 3,7 MiB, 3825664 bytes, 7472 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop11: 160,2 MiB, 167931904 bytes, 327992 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/loop12: 173,8 MiB, 182272000 bytes, 356000 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Добавлено через 1 минуту

А вот это стоит проверить

Добавлено через 28 минут

Отключена

Hello!

I have reinstalled Windows 7 on my system, and now I get such strange error every time I boot it:

IMG_20170624_234018.jpg

This is my translation:

ERROR: no such device: 8AAA06CCAA06B52B
Setting partition type to 0x7
Press any key to continue…

Nevertheless Windows starts up normally after key pressed or time is out (about 5 seconds). And Linux works well (without any errors at all).
Now I should describe organization of my discs and mbrs: I have two physical hard drives for Linux and Windows, let’s call them hdd0 and hdd1. hdd0 is first boot disk in bios and contains Linux partitions and grub. hdd1 contains Windows partitions and Windows bootloader. Very simple. So, when I was reinstalling Windows, I changed boot priority in bios to boot from hdd1 first, so windows setup couldn’t erase grub. It’s worked, but now I have such error, which is just annoying.
My Linux is

Kernel: 4.4.0-53-generic x86_64 (64 bit)
Desktop: Cinnamon 3.2.7
Distro: Linux Mint 18.1 Serena

I decided that uuid have changed since windows setup formatted windows partition and checked this in my grub settings:

insmod part_msdos
insmod ntfs
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 --hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  8AAA06CCAA06B52B
else
  search --no-floppy --fs-uuid --set=root 8AAA06CCAA06B52B
fi
parttool ${root} hidden-
chainloader +1

«Ha!» I thought and changed it to new one (got with blkid) — CAF284CCF284BE67. But it changed nothing. I still have the same error and windows still loading after it normally.
So generally I can leave it as is, but I don’t like such disorder and wish to find how to fix such things. Moreover, it’s good opportunity to learn Linux a step deeper.
Thanks in advance!

I followed online tutorials to install Windows 10 alongside Linux (Arch) on separate HDDs. This involved physically disconnecting each HDD while installing the OS on the other.

The only thread I have found which doesn’t have the answer «use boot-repair» is this one except I have already installed Linux.

Below are my steps.

1. Disable fast boot and enable UEFI in BIOS
2. Create UEFI compatible live images of W10 and ArchLabs
3. Disconnect HDD0, install W10 Home onto HDD1
4. Disconnect HDD1, install ArchLabs onto HDD0 — grub is boot manager
5. Connect HDD1, boot into HDD0 using BIOS — only ArchLabs is listed as a boot option
6. Run grub-mkconfig -o /boot/grub/grub.cfg (update-grub) — Windows is found

Which outputs

Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: initramfs-linux-fallback.img
Found Windows Boot Manager on /dev/sdb2@/efi/Microsoft/Boot/bootmgfw.efi
Found memtest86+ image: /boot/memtest86+/memtest.bin
done

When I boot HDD0 in BIOS I see the Windows option in grub, but when I choose it I get this error

error: no such device: FA77-02BF.
error: disk `hd1,gpt2' not found.

Press any key to continue...

Some information

$sudo blkid
/dev/sda1: UUID="EFA1-BD6C" TYPE="vfat" PARTUUID="f1abfa2e-8f5e-4569-88a7-ebd5ebd1a737"
/dev/sda2: UUID="a43046c3-84ec-4308-9eaf-a872f1c4300d" TYPE="ext4" PARTUUID="c1a4e499-919d-4194-890f-459418430422"
/dev/sdb1: LABEL="Recovery" UUID="58CC724CCC722482" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="78b687ea-65f2-4c5a-9e2e-211c28298378"
/dev/sdb2: UUID="FA77-02BF" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="149fbe08-56e3-4dd7-9dde-b60e668a2253"
/dev/sdb4: UUID="50F28160F2814AE4" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="1e767b54-5723-4d51-889a-48108c2547fe"
/dev/sdb3: PARTLABEL="Microsoft reserved partition" PARTUUID="be54b5e0-7701-473a-aa31-bbc8919d62ae"

fstab hasn’t mounted sdb but im not sure it needs to?

$cat /etc/fstab
# /dev/sda2
UUID=a43046c3-84ec-4308-9eaf-a872f1c4300d   /           ext4        rw,relatime,data=ordered    0 1

# /dev/sda1
UUID=EFA1-BD6C          /boot/efi   vfat        rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro   0 2

/swapfile   none        swap        defaults,pri=-2 0 0

The problem I think lies in the fact that each HDD has its own EFI partition.

$fdisk -l
Disk /dev/sda: 298.1 GiB, 320072933376 bytes, 625142448 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 558CB70E-9540-49A2-87E9-728B9C3CDB16

Device       Start       End   Sectors   Size Type
/dev/sda1     2048   1050623   1048576   512M EFI System
/dev/sda2  1052672 625141759 624089088 297.6G Linux filesystem


Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 0676ACB7-16B9-4BBC-8030-D26B229EEF78

Device       Start       End   Sectors   Size Type
/dev/sdb1     2048   1023999   1021952   499M Windows recovery environment
/dev/sdb2  1024000   1228799    204800   100M EFI System
/dev/sdb3  1228800   1261567     32768    16M Microsoft reserved
/dev/sdb4  1261568 976773119 975511552 465.2G Microsoft basic data

At the moment I can use the BIOS to select the HDD I want to boot which in turn uses that HDDs bootmanager to launch its respective OS. But of course it would be nice to have BIOS boot to the same drive each time so I can select the OS through GRUB.