User Tools

Site Tools


identify_and_mount_a_drive

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
identify_and_mount_a_drive [2017/01/08 21:46] walkeradminidentify_and_mount_a_drive [2023/03/09 22:35] (current) – external edit 127.0.0.1
Line 83: Line 83:
     sudo nano /etc/fstab     sudo nano /etc/fstab
 \\  \\ 
-    Add the line in red to the bottom, replace XXXX-XXXX with your UUID and exfat with your type if it is different (e.g. ntfs, vfat, ext4). You may or may not need the quotation marks wrapped around the UID, you do not need quotation marks wrapped around the file system type (ext4, vfat, NTFS etc).+    Add the line in red to the bottom, replace XXXX-XXXX with your UUID and exfat with your type if it is  
 +    different (e.g. ntfs, vfat, ext4). You may or may not need the quotation marks wrapped around the UID, you do 
 +    not need quotation marks wrapped around the file system type (ext4, vfat, NTFS etc).
 \\  \\ 
-    The umask 0002 sets 775 permissions so the pi user and group can read, write and execute files on the external USB drive. To completely eliminate permission issues you can set the umask to 0000 which equals 777 permissions so anybody can read, write and execute. Note that 777 permissions are considered a security risk.+    The umask 0002 sets 775 permissions so the pi user and group can read, write and execute files  
 +    on the external USB drive. To completely eliminate permission issues you can set the umask to 0000  
 +    which equals 777 permissions so anybody can read, write and execute. Note that 777 permissions are  
 +    considered a security risk.
 \\  \\ 
 If you have issues here then try replacing uid=pi,gid=pi with just the word defaults (typical for ext4). You can also try replacing the UUID with the /dev/sda1 line. If you have issues here then try replacing uid=pi,gid=pi with just the word defaults (typical for ext4). You can also try replacing the UUID with the /dev/sda1 line.
Line 127: Line 132:
     sudo mount -a     sudo mount -a
 \\  \\ 
-<file> +    If you didn’t get errors reboot, otherwise try the suggestions above to get it working then 
-If you didn’t get errors reboot, otherwise try the suggestions above to get it working then mount -a again until it succeeds+    mount -a again until it succeeds
          
-sudo reboot +    sudo reboot
-</file>+
 \\  \\ 
 \\  \\ 
identify_and_mount_a_drive.1483911964.txt.gz · Last modified: 2023/03/09 22:35 (external edit)