UberStudent Forums

US installed flawlessly for me. When I rebooted back into my Debian 7 it dropped to the Command Line. My first investigation showed no partitions and 0 files in home Directory. (Somehow I managed not to panic...*) A little thought and reading later, I remembered the partition I installed US on was listed in my Debian /etc/fstab. When I deleted the pertinent line in the fstab file, Debian booted normally. I can only conclude I should have thought of this before installing UB along side Debian.

Moderators, please edit this if I am not being clear or technically correct. I don't want to mislead anyone.

Susan in northern BC Canada
*my husband called it total shock not calm assurance my life was still safe and a little thought would allow me to access it again ...

To get a system that dual-boots Debian and UberStudent (or any other Ubuntu-based system), do this:

1) Install the Ubuntu-based system.
2) Install Debian, but do not to install the grub bootloader from Debian when you do so.
3) Boot in to the Ubuntu-based system and run the following from a terminal:


Done. Both systems should now be boot options in the boot menu.

Alternately, just run Debian in a Virtual machine on your Ubuntu-based host.

_________________
UberStudent Must Become Self-Sustaining. If UberStudent and my dedicated support of it has benefited you, it's important to make a donation. Thanks!

The UberStudent Headquarters:

* Mobo: MSI 870-G45
* Processor: AMD Phenom II X4 3.4GHz
* RAM: G.SKILL 8GB DDR3 1600
* Graphics: MSI NVIDIA GeForce GTX 750 Ti
* Drive: OCZ Vertex SSD
* Case: Rosewill ATX Mid Tower
* Monitors: 2 x Dell UltraSharp
* With UberStudent 4.3 Development Build

You should build your own computers, too!

I have a larger hard drive ordered, so I will be doing a clean load. I had not thought of running either in a virtual environment. It is something I will definitely look into.

Susan

It's not taken for granted that it should cause Debian problems booting if it mounts a partition that has another OS on it.
Stephen's instructions seem to be about making sure to get each OS to be properly written to Grub (the bootloader). However, that is not necessarily linked to problems /etc/fstab.
If you have problems mounting partitions and drives, it's always a good idea to post the contents of your /etc/fstab in your support request. Also, the respective outputs of:
,
and can be helpful, so make sure you get that information if you experience any more problems.
Afaik, the standard method for mounting in /etc/fstab is by device name (e.g. /dev/sdb1), but I prefer to use LABELS, as they won't change (device names are managed by the kernel and CAN change, e.g. if you boot from a removable drive) unless I do it myself, they're easy to remember and can be made meaningful (unlike UUIDs, for instance). You can assign LABELS using Gparted or gnome-disk-utility, which I find very useful.
This should be helpful for fixing Debian automounts: https://wiki.debian.org/fstab
, and this for Ubuntu and US: https://help.ubuntu.com/community/Fstab