David Wright <deb...@lionunicorn.co.uk> writes: > On Thu 28 Feb 2019 at 15:45:47 (-0500), Stephen P. Molnar wrote: >> I am running Stretch and after much trial and tribulation, and at >> times abject horror, I have succeeded in installing a new SSD. >> >> My drive structure is: >> >> comp@AbNormal:~$ lsblk >> NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT >> sda 8:0 0 465.8G 0 disk >> ├─sda1 8:1 0 457.9G 0 part / >> ├─sda2 8:2 0 1K 0 part >> └─sda5 8:5 0 7.9G 0 part [SWAP] >> sdb 8:16 0 1.8T 0 disk >> ├─sdb1 8:17 0 1.8T 0 part /sdb1 >> ├─sdb2 8:18 0 1K 0 part >> └─sdb5 8:21 0 7.9G 0 part >> sdc 8:32 0 465.8G 0 disk >> └─sdc1 8:33 0 465.8G 0 part /sdc1 >> sr0 11:0 1 1024M 0 rom >> >> and my fstab is: >> >> # /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=ce25f0e1-610d-4030-ab47-129cd47d974e / ext4 >> errors=remount-ro 0 1 >> # swap was on /dev/sda5 during installation >> UUID=a8f6dc7e-13f1-4495-b68a-27886d386db0 none swap sw >> 0 0 >> /dev/sr0 /media/cdrom0 udf,iso9660 user,noauto 0 0 >> >> UUID=900b5f0b-4f3d-4a64-8c91-29aee4c6fd07 /sdb1 ext4 errors=remount-ro >> 0 1 >> >> UUID=1f363165-2c59-4236-850d-36d1e807099e /sdc1 ext4 errors=remount-ro >> 0 1 > > Well, you did ask for a sanity check, but those mount points are still > completely insane. And you still have 1 for the last field of your > non-root filesystems when it should be 2.
Agree with non-root being 2 but that fstab looks like how debian does defaults, it likes errrors=remount-ro. > I always add an explicit rw or ro under options, along with defaults. > With systemd, I add nofail to any filesystems that aren't vital for > the system to run, which means the system will still boot fully > without them. nofail is intended for removable drives that could be missing on boot, such as Thinkpad ultrabay drives/CF or SD cards. >> Finally, my user group structure is (comp is the user): >> >> comp cdrom floppy sudo audio dip video plugdev users netdev lpadmin scanner >> >> The problem is how do I set rw permissions on the new SSD? > > As posted by Dekks, but make sure the filesystem is already mounted: > it's the filesystem that needs changing, not the underlying mount > point. > > I think your 2TB disk hasn't been altered. You could just use its > ownership/permissions as a model if you were happy with them. > > Cheers, > David. > -- Regards......... PGP Fingerprint: 3DF8 311C 4740 B5BC 3867 72DF 1050 452F 9BCE BA00
signature.asc
Description: PGP signature