Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have an Ubuntu 15.10 running on a MSI B75MA-P45 motherboard with a number of connected SATA discs. (plus one external USB-disc)
I have a small 200 GB as boot disc, one 250 GB which I have emptied and two 3TB discs for media. (plus one small 80 GB disc that doesn't even show up on my system).
Anyway, the two 80GB and 250 GB are not used so I want to remove them to reduce the heat in the box.
My problem is that when I remove them, my systems fails to boot and I get stuck in a boot menu with several options of older kernels to boot with, none of will boot though.
The only way I can boot my system is to reconnect the two drives again
This starts to drive me nuts!
Does anyone heard of this before and can point me in a direction for a solution?
The only way I can boot my system is to reconnect the two drives again
Your system uses the boot sector of either the 80Gb or 250Gb. Check which. You can tell it by removing only one of the two, which of them boots.
The clean solution for this is to re-install the boot loader to the disk you wanted to dedicate, then can you only remove the two small disks and continue booting with the new bootloader at the dedicated disk. If you are using grub then grub-install it to /dev/sda<dedicated> hard drive. Then "update-grub" to make it aware of available bootable kernels. When it is done... Remove the two hard drives, and... Reboot.
Hope that helps. Goodluck.
Last edited by malekmustaq; 02-04-2016 at 09:44 AM.
Distribution: Cinnamon Mint 20.1 (Laptop) and 20.2 (Desktop)
Posts: 1,673
Rep:
My thoughts...
All your disk mounts are held in fstab, when you disconnect a disk and try and reboot the system without it, it'll hang trying to mount a non-existent disk. You'll need to unmount your two drives and comment them out of fstab before shutting down, removing them and rebooting.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
I have another possible explanation: The system is identifying drives by node "for example /dev/sda1" and because the other drives are removed these have changed. So the system boots to GRUB then GRUB can't find anything to boot to because it's looking in the wrong place. First things I'd do is check that fstab is using labels or UUIDs rather than the node. It's still possible there will be an issue with GRUB but it's worth a try.
Distribution: several, but trying to get away from systemd while keeping KDE and KVM
Posts: 45
Rep:
Quote:
Originally Posted by Soadyheid
@ Pyrotech72
From this I take that the Op doesn't have /, /boot or /usr on either of the two disks. Will initrd still overide fstab?
Play Bonny!
Those three are mounted with the information in initrd. (It has to know where / is to find fstab.) Hopefully, initrd doesn't search by node. I don't yet know enough about it to know whether it ever would.
Quote:
Originally Posted by 273
I have another possible explanation: The system is identifying drives by node "for example /dev/sda1" and because the other drives are removed these have changed. So the system boots to GRUB then GRUB can't find anything to boot to because it's looking in the wrong place. First things I'd do is check that fstab is using labels or UUIDs rather than the node. It's still possible there will be an issue with GRUB but it's worth a try.
Yes, the fstab is the first place to check. Try that first, along with making sure grub is installed on the desired device. Then only if we have to we'll see what we can do about initrd.
I don't know if you can help me out here, but this is what my fstab looks like:
# / was on /dev/sda2 during installation
UUID=2b96cae3-ec03-4137-ade5-cded72fc182a / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=D954-A1A4 /boot/efi vfat defaults 0 1
# swap was on /dev/sda3 during installation
UUID=9075da08-c6a0-4ff7-84c4-6f0ea12ed1e4 none swap sw 0 0
# second disk
/dev/sdb1 /media/Filmer ext4 defaults 0 2
sda1, sda2 and sda3 are on the same physical disc
sdb1 is the one I want to remove (or sdb to be more precise since all partitions are removed from that disk) so I can remove that entry from the fstab, right?
The big problem I have is that the 80GB disc doesn't appear anywhere, neither in Ubuntu nor in BIOS.
Distribution: Debian Sid AMD64, Raspbian Wheezy, various VMs
Posts: 7,680
Rep:
Your fstab is using UUIDs so that looks fine. Yes, you could comment out the entry for sdb1 in fstab -- it could also just be that the boot process is failing because it can't mount that drive which happens sometimes.
Distribution: several, but trying to get away from systemd while keeping KDE and KVM
Posts: 45
Rep:
Quote:
Originally Posted by 273
Your fstab is using UUIDs so that looks fine. Yes, you could comment out the entry for sdb1 in fstab -- it could also just be that the boot process is failing because it can't mount that drive which happens sometimes.
agreed.
# second disk
#/dev/sdb1 /media/Filmer ext4 defaults 0 2
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.