This will probably turn out to be a forehead slapping red faced problem,
but this used to work.
I Had a Debian v-8.x catastrophe and had to reinstall. I have several
hard drives on the computer and, of course the installer only found
/dev/sda.
Here are the results of blkid:
comp@AbNormal:~$ sudo blkid
[sudo] password for comp:
/dev/sdb1: UUID="d65867da-c658-4e35-928c-9dd2d6dd5742" TYPE="ext4"
PARTUUID="0003d403-01"
/dev/sdb2: UUID="007c1f16-34a4-438c-9d15-e3df601649ba" TYPE="ext4"
PARTUUID="0003d403-02"
/dev/sda1: UUID="3a2e7e1d-3365-447b-85c5-f454a2f0b446" TYPE="ext4"
PARTUUID="cdf775c6-01"
/dev/sda5: UUID="92727ce9-2cff-40f5-b6d0-e9580afdeef3" TYPE="swap"
PARTUUID="cdf775c6-05"
I edited 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).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda1 during installation
UUID=3a2e7e1d-3365-447b-85c5-f454a2f0b446 / ext4
errors=remount-ro 0 1
# swap was on /dev/sda5 during installation
UUID=92727ce9-2cff-40f5-b6d0-e9580afdeef3 none swap sw
0 0
/dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0
#UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdb1 ext4
errors=remount-ro 0 1
#UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdb2 ext4
errors=remount-ro 0 1
The problem is, that when I reboot the system it doesn't like the new
fstab entries and halts. It's easy to fix in recovery mode by
commenting out the new lines, but that doesn't solve the problem.
My computer log doesn't record what actions I might had to take to get
this to work the last time it. happened.
What have I missed?
Thanks in advance.
--
Stephen P. Molnar, Ph.D. Life is a fuzzy set
www.molecular-modeling.net Stochastic and multivariate
(614)312-7528 (c)
Skype: smolnar1
