No bootable devices

I am trying to install Manjaro KDE in legacy mode as a second drive with a drive bay caddie in my laptop. I have ran Manjaro like this for a year on a previous SDD but now bought a bigger SSD and I can't get it to boot after install. It goes through the installation process perfectly but upon restart, it won't boot and gives me a "No bootable devices" icon. I believe it should be booting from hdd1 but When I look in the bios it doesn't recognize any drives exist and the error says:

attempt to read or write outside of disk 'hd0

I tried with Universal-USB-Installer-1.9.8.7 and Rufus 3.5 but neither worked. I used MBR partition scheme with Rufus but it wouldn't let me identify BIOS instead of UEFI as the target system. It also gave me a "download required" error that said this image uses Grub 2.03.4 but the application only includes the installation files for Grub 2.02.

This is what I'm seeing now:
https://drive.google.com/drive/folders/133bhK8ad1jHOMC3B-zcgAbpru9fOWnoS?usp=sharing

I don't remember it being this difficult last time I installed Manjaro. Am I missing something. Any ideas?

Thank you.

Hardware is good. I can see the files on the SSD. I also tried installing via Etcher and UEFI instead of Legacy and that didn't work either. My guess is it not seeing the correct disk when trying to boot. Been researching for 6 hours and still can't find an answer. So much for "enjoying the simplicity."

uses Etcher or imagewriter or isousb
or Rufus in DD mode only

Yep did that too

Actually Etcher doesn't even give you the option.

I think the ssd is crashed. :slightly_frowning_face:

No sir. But...I just tried it with "no boot loader" option and it worked. I'm back baby!

:+1: :smile:

Darn..it's still not booting properly. I was able to boot that one time where I configured my entire machine. I went to reboot now and same thing.

attempt to read or write outside of disk 'hd0

Is there anyone out who has come across this or someone that may be able to help me get my system to boot properly? It was running fine for the past 6 hours while I set up everything. It's just something with the boot.

Wonder if it's a timing thing with the Kernel? It booted that one time but now just gives the "no bootable device" icon (like in the picture I linked) immediately following the Acer splash screen.

Tried this and got the following error:

[manjaro@manjaro ~]$ sudo fdisk -l
Disk /dev/loop0: 18.1 MiB, 18948096 bytes, 37008 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: 274.6 MiB, 287969280 bytes, 562440 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: 1.1 GiB, 1229180928 bytes, 2400744 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: 475.5 MiB, 498573312 bytes, 973776 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/sda: 953.9 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SPCC Solid State
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: dos
Disk identifier: 0xcb281157

Device Boot Start End Sectors Size Id Type
/dev/sda1 2048 1964545565 1964543518 936.8G 83 Linux
/dev/sda2 1964545566 2000397734 35852169 17.1G 82 Linux swap / Solar

Disk /dev/sdb: 3.8 GiB, 4027580416 bytes, 7866368 sectors
Disk model: Flash Disk
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: dos
Disk identifier: 0x00000000

Device Boot Start End Sectors Size Id Type
/dev/sdb1 * 64 4094111 4094048 2G 0 Empty
/dev/sdb2 4094112 4102303 8192 4M ef EFI (FAT-12/16/32)
[manjaro@manjaro ~]$ lsblk -f
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
loop0 squashfs 0 100% /run/miso/sfs/
loop1 squashfs 0 100% /run/miso/sfs/
loop2 squashfs 0 100% /run/miso/sfs/
loop3 squashfs 0 100% /run/miso/sfs/
sda
├─sda1 ext4 6c24b07e-4272-4d87-ae63-17eb69f00a8b 859.4G 2% /run/media/man
└─sda2 swap ef46227c-08a3-4249-a43f-3818228c8e10
sdb iso9660 M1804 2019-03-12-09-50-33-00
├─sdb1 iso9660 M1804 2019-03-12-09-50-33-00 0 100% /run/miso/boot
└─sdb2 vfat MISO_EFI F464-EFAB
[manjaro@manjaro ~]$ sudo mount /dev/sda1 /mnt
[manjaro@manjaro ~]$ sudo pacman -Sy
:: Synchronizing package databases...
[manjaro@manjaro ~]$ sudo pacman -S mhwd-chroot
:: Some packages should be upgraded first...
resolving dependencies...
looking for conflicting packages...

Packages (2) manjaro-keyring-20190512-1 manjaro-system-20190429-1

Total Download Size: 0.13 MiB
Total Installed Size: 0.19 MiB
Net Upgrade Size: 0.03 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
manjaro-keyring-2019051... 126.9 KiB 1032K/s 00:00 [#############################] 100%
manjaro-system-20190429... 7.2 KiB 0.00B/s 00:00 [#############################] 100%
(2/2) checking keys in keyring [#############################] 100%
(2/2) checking package integrity [#############################] 100%
(2/2) loading package files [#############################] 100%
(2/2) checking for file conflicts [#############################] 100%
(2/2) checking available disk space [#############################] 100%
:: Processing package changes...
(1/2) upgrading manjaro-keyring [#############################] 100%
==> Appending keys from manjaro.gpg...
==> Locally signing trusted keys in keyring...
-> Locally signing key B4663188A692DB1E45A98EE95BD96CC4247B52CC...
-> Locally signing key 76C6E477042BFE985CC220BD9C08A255442FAFF0...
-> Locally signing key 7C89F4D439B2BFACF425107B62443D89B35859F8...
-> Locally signing key 1E7908935AAB9A00D6B47503363DFFFD59152F77...
-> Locally signing key 04BB537F5BC2D399BFA72F8F17C752B61B2F2E90...
-> Locally signing key 5A97ED6B72418199F0C22B23137C934B5DCB998E...
-> Locally signing key 75C1B95A4D9514A57EB2DAE71817DC63CD3B5DF5...
-> Locally signing key 39F0EC1AE50B37E5F3196F09DAD3B211663CA268...
-> Locally signing key 2D14560CDCE6A75BB186DB758238651DDF5E0594...
-> Locally signing key 7A443CEE69B6B3777740E258084A7FC0035B1D49...
-> Locally signing key F66AD0FF0E57C561615A0901CEE477135C5872B0...
-> Locally signing key 35B4FF23EA9477582C2A0AF12B80869C5C0102A6...
-> Locally signing key E4CDFE50A2DA85D58C8A8C70CAA6A59611C7F07E...
-> Locally signing key 74C2F2CC05A0AB7D859839938934292D604F8BA2...
-> Locally signing key 77DC01C9971AC3C39A0626F72C089F09AC97B894...
-> Locally signing key 16DC688DF3EECC72323954237EC47C82A42D53A2...
-> Locally signing key 2C688B52E3FC0144B7484BABE3B3F44AC45EE0AA...
-> Locally signing key 22C903DE964E6FE321656E318DB9F8C18DF53602...
==> Importing owner trust values...
gpg: setting ownertrust to 4
gpg: setting ownertrust to 4
==> Disabling revoked keys in keyring...
-> Disabling key 540DE7083B89314CF70EA6F0C1B1AD0DA80EBF3E...
-> Disabling key FAA6840E8C3FC7F89BEE0DC8AC7AB10BCB6CDD17...
==> Updating trust database...
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 1EB2638FF56C0C53: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: key 786C63F330D7CB92: no user ID for key signature packet of class 10
gpg: marginals needed: 3 completes needed: 1 trust model: pgp
gpg: depth: 0 valid: 1 signed: 24 trust: 0-, 0q, 0n, 0m, 0f, 1u
gpg: depth: 1 valid: 24 signed: 75 trust: 0-, 0q, 0n, 24m, 0f, 0u
gpg: depth: 2 valid: 75 signed: 7 trust: 75-, 0q, 0n, 0m, 0f, 0u
gpg: next trustdb check due at 2019-06-02
(2/2) upgrading manjaro-system [#############################] 100%
==> adjusting file permissions for Accountsservice 0.6.55 ...
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...

resolving dependencies...
looking for conflicting packages...

Packages (1) mhwd-chroot-20180408-1

Total Download Size: 0.01 MiB
Total Installed Size: 0.02 MiB

:: Proceed with installation? [Y/n] y
:: Retrieving packages...
mhwd-chroot-20180408-1-any 6.6 KiB 0.00B/s 00:00 [#############################] 100%
(1/1) checking keys in keyring [#############################] 100%
(1/1) checking package integrity [#############################] 100%
(1/1) loading package files [#############################] 100%
(1/1) checking for file conflicts [#############################] 100%
(1/1) checking available disk space [#############################] 100%
:: Processing package changes...
(1/1) installing mhwd-chroot [#############################] 100%
Optional dependencies for mhwd-chroot
gksu: gnome gui for su
kdesu: kde gui for su [installed]
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Updating the desktop file MIME type cache...
[manjaro@manjaro ~]$ sudo mhwd-chroot
konsole --separate -e mhwd-chroot-shell

/dev/sda1
swapon UUID=ef46227c-08a3-4249-a43f-3818228c8e10
[manjaro /]# cd /mnt
[manjaro mnt]# grub-install /dev/sda --boot-directory=/mnt/boot
Installing for i386-pc platform.
Installation finished. No error reported.
[manjaro mnt]# update-grub
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-4.19-x86_64
Found initrd image: /boot/intel-ucode.img /boot/initramfs-4.19-x86_64.img
Found initrd fallback image: /boot/initramfs-4.19-x86_64-fallback.img
grub-probe: error: cannot find a GRUB drive for /dev/sdb1.  Check your device.map.
Found memtest86+ image: /boot/memtest86+/memtest.bin
done
[manjaro mnt]# 

Not contributing much here and I've never used a caddie bay, but I think it is a hardware issue.

Your caddy may be sata II and your drive in sata III or just a faulty caddy. If it is the former, try switching drives. Can your old previous SSD drive be detected by bios? Oh..just how big is your new SSD? Bigger than 2 TB? :grin: Obviously with your setup, it cannot handle > 2 TB. But if it is smaller than 2 TB and if old drive works in it (now as well), it may very well be a sata speed issue. You may want to switch your internal drive and that new ssd drive and see if the bios detect it.

Of course, anything the bios cannot see won't boot.
But good luck.

I don't know. I've used the caddie just fine and I was able to install just fine and when it did boot that one time I was able to configure the whole system on that drive just fine. It could be bios but my old SSD is fine in the caddie. It's a new 1TB drive. I knew I should have tried to reboot before I spent 6 hours configuring the system. Kind of at a loss if even the experts can't figure it out. Maybe I'll clonezilla to another SSD and see if that works? I don't know. I'm kinda at wits end.

So it is just the new SSD in the caddie.
So

Meaning... Put your internal drive in the caddy and the new SSD as internal drive.
(but watch out at booting after you do that, select the bios to pick the caddie to boot caddie drive then fix boot sequence or fix boot loader drive).

Forget clonezilla. It won't help in this issue.

BTW, I am not an expert in hardware. And I told you I've never used a caddy bay. I've never heard anyone say they are experts, here.
And this forum does not say we can fix hardware issues.
.

Thanks gohlip, you are leading me in the right direction. I put my old drive in WITH the other main drive and it booted. So I put the new drive in and Now I get this

Well, if you see this use this.
You may need to boot up using the more complicated set up procedure, not the simple set up procedure.

I get another error loading the kerel

Perhaps you're right the bios just doesn't like that SSD.

Nope the SSD is fine because I just tried to install Majaro on another SSD that I had previously had Ubuntu running just fine for years and it's doing the same thing on that SSD. I verified the checksum on the USB and the image is correct. Starting to think something is wrong with this version of Manjaro.

Chet, as said, I don't use caddies and I'm no hardware expert.
I may think it is your sata II and sata III because your caddie works on another system with the old drive. But I cannot proclaim to know it as fact.

I've not replied in this topic earlier but have done so because you PM'ed me to look into this which I did. I will have to withdraw as I have nothing new to contribute. Sorry to disappoint but wish you all the best.

Cheers, take care.

ps: why is your first screen shot grub version 2.03.6 ~manjaro
and the second screen shot grub version 2.03.4 ?

1 Like

Forum kindly sponsored by Bytemark