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


Groups > comp.sys.mac.system > #134173 > unrolled thread

Rename Partition on USB Hard Drive

Started byWade Garrett <wade@cooler.net>
First post2020-08-26 15:38 -0400
Last post2020-09-01 01:20 -0400
Articles 8 — 6 participants

Back to article view | Back to comp.sys.mac.system


Contents

  Rename Partition on USB Hard Drive Wade Garrett <wade@cooler.net> - 2020-08-26 15:38 -0400
    Re: Rename Partition on USB Hard Drive Lewis <g.kreme@gmail.com.dontsendmecopies> - 2020-08-26 22:45 +0000
      Re: Rename Partition on USB Hard Drive MeV <michael.vilain@gmail.com> - 2020-08-29 07:51 -0700
        Re: Rename Partition on USB Hard Drive Wade Garrett <wade@cooler.net> - 2020-08-29 18:27 -0400
        Re: Rename Partition on USB Hard Drive Lewis <g.kreme@gmail.com.dontsendmecopies> - 2020-08-30 11:47 +0000
          Re: Rename Partition on USB Hard Drive Percival John Hackworth <pjh@nanoworks.com> - 2020-08-30 08:47 -0700
          Re: Rename Partition on USB Hard Drive Bernd Froehlich <befr@eaglesoft.de> - 2020-08-31 08:31 +0000
            Re: Rename Partition on USB Hard Drive JF Mezei <jfmezei.spamnot@vaxination.ca> - 2020-09-01 01:20 -0400

#134173 — Rename Partition on USB Hard Drive

FromWade Garrett <wade@cooler.net>
Date2020-08-26 15:38 -0400
SubjectRename Partition on USB Hard Drive
Message-ID<ri6doc$1vv$1@dont-email.me>
Will renaming an extended journaled partition on an external USB 
spinning hard drive with a GUID Partition Map under OS 10.15.6 put its 
data at risk or create other problems?

Not changing the drive name, just a partition on it.

-- 
Criminals love gun control; it makes their job much, much safer.

[toc] | [next] | [standalone]


#134174

FromLewis <g.kreme@gmail.com.dontsendmecopies>
Date2020-08-26 22:45 +0000
Message-ID<slrnrkdpg1.fie.g.kreme@ProMini.lan>
In reply to#134173
In message <ri6doc$1vv$1@dont-email.me> Wade Garrett <wade@cooler.net> wrote:
> Will renaming an extended journaled partition on an external USB 
> spinning hard drive with a GUID Partition Map under OS 10.15.6 put its 
> data at risk or create other problems?

No.

Well, if you have written code that accesses the volume by name,
obviously that will stop working.

-- 
Oh never resist an impulse, Sabrina. Especially if it's terrible.

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


#134175

FromMeV <michael.vilain@gmail.com>
Date2020-08-29 07:51 -0700
Message-ID<13bbb97d-8309-4a72-914e-e946fb3b8199o@googlegroups.com>
In reply to#134174
On Wednesday, August 26, 2020 at 3:45:25 PM UTC-7, Lewis wrote:
> In message <ri6doc$1vv$1@dont-email.me> Wade Garrett <wade@cooler.net> wrote:
> > Will renaming an extended journaled partition on an external USB 
> > spinning hard drive with a GUID Partition Map under OS 10.15.6 put its 
> > data at risk or create other problems?
> 
> No.
> 
> Well, if you have written code that accesses the volume by name,
> obviously that will stop working.
> 
> -- 
> Oh never resist an impulse, Sabrina. Especially if it's terrible.

Like SuperDuper! backups will fail

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


#134176

FromWade Garrett <wade@cooler.net>
Date2020-08-29 18:27 -0400
Message-ID<riekop$85i$1@dont-email.me>
In reply to#134175
On 8/29/20 10:51 AM, MeV wrote:
> On Wednesday, August 26, 2020 at 3:45:25 PM UTC-7, Lewis wrote:
>> In message <ri6doc$1vv$1@dont-email.me> Wade Garrett <wade@cooler.net> wrote:
>>> Will renaming an extended journaled partition on an external USB
>>> spinning hard drive with a GUID Partition Map under OS 10.15.6 put its
>>> data at risk or create other problems?
>>
>> No.
>>
>> Well, if you have written code that accesses the volume by name,
>> obviously that will stop working.
>>
>> -- 
>> Oh never resist an impulse, Sabrina. Especially if it's terrible.
> 
> Like SuperDuper! backups will fail
> 
Yup, Time Machine too- even when I changed the volume name back to what 
it was. Had to pull files and folders I wanted to keep off there manually.

-- 
When did Western society decide that instead of helping mentally ill 
people, we should indulge their delusions 100% and allow them to set 
policy for the rest of us?

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


#134177

FromLewis <g.kreme@gmail.com.dontsendmecopies>
Date2020-08-30 11:47 +0000
Message-ID<slrnrkn4e0.dvr.g.kreme@ProMini.lan>
In reply to#134175
In message <13bbb97d-8309-4a72-914e-e946fb3b8199o@googlegroups.com> MeV <michael.vilain@gmail.com> wrote:
> On Wednesday, August 26, 2020 at 3:45:25 PM UTC-7, Lewis wrote:
>> In message <ri6doc$1vv$1@dont-email.me> Wade Garrett <wade@cooler.net> wrote:
>> > Will renaming an extended journaled partition on an external USB 
>> > spinning hard drive with a GUID Partition Map under OS 10.15.6 put its 
>> > data at risk or create other problems?
>> 
>> No.
>> 
>> Well, if you have written code that accesses the volume by name,
>> obviously that will stop working.
>> 
>> -- 
>> Oh never resist an impulse, Sabrina. Especially if it's terrible.

> Like SuperDuper! backups will fail

Really? That seems odd, why would it not use the disk ID? That seems
very broken to me if renaming a disk causes your backup strategy to
fail.

-- 
We’re despairing in style, as befits two former High Kings of Fillory.

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


#134178

FromPercival John Hackworth <pjh@nanoworks.com>
Date2020-08-30 08:47 -0700
Message-ID<0001HW.24FC01AA0200817D70000959C2CF@news.individual.net>
In reply to#134177
On 30-Aug-2020, Lewis wrote
(in article <slrnrkn4e0.dvr.g.kreme@ProMini.lan>):

> In message<13bbb97d-8309-4a72-914e-e946fb3b8199o@googlegroups.com>
> MeV<michael.vilain@gmail.com>  wrote:
> > On Wednesday, August 26, 2020 at 3:45:25 PM UTC-7, Lewis wrote:
> > > In message<ri6doc$1vv$1@dont-email.me>  Wade Garrett<wade@cooler.net>
> > > wrote:
> > > > Will renaming an extended journaled partition on an external USB
> > > > spinning hard drive with a GUID Partition Map under OS 10.15.6 put its
> > > > data at risk or create other problems?
> > >
> > > No.
> > >
> > > Well, if you have written code that accesses the volume by name,
> > > obviously that will stop working.
> > >
> > > --
> > > Oh never resist an impulse, Sabrina. Especially if it's terrible.
>
> > Like SuperDuper! backups will fail
>
> Really? That seems odd, why would it not use the disk ID? That seems
> very broken to me if renaming a disk causes your backup strategy to
> fail.

It's a crontab and won't recognize the drive any more. It can be fixed by 
removing the backup source and re-adding it. The backup destination, however, 
is another matter. You have to wipe the partition and back it up all over 
again. I haven't tried restoring from the backup of the renamed partition.

If you have File Vault enabled, I don't know what will happen when you try to 
boot from the renamed partition.

These are all warnings. You'll have to do the work yourself and find out what 
breaks and report it here. I prefer to leave what works alone rather than 
spend time futzing with stuff I don't have to.

-- 
DeeDee, don't press that button! DeeDee! NO! Dee...

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


#134179

FromBernd Froehlich <befr@eaglesoft.de>
Date2020-08-31 08:31 +0000
Message-ID<hr3qqbF6phfU1@mid.individual.net>
In reply to#134177
On 30. Aug 2020 at 13:47:13 CEST, "Lewis"
<g.kreme@gmail.com.dontsendmecopies> wrote:

> Really? That seems odd, why would it not use the disk ID? That seems
> very broken to me if renaming a disk causes your backup strategy to
> fail.

Hmm, you would prefer that if a user renames Volume "A" to "B" and connects
a new volume "A" that the backup then should go to volume "B"?
Sounds dangerous to me.

An alternative would be not to display the volumename but the disc ID
instead. But I guess that would be a bit confusing too.

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


#134180

FromJF Mezei <jfmezei.spamnot@vaxination.ca>
Date2020-09-01 01:20 -0400
Message-ID<xSk3H.197263$5_4.141471@fx40.iad>
In reply to#134179
On 2020-08-31 04:31, Bernd Froehlich wrote:

> Hmm, you would prefer that if a user renames Volume "A" to "B" and connects
> a new volume "A" that the backup then should go to volume "B"?
> Sounds dangerous to me.



From man tmutil

 In Mac OS X, HFS+ volumes have a persistent UUID that is assigned when
the file system is created. Time Machine uses this identifier to make an
association between a source volume and a snapshot volume. Erasing the
source  volume creates a new file system on the disk, and the previous
UUID is not retained. The new UUID causes the source volume -> snapshot
volume association to be broken. If one were just erasing the volume and
starting over, it would likely be of no real consequence, and the new
UUID would not be a concern; when erasing a volume in order to clone
another volume to it, recreating the association may be desired.

This is from the "assoiciatedisk" subcommand of tmutil. After
reformatting a ddrive, you can recreate the association with the backup
destination directory (akaL same volume name but differenr UUID in the
source)

[toc] | [prev] | [standalone]


Back to top | Article view | comp.sys.mac.system


csiph-web