Re: Problem Mounting New Drives
On Sun, Aug 19, 2018 at 09:10:10PM +0200, john doe wrote: > On 8/19/2018 8:59 PM, Stephen P. Molnar wrote: > > > > > > On 08/19/2018 02:28 PM, Reco wrote: > > > Hi. > > > > > > On Sun, Aug 19, 2018 at 02:04:39PM -0400, Stephen P. Molnar wrote: > > > > > > Note that second field is a mountpoint in fstab(5), as one of the stock > > > records show: > > > > > > > UUID=8f4eeaae-a055-4262-bebb-cf99abe982a5 /var ext4 defaults > > > > 0 2 > > > Yours have a block device name instead of mountpoint: > > > > > > > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /dev/sdb1 ext4 > > > > errors=remount-ro 0 > > > > 1 > > > > UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdc1 ext4 > > > > errors=remount-ro 0 > > > > 1 > > > > UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdc2 ext4 > > > > errors=remount-ro 0 > > > > 1 > > > So even a stock mount(1) should refuse to mount these. > > > > > > > > > > When I rebooted the computer the OS didn't like the new > > > > fstab and gave me a > > > > number of, at least to me, obscure messages. > > > systemd-mount can be cryptic, I agree. > > > > > > > > > > Obviously, I missed something important. My question is what? > > > It's a kind of dumb question, but where do you need your sdb1, sdc1 and > > > sdc2 mounted? Your fstab(5) does not mention that. > > > > > > Reco > > > > > > > > Well, that's another red faced forehead slapper! > > > > It merely reinforces that I don't know what I'm doing as far as > > hardware is concerned. > > > > It's a good thing that I'm an Organic Chemist and not an IT person. > > > > Instead of trying your new changes in '/etc/fstab' by rebooting, you > could also try 'mount -a'. Or # findmnt -x > https://linux.die.net/man/8/mount > > -- > John Doe Regards -- Felipe Salvador
Re: Problem Mounting New Drives
On 8/19/2018 8:59 PM, Stephen P. Molnar wrote: On 08/19/2018 02:28 PM, Reco wrote: Hi. On Sun, Aug 19, 2018 at 02:04:39PM -0400, Stephen P. Molnar wrote: Note that second field is a mountpoint in fstab(5), as one of the stock records show: UUID=8f4eeaae-a055-4262-bebb-cf99abe982a5 /var ext4 defaults 0 2 Yours have a block device name instead of mountpoint: UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /dev/sdb1 ext4 errors=remount-ro 0 1 UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdc1 ext4 errors=remount-ro 0 1 UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdc2 ext4 errors=remount-ro 0 1 So even a stock mount(1) should refuse to mount these. When I rebooted the computer the OS didn't like the new fstab and gave me a number of, at least to me, obscure messages. systemd-mount can be cryptic, I agree. Obviously, I missed something important. My question is what? It's a kind of dumb question, but where do you need your sdb1, sdc1 and sdc2 mounted? Your fstab(5) does not mention that. Reco Well, that's another red faced forehead slapper! It merely reinforces that I don't know what I'm doing as far as hardware is concerned. It's a good thing that I'm an Organic Chemist and not an IT person. Instead of trying your new changes in '/etc/fstab' by rebooting, you could also try 'mount -a'. https://linux.die.net/man/8/mount -- John Doe
Re: Problem Mounting New Drives
On 08/19/2018 02:28 PM, Reco wrote: Hi. On Sun, Aug 19, 2018 at 02:04:39PM -0400, Stephen P. Molnar wrote: Note that second field is a mountpoint in fstab(5), as one of the stock records show: UUID=8f4eeaae-a055-4262-bebb-cf99abe982a5 /varext4 defaults 0 2 Yours have a block device name instead of mountpoint: UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /dev/sdb1 ext4 errors=remount-ro 0 1 UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdc1 ext4 errors=remount-ro 0 1 UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdc2 ext4 errors=remount-ro 0 1 So even a stock mount(1) should refuse to mount these. When I rebooted the computer the OS didn't like the new fstab and gave me a number of, at least to me, obscure messages. systemd-mount can be cryptic, I agree. Obviously, I missed something important. My question is what? It's a kind of dumb question, but where do you need your sdb1, sdc1 and sdc2 mounted? Your fstab(5) does not mention that. Reco Well, that's another red faced forehead slapper! It merely reinforces that I don't know what I'm doing as far as hardware is concerned. It's a good thing that I'm an Organic Chemist and not an IT person. Many, many thanks. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
Re: Problem Mounting New Drives
Hi. On Sun, Aug 19, 2018 at 02:04:39PM -0400, Stephen P. Molnar wrote: Note that second field is a mountpoint in fstab(5), as one of the stock records show: > UUID=8f4eeaae-a055-4262-bebb-cf99abe982a5 /varext4 defaults > 0 2 Yours have a block device name instead of mountpoint: > UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /dev/sdb1 ext4 errors=remount-ro 0 > 1 > UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdc1 ext4 errors=remount-ro 0 > 1 > UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdc2 ext4 errors=remount-ro 0 > 1 So even a stock mount(1) should refuse to mount these. > When I rebooted the computer the OS didn't like the new fstab and gave me a > number of, at least to me, obscure messages. systemd-mount can be cryptic, I agree. > Obviously, I missed something important. My question is what? It's a kind of dumb question, but where do you need your sdb1, sdc1 and sdc2 mounted? Your fstab(5) does not mention that. Reco
Problem Mounting New Drives
Up to date Stretch. I have just reinstalled Stretch on a new SSD as sda. I have two additional HD's on the platform, sdb and sdc. Here is the blkid ouput: root@AbNormal:/home/comp# blkid /dev/sda1: UUID="07defe36-57e7-4218-82cb-35cc109b004e" TYPE="ext4" PARTUUID="2f9cc88d-01" /dev/sda5: UUID="8f4eeaae-a055-4262-bebb-cf99abe982a5" TYPE="ext4" PARTUUID="2f9cc88d-05" /dev/sda6: UUID="09461b2f-2b58-461a-869f-eef158a78127" TYPE="swap" PARTUUID="2f9cc88d-06" /dev/sda7: UUID="3508065e-0ab4-424f-9002-3b237e5d120e" TYPE="ext4" PARTUUID="2f9cc88d-07" /dev/sda8: UUID="af824450-3dd9-48b8-8ff3-c831365f31fa" TYPE="ext4" PARTUUID="2f9cc88d-08" /dev/sdb1: UUID="900b5f0b-4f3d-4a64-8c91-29aee4c6fd07" TYPE="ext4" PARTUUID="0bc7db76-01" /dev/sdb5: UUID="7c386aca-a547-475f-8616-f7664f93c595" TYPE="swap" PARTUUID="0bc7db76-05" /dev/sdc1: UUID="d65867da-c658-4e35-928c-9dd2d6dd5742" TYPE="ext4" PARTUUID="0003d403-01" /dev/sdc2: UUID="007c1f16-34a4-438c-9d15-e3df601649ba" TYPE="ext4" PARTUUID="0003d403-02" On the basis of blkid output I edited /etc/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). # # # / was on /dev/sda1 during installation UUID=07defe36-57e7-4218-82cb-35cc109b004e / ext4 errors=remount-ro 0 1 # /home was on /dev/sda8 during installation UUID=af824450-3dd9-48b8-8ff3-c831365f31fa /home ext4 defaults0 2 # /tmp was on /dev/sda7 during installation UUID=3508065e-0ab4-424f-9002-3b237e5d120e /tmpext4 defaults0 2 # /var was on /dev/sda5 during installation UUID=8f4eeaae-a055-4262-bebb-cf99abe982a5 /varext4 defaults0 2 # swap was on /dev/sda6 during installation UUID=09461b2f-2b58-461a-869f-eef158a78127 noneswap sw 0 0 /dev/sr0/media/cdrom0 udf,iso9660 user,noauto 0 0 UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /dev/sdb1 ext4 errors=remount-ro 0 1 UUID=d65867da-c658-4e35-928c-9dd2d6dd5742 /dev/sdc1 ext4 errors=remount-ro 0 1 UUID=007c1f16-34a4-438c-9d15-e3df601649ba /dev/sdc2 ext4 errors=remount-ro 0 1 /dev/sdb5 is the swap partition on the old sda, the new SSD was installed as sda, so I didn't include that swap in the edited fstab. I also added sdb1, sdc1 and sdc2 to /. /dev contains /sdb/sdb1/sdb2/sdb5/sdc,sdc1 and sdc2 as well as all of the entries for sda. Before saving the edited fstab I renamed the /etc/fsab /etc/fstab_old. When I rebooted the computer the OS didn't like the new fstab and gave me a number of, at least to me, obscure messages. However, I was allowed to log on as root and execute startx. This allowed me to reinstall the unedited fstab and the system booted properly. Obviously, I missed something important. My question is what? Thanks in advance. -- Stephen P. Molnar, Ph.D. Consultant www.molecular-modeling.net (614)312-7528 (c) Skype: smolnar1
