Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #248010 > unrolled thread

Re: fstab problem [FIXED]

Started byghe2001 <ghe2001@protonmail.com>
First post2022-05-09 00:10 +0200
Last post2022-05-09 19:30 +0200
Articles 7 — 4 participants

Back to article view | Back to linux.debian.user

Contents

  Re: fstab problem [FIXED] ghe2001 <ghe2001@protonmail.com> - 2022-05-09 00:10 +0200
    Re: fstab problem [FIXED] David Wright <deblis@lionunicorn.co.uk> - 2022-05-09 01:00 +0200
      Re: fstab problem [FIXED] ghe2001 <ghe2001@protonmail.com> - 2022-05-09 01:10 +0200
    Re: fstab problem [FIXED] David <bouncingcats@gmail.com> - 2022-05-09 01:40 +0200
      Re: fstab problem [FIXED] David Wright <deblis@lionunicorn.co.uk> - 2022-05-09 02:50 +0200
    Re: fstab problem [FIXED] David Christensen <dpchrist@holgerdanske.com> - 2022-05-09 08:40 +0200
      Re: fstab problem [FIXED] David Wright <deblis@lionunicorn.co.uk> - 2022-05-09 19:30 +0200

#248010 — Re: fstab problem [FIXED]

Fromghe2001 <ghe2001@protonmail.com>
Date2022-05-09 00:10 +0200
SubjectRe: fstab problem [FIXED]
Message-ID<EkXge-eb8l-3@gated-at.bofh.it>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256






------- Original Message -------
On Sunday, May 8th, 2022 at 3:51 PM, David Christensen <dpchrist@holgerdanske.com> wrote:

> My bad -- default options is spelled 'defaults'.
>
> UUID=301d6d6d-6782-4be3-b979-0cb595ef1a48 /backupDisk ext4 defaults 0 0

Well, damned if it didn't work.  And I had all of my non-root fstab entries with singular defaults too.  Thanks vastly, David.

--
Glenn English

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJieD1fACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDL9+wgAx0upe2HuSvPTsfL7O5c1hbWfR9Kz2O8ASeRanYgWVpbPALZj
Y83gVlOM5yCxdFid31eoJ9JEmUFtklZSqDTnAxZCzLOJS/j9G3KSKFaJG5fI
jO3O969WcUfM0/LufJrXI6Wwsj2xyJg1hplVWqK2j/qLsmLyE8U+9Y8I5WIU
WayypmyFTlupOkG47CVVDoi4zbxB36QN0Oi0NRrdnM85UWbhIkG1FzJ5P62W
byjlUQlYQd2jh2vS25vB+XcD5Npj5t/9TUT1zLgsQ8WyVb8JUNM9Dz/OX7bk
qXWW+QeAbTFApFos2cW22unNVSnDSXmakfdRwXNjXHrNcQPBhRQWKQ==
=Xfb8
-----END PGP SIGNATURE-----

[toc] | [next] | [standalone]

#248012

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-05-09 01:00 +0200
Message-ID<EkY2C-eboV-3@gated-at.bofh.it>
In reply to#248010
On Sun 08 May 2022 at 22:00:23 (+0000), ghe2001 wrote:
> On Sunday, May 8th, 2022 at 3:51 PM, David Christensen <dpchrist@holgerdanske.com> wrote:
> 
> > My bad -- default options is spelled 'defaults'.
> >
> > UUID=301d6d6d-6782-4be3-b979-0cb595ef1a48 /backupDisk ext4 defaults 0 0
> 
> Well, damned if it didn't work.  And I had all of my non-root fstab entries with singular defaults too.

My proof reading of the options was obviously worse than your
pasting of the UUID (I thought you might have accidentally
chosen to use the PARTUUID).

But I get the same failure from "default" whether I use
/dev/sdX, UUID, or LABEL. And lest systemd is involved,
I followed all my fstab changes with:
# systemctl daemon-reload.
So I don't know where your:

/dev/sde1                                       /backupDisk     ext4    default                 0       0

came from.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#248014

Fromghe2001 <ghe2001@protonmail.com>
Date2022-05-09 01:10 +0200
Message-ID<EkYch-ebHD-3@gated-at.bofh.it>
In reply to#248012
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256





------- Original Message -------
On Sunday, May 8th, 2022 at 4:57 PM, David Wright <deblis@lionunicorn.co.uk> wrote:

> My proof reading of the options was obviously worse than your
> pasting of the UUID (I thought you might have accidentally
> chosen to use the PARTUUID).
>
> But I get the same failure from "default" whether I use
> /dev/sdX, UUID, or LABEL. And lest systemd is involved,
> I followed all my fstab changes with:
> # systemctl daemon-reload.
> So I don't know where your:
>
> /dev/sde1 /backupDisk ext4 default 0 0
>
> came from.

Nor do I, but I'm suspecting bewilderment :-)

--
Glenn English

-----BEGIN PGP SIGNATURE-----
Version: ProtonMail

wsBzBAEBCAAGBQJieEwSACEJEJ/XhjGCrIwyFiEELKJzD0JScCVjQA2Xn9eG
MYKsjDKe7gf/fQGSyNTyaaJJkQyXX6Y0/nIOrjO4gwo/VAcMa+nLFxLQI5iB
8+zglojEzi/o8nqoCU/MegzFtyF5r+fcEbKwyHbLUdjri948AAzkzXKCZEw3
fnFwVpo+R2B7hiaf+0XeGQUiCiHKoYAbuu7uoIQwvdlikMLO+ukXJEeHeQBm
X3a6ZJsflG9OsmS079UE41sonWn94jx38YSwm0Smfr12isEpAIpF8+9EE5Ax
Hn51u/MlWCw5+xNs0aCYFCegGTJmluAqi5jHPnpO+p2/4eS5qpEYXDj9roh+
FcyHqz2nTxERS+XVRaLt6e7ph+F25P1cihUHRwSbmBQm8EIGj7HTKg==
=1cOw
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#248015

FromDavid <bouncingcats@gmail.com>
Date2022-05-09 01:40 +0200
Message-ID<EkYFj-ebQy-3@gated-at.bofh.it>
In reply to#248010
On Mon, 9 May 2022 at 05:30, ghe2001 <ghe2001@pm.me> wrote:

> The fstab:
> # <file system>                                 <mount point>   <type>  <options>               <dump>  <pass>

On Mon, 9 May 2022 at 08:00, ghe2001 <ghe2001@protonmail.com> wrote:

> > My bad -- default options is spelled 'defaults'.
> >
> > UUID=301d6d6d-6782-4be3-b979-0cb595ef1a48 /backupDisk ext4 defaults 0 0
>
> Well, damned if it didn't work.  And I had all of my non-root fstab entries with singular defaults too.  Thanks vastly, David.

The only reason to that <options>=defaults exists is so that
a non-default value can be specified for either <dump> or <pass>,
while not specifying any non-default <options>.

Because there can't be a fifth or sixth column unless there is
also a fourth column. "defaults" is just a dummy value for the
fourth column.

Using "defaults 0 0" is specifying default value for all three
of <options>, <dump>, and <pass>.

In that situation, they can all be omitted.

[toc] | [prev] | [next] | [standalone]

#248019

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-05-09 02:50 +0200
Message-ID<EkZL4-ecvG-3@gated-at.bofh.it>
In reply to#248015
On Mon 09 May 2022 at 09:34:56 (+1000), David wrote:

> The only reason to that <options>=defaults exists is so that
> a non-default value can be specified for either <dump> or <pass>,
> while not specifying any non-default <options>.
> 
> Because there can't be a fifth or sixth column unless there is
> also a fourth column. "defaults" is just a dummy value for the
> fourth column.
> 
> Using "defaults 0 0" is specifying default value for all three
> of <options>, <dump>, and <pass>.
> 
> In that situation, they can all be omitted.

I think a jolly good default for field 4 is errors=remount-ro,
which I use everywhere (bar /dev/sr0), even where it results
in the tautological, but harmless, ro,errors=remount-ro.

Cheers,
David.

[toc] | [prev] | [next] | [standalone]

#248033

FromDavid Christensen <dpchrist@holgerdanske.com>
Date2022-05-09 08:40 +0200
Message-ID<El5dL-egJe-3@gated-at.bofh.it>
In reply to#248010
On 5/8/22 15:00, ghe2001 wrote:

> On Sunday, May 8th, 2022 at 3:51 PM, David Christensen wrote:
> 
>> My bad -- default options is spelled 'defaults'.
> 
>> UUID=301d6d6d-6782-4be3-b979-0cb595ef1a48 /backupDisk ext4 defaults 0 0
> 
> Well, damned if it didn't work.  And I had all of my non-root fstab entries with singular defaults too.  Thanks vastly, David.


YW.


One character present, absent, or different is all it takes.


And, the error messages may or may not be helpful.


Related -- beware of "sda" vs. "sdb" in Debian 11 configuration files. 
As noted by another reader in another thread, the Debian 11 installer 
appears to always assign /dev/sda to d-i USB installation media; in 
spite of decades of standard practice of using the first drive node for 
the target drive.  Thus, the target drive may have been /dev/sdb at 
installation time, resulting in "sdb" in crypttab(5) and/or fstab(5) 
entries rather than the conventional "sda".  This break with convention 
cost me at least an hour of frustration recently, and I almost posted to 
this list.


David

[toc] | [prev] | [next] | [standalone]

#248044

FromDavid Wright <deblis@lionunicorn.co.uk>
Date2022-05-09 19:30 +0200
Message-ID<ElfmN-emQS-5@gated-at.bofh.it>
In reply to#248033
On Sun 08 May 2022 at 23:39:31 (-0700), David Christensen wrote:
> On 5/8/22 15:00, ghe2001 wrote:
> > On Sunday, May 8th, 2022 at 3:51 PM, David Christensen wrote:
> > 
> > > My bad -- default options is spelled 'defaults'.
> > 
> > > UUID=301d6d6d-6782-4be3-b979-0cb595ef1a48 /backupDisk ext4 defaults 0 0
> > 
> > Well, damned if it didn't work.  And I had all of my non-root fstab entries with singular defaults too.  Thanks vastly, David.
> 
> YW.
> 
> One character present, absent, or different is all it takes.
> And, the error messages may or may not be helpful.
> 
> Related -- beware of "sda" vs. "sdb" in Debian 11 configuration files.
> As noted by another reader in another thread, the Debian 11 installer
> appears to always assign /dev/sda to d-i USB installation media; in
> spite of decades of standard practice of using the first drive node
> for the target drive.  Thus, the target drive may have been /dev/sdb
> at installation time, resulting in "sdb" in crypttab(5) and/or
> fstab(5) entries rather than the conventional "sda".  This break with
> convention cost me at least an hour of frustration recently, and I
> almost posted to this list.

This is news to me, and I'm not sure why you blame the d-i's going
against decades of precedent. Yes, it can happen, and I guess it might
be the result of the way the buses are configured inside the machine.
Gone are the simple days of PATAs on hda.

Anyway, here are six machines: three are laptops, three EFIs, one AiO,
one i386, all GPT, all netinst, variously 11.1–3 with firmware. All
except the last have the installer on sdb, and the reason there is
obvious.

The sole occasion where the devices have been named the "wrong" way
round is when I installed Debian on an EFI laptop onto a virgin
external hard drive. If memory serves, the d-i was connected through
a hub to the USB-C port, the drive was on the single USB3 port.
I think.

$ grep -e sda -e sdb -e nvme /var/log/installer/syslog | sed -e '/CD-ROM/{p; q}'
Jan  1 16:29:18 kernel: [    1.815571] sd 1:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Jan  1 16:29:18 kernel: [    1.816244] sd 1:0:0:0: [sda] 4096-byte physical blocks
Jan  1 16:29:18 kernel: [    1.817495] sd 1:0:0:0: [sda] Write Protect is off
Jan  1 16:29:18 kernel: [    1.819103] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan  1 16:29:18 kernel: [    1.819791] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan  1 16:29:18 kernel: [    1.853168]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8 sda9 sda10 sda11
Jan  1 16:29:18 kernel: [    1.875612] sd 1:0:0:0: [sda] Attached SCSI disk
Jan  1 16:29:18 kernel: [    3.422080] sd 3:0:0:0: [sdb] 2006528 512-byte logical blocks: (1.03 GB/980 MiB)
Jan  1 16:29:18 kernel: [    3.422370] sd 3:0:0:0: [sdb] Write Protect is off
Jan  1 16:29:18 kernel: [    3.422372] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
Jan  1 16:29:18 kernel: [    3.422673] sd 3:0:0:0: [sdb] No Caching mode page found
Jan  1 16:29:18 kernel: [    3.422674] sd 3:0:0:0: [sdb] Assuming drive cache: write through
Jan  1 16:29:18 kernel: [    3.453581]  sdb: sdb1 sdb2
Jan  1 16:29:18 kernel: [    3.490735] sd 3:0:0:0: [sdb] Attached SCSI removable disk
Jan  1 16:29:55 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
Jan  1 16:29:55 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
$ 

$ grep -e sda -e sdb -e nvme /var/log/installer/syslog | sed -e '/CD-ROM/{p; q}'
Jan 25 21:12:08 kernel: [    4.310937] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Jan 25 21:12:08 kernel: [    4.310951] sd 0:0:0:0: [sda] Write Protect is off
Jan 25 21:12:08 kernel: [    4.310952] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Jan 25 21:12:08 kernel: [    4.310972] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Jan 25 21:12:08 kernel: [    4.681368]  sda: sda1 sda2 sda3 sda4 sda5 sda6
Jan 25 21:12:08 kernel: [    4.839485] sd 0:0:0:0: [sda] Attached SCSI disk
Jan 25 21:12:08 kernel: [    5.617893] sd 6:0:0:0: [sdb] 2006528 512-byte logical blocks: (1.03 GB/980 MiB)
Jan 25 21:12:08 kernel: [    5.637613] sd 6:0:0:0: [sdb] Write Protect is off
Jan 25 21:12:08 kernel: [    5.655705] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
Jan 25 21:12:08 kernel: [    5.656965] sd 6:0:0:0: [sdb] No Caching mode page found
Jan 25 21:12:08 kernel: [    5.674988] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Jan 25 21:12:08 kernel: [    5.718770]  sdb: sdb1 sdb2
Jan 25 21:12:08 kernel: [    5.762284] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Jan 25 21:13:04 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
Jan 25 21:13:04 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
$ 

$ grep -e sda -e sdb -e nvme /var/log/installer/syslog | sed -e '/CD-ROM/{p; q}'
Feb  1 17:32:10 kernel: [    5.562125] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Feb  1 17:32:10 kernel: [    5.569327] sd 0:0:0:0: [sda] Write Protect is off
Feb  1 17:32:10 kernel: [    5.576324] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Feb  1 17:32:10 kernel: [    5.576399] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Feb  1 17:32:10 kernel: [    5.646877]  sda: sda1 sda2 sda3 sda4 sda5 sda6
Feb  1 17:32:10 kernel: [    5.667737] sd 0:0:0:0: [sda] Attached SCSI disk
Feb  1 17:32:10 kernel: [    5.834514] sd 4:0:0:0: [sdb] 2006528 512-byte logical blocks: (1.03 GB/980 MiB)
Feb  1 17:32:10 kernel: [    5.849013] sd 4:0:0:0: [sdb] Write Protect is off
Feb  1 17:32:10 kernel: [    5.855644] sd 4:0:0:0: [sdb] Mode Sense: 03 00 00 00
Feb  1 17:32:10 kernel: [    5.856638] sd 4:0:0:0: [sdb] No Caching mode page found
Feb  1 17:32:10 kernel: [    5.863141] sd 4:0:0:0: [sdb] Assuming drive cache: write through
Feb  1 17:32:10 kernel: [    5.889163]  sdb: sdb1 sdb2
Feb  1 17:32:10 kernel: [    5.914390] sd 4:0:0:0: [sdb] Attached SCSI removable disk
Feb  1 17:32:45 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
Feb  1 17:32:45 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
$ 

$ grep -e sda -e sdb -e nvme /var/log/installer/syslog | sed -e '/CD-ROM/{p; q}'
Apr 17 01:01:15 kernel: [    1.835596] sd 0:0:0:0: [sda] 976773168 512-byte logical blocks: (500 GB/466 GiB)
Apr 17 01:01:15 kernel: [    1.837196] sd 0:0:0:0: [sda] 4096-byte physical blocks
Apr 17 01:01:15 kernel: [    1.838100] sd 0:0:0:0: [sda] Write Protect is off
Apr 17 01:01:15 kernel: [    1.838967] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr 17 01:01:15 kernel: [    1.838992] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 17 01:01:15 kernel: [    1.863206]  sda: sda1 sda2 sda3 sda4 sda5 sda6
Apr 17 01:01:15 kernel: [    1.888613] sd 0:0:0:0: [sda] Attached SCSI disk
Apr 17 01:01:16 kernel: [    3.120312] sd 6:0:0:0: [sdb] 2006528 512-byte logical blocks: (1.03 GB/980 MiB)
Apr 17 01:01:16 kernel: [    3.120785] sd 6:0:0:0: [sdb] Write Protect is off
Apr 17 01:01:16 kernel: [    3.120790] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
Apr 17 01:01:16 kernel: [    3.121108] sd 6:0:0:0: [sdb] No Caching mode page found
Apr 17 01:01:16 kernel: [    3.121111] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 17 01:01:16 kernel: [    3.143895]  sdb: sdb1 sdb2 sdb3
Apr 17 01:01:16 kernel: [    3.157941] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Apr 17 01:02:28 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
Apr 17 01:02:28 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
$ 

$ grep -e sda -e sdb -e nvme /var/log/installer/syslog | sed -e '/CD-ROM/{p; q}'
Apr 21 18:43:48 kernel: [    4.728919] sd 0:0:0:0: [sda] 117210240 512-byte logical blocks: (60.0 GB/55.9 GiB)
Apr 21 18:43:48 kernel: [    4.781174] sd 0:0:0:0: [sda] Write Protect is off
Apr 21 18:43:48 kernel: [    4.791354] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
Apr 21 18:43:48 kernel: [    4.853619] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Apr 21 18:43:48 kernel: [    5.284602]  sda: sda1 sda2 sda3 sda4
Apr 21 18:43:48 kernel: [    5.320578] sd 0:0:0:0: [sda] Attached SCSI disk
Apr 21 18:43:48 kernel: [    6.301453] sd 2:0:0:0: [sdb] 2006528 512-byte logical blocks: (1.03 GB/980 MiB)
Apr 21 18:43:48 kernel: [    6.314811] sd 2:0:0:0: [sdb] Write Protect is off
Apr 21 18:43:48 kernel: [    6.326835] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
Apr 21 18:43:48 kernel: [    6.328822] sd 2:0:0:0: [sdb] No Caching mode page found
Apr 21 18:43:48 kernel: [    6.340627] sd 2:0:0:0: [sdb] Assuming drive cache: write through
Apr 21 18:43:48 kernel: [    6.363150]  sdb: sdb1 sdb2 sdb3
Apr 21 18:43:48 kernel: [    6.387070] sd 2:0:0:0: [sdb] Attached SCSI removable disk
Apr 21 18:44:19 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
Apr 21 18:44:19 cdrom-detect: CD-ROM mount succeeded: device=/dev/sdb1 fstype=iso9660
$ 

$ grep -e sda -e sdb -e nvme /var/log/installer/syslog | sed -e '/CD-ROM/{p; q}'
Dec 13 03:02:14 kernel: [    0.874287] nvme nvme0: pci function 0000:3d:00.0
Dec 13 03:02:14 kernel: [    0.890575] nvme nvme0: 4/0/0 default/read/poll queues
Dec 13 03:02:14 kernel: [    0.892293]  nvme0n1: p1 p2 p3 p4
Dec 13 03:02:15 kernel: [    3.106803] sd 0:0:0:0: [sda] 2006528 512-byte logical blocks: (1.03 GB/980 MiB)
Dec 13 03:02:15 kernel: [    3.107444] sd 0:0:0:0: [sda] Write Protect is off
Dec 13 03:02:15 kernel: [    3.107450] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00
Dec 13 03:02:15 kernel: [    3.107907] sd 0:0:0:0: [sda] No Caching mode page found
Dec 13 03:02:15 kernel: [    3.107913] sd 0:0:0:0: [sda] Assuming drive cache: write through
Dec 13 03:02:15 kernel: [    3.125917]  sda: sda1 sda2
Dec 13 03:02:16 kernel: [    3.155962] sd 0:0:0:0: [sda] Attached SCSI removable disk
Dec 13 03:02:48 cdrom-detect: CD-ROM mount succeeded: device=/dev/sda1 fstype=iso9660
Dec 13 03:02:48 cdrom-detect: CD-ROM mount succeeded: device=/dev/sda1 fstype=iso9660
$ 

Cheers,
David.

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web