I have an external drive I set up yesterday that has the name "a3cd7e7f-254d-410a-b120-e02524f75a29." How can I change that to something like "/run/media/bobg/externaldrive?"
Bob
On 07/24/16 16:28, Bob Goodwin wrote:
I have an external drive I set up yesterday that has the name "a3cd7e7f-254d-410a-b120-e02524f75a29." How can I change that to something like "/run/media/bobg/externaldrive?"
What type of file system? If you're using ext you can label the file system with e2label and it should come up mounted with the label name. If I'm not mistaken.
On 07/24/16 05:59, Ed Greshko wrote:
On 07/24/16 16:28, Bob Goodwin wrote:
I have an external drive I set up yesterday that has the name "a3cd7e7f-254d-410a-b120-e02524f75a29." How can I change that to something like "/run/media/bobg/externaldrive?"
What type of file system? If you're using ext you can label the file system with e2label and it should come up mounted with the label name. If I'm not mistaken.
+
Thanks Ed, that seems to have worked although I'm don't understand how ...
[root@Box10 ~]# mount /dev/sde1 /mnt/temp/
Mounts the drive to /mnt/temp/ and "mount" shows the following:
[root@Box10 ~]# mount
............ snip ............
/dev/sdd1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered) /dev/sde1 on /run/media/bobg/st1000 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2) /dev/sde1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered)
It does what I asked!
Bob
On 07/24/2016 01:16 PM, Bob Goodwin wrote:
Thanks Ed, that seems to have worked although I'm don't understand how ...
If a removable device has a label, the system will create a mountpoint for it using that label; it was using the UUID simply because that was the only unique identifier it had.
On 07/24/16 16:27, Joe Zeff wrote:
On 07/24/2016 01:16 PM, Bob Goodwin wrote:
Thanks Ed, that seems to have worked although I'm don't understand how ...
If a removable device has a label, the system will create a mountpoint for it using that label; it was using the UUID simply because that was the only unique identifier it had.
+
The curious thing is I did: # e2label /dev/sdd1 st1000
and now, from mount, I see three devices:
/dev/sdd1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered) /dev/sde1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered) /dev/sdf1 on /run/media/bobg/a3cd7e7f-254d-410a-b120-e02524f75a29 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
It works just fine, puts an icon on the desktop and I can mount it from that.
Bob
On 07/25/16 04:16, Bob Goodwin wrote:
On 07/24/16 05:59, Ed Greshko wrote:
On 07/24/16 16:28, Bob Goodwin wrote:
I have an external drive I set up yesterday that has the name "a3cd7e7f-254d-410a-b120-e02524f75a29." How can I change that to something like "/run/media/bobg/externaldrive?"
What type of file system? If you're using ext you can label the file system with e2label and it should come up mounted with the label name. If I'm not mistaken.
Thanks Ed, that seems to have worked although I'm don't understand how ...
[root@Box10 ~]# mount /dev/sde1 /mnt/temp/
Mounts the drive to /mnt/temp/ and "mount" shows the following:
[root@Box10 ~]# mount
............ snip ............
OK.... But please note.
/dev/sdd1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered) /dev/sde1 on /run/media/bobg/st1000 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2) /dev/sde1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered)
It does what I asked!
You seem to have /dev/sdd1 already mounted on /mnt/temp.
And you've manually mounted /dev/sde1 on /mnt/temp as well as it being automounted on /run/media/bobg.
Not sure that is what you wanted to accomplish.
Allegedly, on or about 24 July 2016, Bob Goodwin sent:
/dev/sdd1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered) /dev/sde1 on /mnt/temp type ext4 (rw,relatime,seclabel,data=ordered)
You've mounted two things onto the same mount point. Do-able, but the second thing takes over, and the first one becomes hidden. You should really unmount something before mounting something else over the top of it.
If you've been unplugging and replugging USB drives rather quickly, even if it was unmounted, the system doesn't let go of the previous device name (e.g. /dev/sdd1) immediately, and when replugged it may be given the next available device name (e.g. /dev/sde1).
If you unplug, wait some time, then replug, chances are that the previous device will be noticed as free, and the second time its loaded up, will be given the same device name as before.
Ordinarily, it probably doesn't matter that something has changed device names, as we're supposed to be using labels and unique IDs to refer to drives. But it can be confusing when trying to sort out hardware, and a potential risk if your next task was to do something with a device based on the device name. You end up operating on the wrong thing.
On 07/24/16 18:42, Ed Greshko wrote:
It does what I asked!
You seem to have /dev/sdd1 already mounted on /mnt/temp.
And you've manually mounted /dev/sde1 on /mnt/temp as well as it being automounted on /run/media/bobg.
Not sure that is what you wanted to accomplish.
+
After boot this morning I switched on the power on the external, usb drive adapter and an icon appeared on the desktop screen. I clicked on "Mount" and got:
/dev/sdd1 on /run/media/bobg/a3cd7e7f-254d-410a-b120-e02524f75a29 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
So the command 'e2label /dev/sdd1 st1000' makes it possible to add another device, it doesn't change the name. What did I miss in setting up the external drive initially?
None of this really matters since all I need is to have the data saved and to be able to use it to recover if needed. But I would like things to work predictably whan I configure something.
Bob
On 07/25/2016 04:46 AM, Bob Goodwin wrote:
So the command 'e2label /dev/sdd1 st1000' makes it possible to add another device, it doesn't change the name. What did I miss in setting up the external drive initially?
Two questions: first, have you rebooted, or otherwise unmounted/remounted that drive since giving it a label and second, what does 'e2label /dev/sdd1' return?
On 07/25/16 08:01, Joe Zeff wrote:
On 07/25/2016 04:46 AM, Bob Goodwin wrote:
So the command 'e2label /dev/sdd1 st1000' makes it possible to add another device, it doesn't change the name. What did I miss in setting up the external drive initially?
Two questions: first, have you rebooted, or otherwise unmounted/remounted that drive since giving it a label and second, what does 'e2label /dev/sdd1' return?
+
Yes I ran the command yesterday and have re-booted several times since, usually shut this computer down at night.
[bobg@Box10 ~]$ e2label /dev/sdd1 e2label: Permission denied while trying to open /dev/sdd1 Couldn't find valid filesystem superblock.
[bobg@Box10 ~]$ su Password:
[root@Box10 bobg]# e2label /dev/sdd1
[root@Box10
Nothing, perhaps it does not survive a re-boot?
On 07/25/16 19:46, Bob Goodwin wrote:
On 07/24/16 18:42, Ed Greshko wrote:
It does what I asked!
You seem to have /dev/sdd1 already mounted on /mnt/temp.
And you've manually mounted /dev/sde1 on /mnt/temp as well as it being automounted on /run/media/bobg.
Not sure that is what you wanted to accomplish.
After boot this morning I switched on the power on the external, usb drive adapter and an icon appeared on the desktop screen. I clicked on "Mount" and got:
/dev/sdd1 on /run/media/bobg/a3cd7e7f-254d-410a-b120-e02524f75a29 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
So the command 'e2label /dev/sdd1 st1000' makes it possible to add another device, it doesn't change the name. What did I miss in setting up the external drive initially?
None of this really matters since all I need is to have the data saved and to be able to use it to recover if needed. But I would like things to work predictably whan I configure something.
It shouldn't make any difference but I just realized that when I label my file systems I didn't use e2label but I used tune2fs.
What is the output of "tune2fs -l /dev/sdd1"
On 07/25/16 09:35, Ed Greshko wrote:
What is the output of "tune2fs -l /dev/sdd1"
# tune2fs -l /dev/sdd1 tune2fs 1.42.13 (17-May-2015) Filesystem volume name: <none> Last mounted on: /mnt/temp Filesystem UUID: a3cd7e7f-254d-410a-b120-e02524f75a29 Filesystem magic number: 0xEF53 Filesystem revision #: 1 (dynamic) Filesystem features: has_journal ext_attr resize_inode dir_index filetype needs_recovery extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize Filesystem flags: signed_directory_hash Default mount options: user_xattr acl Filesystem state: clean Errors behavior: Continue Filesystem OS type: Linux Inode count: 61054976 Block count: 244190208 Reserved block count: 12209510 Free blocks: 177680200 Free inodes: 61008619 First block: 0 Block size: 4096 Fragment size: 4096 Reserved GDT blocks: 965 Blocks per group: 32768 Fragments per group: 32768 Inodes per group: 8192 Inode blocks per group: 512 Flex block group size: 16 Filesystem created: Sat Jul 23 16:11:22 2016 Last mount time: Mon Jul 25 07:30:23 2016 Last write time: Mon Jul 25 07:30:23 2016 Mount count: 11 Maximum mount count: -1 Last checked: Sat Jul 23 16:11:22 2016 Check interval: 0 (<none>) Lifetime writes: 251 GB Reserved blocks uid: 0 (user root) Reserved blocks gid: 0 (group root) First inode: 11 Inode size: 256 Required extra isize: 28 Desired extra isize: 28 Journal inode: 8 Default directory hash: half_md4 Directory Hash Seed: b7537a31-5c4b-4013-a2f0-191b7ebf959d Journal backup: inode blocks
On 07/25/16 09:43, Ed Greshko wrote:
On 07/25/16 21:40, Bob Goodwin wrote:
# tune2fs -l /dev/sdd1 tune2fs 1.42.13 (17-May-2015) Filesystem volume name: <none>
OK....
Do
tune2fs -L st1000
and then
tune2fs -l
to see if <none> changes....
--
+
That's what I thought after reading through the man page, but thought I would wait for your response and try to get it right rather than trial and error, my usual way.
No that [# tune2fs -L st1000] does not work, I tried unmounting and remounting, still no volume name
# tune2fs -l /dev/sdd1 tune2fs 1.42.13 (17-May-2015) Filesystem volume name: <none> Last mounted on: /mnt/temp Filesystem UUID: a3cd7e7f-254d-410a-b120-e02524f75a29 Filesystem magic number: 0xEF53 ...... snip .....
This is what I see:
]# tune2fs -L st1000 tune2fs 1.42.13 (17-May-2015) Usage: tune2fs [-c max_mounts_count] [-e errors_behavior] [-g group] [-i interval[d|m|w]] [-j] [-J journal_options] [-l] [-m reserved_blocks_percent] [-o [^]mount_options[,...]] [-p mmp_update_interval] [-r reserved_blocks_count] [-u user] [-C mount_count] [-L volume_label] [-M last_mounted_dir] [-O [^]feature[,...]] [-Q quota_options] [-E extended-option[,...]] [-T last_check_time] [-U UUID] [ -I new_inode_size ] device
On 07/25/16 10:12, Ed Greshko wrote:
On 07/25/16 22:07, Bob Goodwin wrote:
# tune2fs -L st1000
Ooopppsss My bad.... Having a night cap and forgot the most important part...
tune2fs -L st1000 /dev/sdd1
How else will it know what filesystem we're talking about? :-) :-)
--
+
And that should have been obvious to me too. Problem is I just followed your command without thinking obviously. It now shows:
/dev/sdd1 on /run/media/bobg/st1000 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
Thank you for your patience,
Bob
On 07/25/16 22:41, Bob Goodwin wrote:
On 07/25/16 10:12, Ed Greshko wrote:
On 07/25/16 22:07, Bob Goodwin wrote:
# tune2fs -L st1000
Ooopppsss My bad.... Having a night cap and forgot the most important part...
tune2fs -L st1000 /dev/sdd1
How else will it know what filesystem we're talking about? :-) :-)
--
And that should have been obvious to me too. Problem is I just followed your command without thinking obviously. It now shows:
/dev/sdd1 on /run/media/bobg/st1000 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
Thank you for your patience,
And Thank You for your understanding that Jack Daniels isn't always compatible with sound advice.
On 07/25/16 10:52, Ed Greshko wrote:
And Thank You for your understanding that Jack Daniels isn't always compatible with sound advice.
+
Hick,
On Mon, Jul 25, 2016 at 07:46:04AM -0400, Bob Goodwin wrote:
On 07/24/16 18:42, Ed Greshko wrote:
It does what I asked!
You seem to have /dev/sdd1 already mounted on /mnt/temp.
And you've manually mounted /dev/sde1 on /mnt/temp as well as it being automounted on /run/media/bobg.
Not sure that is what you wanted to accomplish.
After boot this morning I switched on the power on the external, usb drive adapter and an icon appeared on the desktop screen. I clicked on "Mount" and got:
/dev/sdd1 on /run/media/bobg/a3cd7e7f-254d-410a-b120-e02524f75a29 type ext4 (rw,nosuid,nodev,relatime,seclabel,data=ordered,uhelper=udisks2)
So the command 'e2label /dev/sdd1 st1000' makes it possible to add another device, it doesn't change the name. What did I miss in setting up the external drive initially?
IIRC, yesterday you were labelling /dev/sde1, not sdd1. Did it get enumerated differently today?
If the system consistently mounts the drive to a specific location (ex /run/media/bobg/<UUID> you could make a symbolic link to the mount point in your homedir, say /home/bobg/extdisc. If the drive is mounted you have an easy to use path to it. Otherwise it will just be a broken link, no problem.
jon
On 07/26/16 01:15, Jon LaBadie wrote:
IIRC, yesterday you were labelling /dev/sde1, not sdd1. Did it get enumerated differently today?
If the system consistently mounts the drive to a specific location (ex/run/media/bobg/<UUID> you could make a symbolic link to the mount point in your homedir, say /home/bobg/extdisc. If the drive is mounted you have an easy to use path to it. Otherwise it will just be a broken link, no problem.
jon
+
Yes, I apparently had it mounted as several devices but normally it is /dev/sdd1.
Your suggestion is interesting but I don't think I need that. I have a Samba server set up as raid0 that I want to make changes to [eliminate the raid] and just needed a place to back up ~ 239GB of data, mostly image files. Once that is done my need for an external drive drops to virtually nothing. It's not to be accessed often, hopefully just once.
Bob
tisdag 26 juli 2016 skrev Bob Goodwin bobgoodwin@fastmail.us:
On 07/26/16 01:15, Jon LaBadie wrote:
IIRC, yesterday you were labelling /dev/sde1, not sdd1. Did it get enumerated differently today?
If the system consistently mounts the drive to a specific location (ex/run/media/bobg/<UUID> you could make a symbolic link to the mount point in your homedir, say /home/bobg/extdisc. If the drive is mounted you have an easy to use path to it. Otherwise it will just be a broken link, no problem.
jon
Yes, I apparently had it mounted as several devices but normally it is /dev/sdd1.
Arne you aware that you can use /dev/disk/by-label/ now when you have a label set?
-- john
On 07/26/16 07:31, John Obaterspok wrote:
Yes, I apparently had it mounted as several devices but normally it is /dev/sdd1.Arne you aware that you can use /dev/disk/by-label/ now when you have a label set?
-- john
That was one of many things I was not aware of.
[bobg@Box10 ~]$ ls -al /dev/disk/by-label/ total 0 drwxr-xr-x. 2 root root 80 Jul 26 12:49 . drwxr-xr-x. 6 root root 120 Jul 26 02:11 .. lrwxrwxrwx. 1 root root 10 Jul 26 02:11 F23b -> ../../sda2 lrwxrwxrwx. 1 root root 10 Jul 26 12:49 st1000 -> ../../sdd1
Thanks,
Bob
2016-07-26 19:59 GMT+02:00 Bob Goodwin bobgoodwin@fastmail.us:
On 07/26/16 07:31, John Obaterspok wrote:
Yes, I apparently had it mounted as several devices but normally it is /dev/sdd1.Arne you aware that you can use /dev/disk/by-label/ now when you have a label set?
-- john
That was one of many things I was not aware of.
[bobg@Box10 ~]$ ls -al /dev/disk/by-label/ total 0 drwxr-xr-x. 2 root root 80 Jul 26 12:49 . drwxr-xr-x. 6 root root 120 Jul 26 02:11 .. lrwxrwxrwx. 1 root root 10 Jul 26 02:11 F23b -> ../../sda2 lrwxrwxrwx. 1 root root 10 Jul 26 12:49 st1000 -> ../../sdd1
There are other /dev/disk/by-xxx links there as well. Depends on use-case, but by-label is the one I use most.
-- john
-
Bob Goodwin -
Ed Greshko -
Joe Zeff -
John Obaterspok -
Jon LaBadie -
Tim