Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #177992 > unrolled thread
| Started by | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| First post | 2017-02-19 13:40 +0100 |
| Last post | 2017-02-19 23:50 +0100 |
| Articles | 7 — 5 participants |
Back to article view | Back to linux.debian.user
Fstab Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2017-02-19 13:40 +0100
Re: Fstab Problem Hans <hans.ullrich@loop.de> - 2017-02-19 13:50 +0100
Re: Fstab Problem Andy Smith <andy@strugglers.net> - 2017-02-19 13:50 +0100
Re: Fstab Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2017-02-19 14:20 +0100
Re: Fstab Problem Frank <zuiderduin@gmx.com> - 2017-02-19 14:00 +0100
Re: Fstab Problem Jimmy Johnson <field.engineer@gmail.com> - 2017-02-19 19:50 +0100
Re: Fstab Problem "Stephen P. Molnar" <s.molnar@sbcglobal.net> - 2017-02-19 23:50 +0100
| From | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| Date | 2017-02-19 13:40 +0100 |
| Subject | Fstab Problem |
| Message-ID | <tcyWt-7nn-9@gated-at.bofh.it> |
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
[toc] | [next] | [standalone]
| From | Hans <hans.ullrich@loop.de> |
|---|---|
| Date | 2017-02-19 13:50 +0100 |
| Message-ID | <tcz69-7qN-1@gated-at.bofh.it> |
| In reply to | #177992 |
Am Sonntag, 19. Februar 2017, 07:37:50 CET schrieb Stephen P. Molnar: Hi Stepehen, did you try, to enter just the devices (like /dev/sda1, dev/sdb1 etc.) instead of using UUID? If that is working, try to add the UUID later. Asd far as I know, there is also a kernel parameter, which inhibits to check for UUIDs. I blieve, it is nouuid, but I am not sure. I would think in that direction, maybe the UUIDs are wrong. Good luck! Hans > 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.
[toc] | [prev] | [next] | [standalone]
| From | Andy Smith <andy@strugglers.net> |
|---|---|
| Date | 2017-02-19 13:50 +0100 |
| Message-ID | <tcz6a-7qN-7@gated-at.bofh.it> |
| In reply to | #177992 |
Hi Stephen, On Sun, Feb 19, 2017 at 07:37:50AM -0500, Stephen P. Molnar wrote: > # <file system> <mount point> <type> <options> <dump> <pass> […] > #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 You've put the device path (e.g. /dev/sdb2) in the second column instead of the mount point. Since you've specified UUID you don't need to specify device path. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting
[toc] | [prev] | [next] | [standalone]
| From | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| Date | 2017-02-19 14:20 +0100 |
| Message-ID | <tczzb-7PQ-1@gated-at.bofh.it> |
| In reply to | #177994 |
On 02/19/2017 07:43 AM, Andy Smith wrote: > Hi Stephen, > > On Sun, Feb 19, 2017 at 07:37:50AM -0500, Stephen P. Molnar wrote: >> # <file system> <mount point> <type> <options> <dump> <pass> > > […] > >> #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 > > You've put the device path (e.g. /dev/sdb2) in the second column > instead of the mount point. Since you've specified UUID you don't > need to specify device path. > > Cheers, > Andy > That solved the problem. Many thanks. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set www.molecular-modeling.net Stochastic and multivariate (614)312-7528 (c) Skype: smolnar1
[toc] | [prev] | [next] | [standalone]
| From | Frank <zuiderduin@gmx.com> |
|---|---|
| Date | 2017-02-19 14:00 +0100 |
| Message-ID | <tczfQ-7u2-7@gated-at.bofh.it> |
| In reply to | #177992 |
Op 19-02-17 om 13:37 schreef Stephen P. Molnar: > #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. Somehow I don't think you can use the device name as mountpoiint (i.e. you're mounting /dev/sdb1 on /dev/sdb1...). Also, the sixth field of fstab lines is only supposed to be 1 for the root filesystem. Others should have 2 (or 0 if you don't want the check to run at all). Regards, Frank
[toc] | [prev] | [next] | [standalone]
| From | Jimmy Johnson <field.engineer@gmail.com> |
|---|---|
| Date | 2017-02-19 19:50 +0100 |
| Message-ID | <tcEIx-2pO-9@gated-at.bofh.it> |
| In reply to | #177992 |
On 02/19/2017 04:37 AM, Stephen P. Molnar wrote: > 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 I multi-boot and I like to keep things simple, including grub, I like a neat menu.lst and fstab too and I always keep these things backed up while installing a new system, this is the way I would do your fstab so I can edit sdb1 and sdb2, note no auto mount on sdb1 and sdb2, but you can now read and write. /dev/sda1 / ext4 errors=remount-ro 0 1 /dev/sda5 none swap sw 0 0 /dev/sdb1 /mnt/sdb1 ext4 noauto,users,exec,relatime 0 0 /dev/sdb2 /mnt/sdb2 ext4 noauto,users,exec,relatime 0 0 /dev/sr0 /media/cdrom udf,iso9660 noauto,users 0 0 If you use the above you will need to make two folders in /mnt named sdb1 and sdb2 > What have I missed? I don't think you missed anything, just didn't know what you where doing. :) > Thanks in advance. regard, -- Jimmy Johnson Debian Sid/Testing - Plasma 5.8.4 - EXT4 at sda15 Registered Linux User #380263
[toc] | [prev] | [next] | [standalone]
| From | "Stephen P. Molnar" <s.molnar@sbcglobal.net> |
|---|---|
| Date | 2017-02-19 23:50 +0100 |
| Message-ID | <tcIsN-4KT-9@gated-at.bofh.it> |
| In reply to | #178003 |
On 02/19/2017 01:39 PM, Jimmy Johnson wrote: > On 02/19/2017 04:37 AM, Stephen P. Molnar wrote: >> 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 > > I multi-boot and I like to keep things simple, including grub, I like a > neat menu.lst and fstab too and I always keep these things backed up > while installing a new system, this is the way I would do your fstab so > I can edit sdb1 and sdb2, note no auto mount on sdb1 and sdb2, but you > can now read and write. > > /dev/sda1 / ext4 errors=remount-ro 0 1 > /dev/sda5 none swap sw 0 0 > /dev/sdb1 /mnt/sdb1 ext4 noauto,users,exec,relatime 0 0 > /dev/sdb2 /mnt/sdb2 ext4 noauto,users,exec,relatime 0 0 > /dev/sr0 /media/cdrom udf,iso9660 noauto,users 0 0 > > If you use the above you will need to make two folders in /mnt named > sdb1 and sdb2 > >> What have I missed? > > I don't think you missed anything, just didn't know what you where > doing. :) > >> Thanks in advance. > > regard, Not know what I'm doing is nothing new. That's hardly a useful response. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set www.molecular-modeling.net Stochastic and multivariate (614)312-7528 (c) Skype: smolnar1
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.user
csiph-web