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

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

Sierra install accessed an external drive during install

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

Contents

  Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-24 12:30 -0400
    Re: Sierra install accessed an external drive during install Jolly Roger <jollyroger@pobox.com> - 2016-09-24 16:55 +0000
      Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-24 13:09 -0400
        Re: Sierra install accessed an external drive during install Jolly Roger <jollyroger@pobox.com> - 2016-09-24 17:41 +0000
          Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-24 13:49 -0400
            Re: Sierra install accessed an external drive during install Jolly Roger <jollyroger@pobox.com> - 2016-09-24 18:11 +0000
              Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-24 15:07 -0400
                Re: Sierra install accessed an external drive during install JF Mezei <jfmezei.spamnot@vaxination.ca> - 2016-09-24 15:35 -0400
                  Re: Sierra install accessed an external drive during install "Happy.Hobo" <Happy.Hobo@Spam.Invalid> - 2016-09-24 20:46 -0500
                    Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-25 09:22 -0400
                    Re: Sierra install accessed an external drive during install JF Mezei <jfmezei.spamnot@vaxination.ca> - 2016-09-25 14:22 -0400
            Re: Sierra install accessed an external drive during install JF Mezei <jfmezei.spamnot@vaxination.ca> - 2016-09-24 15:30 -0400
              Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-24 15:44 -0400
    Re: Sierra install accessed an external drive during install Bruce Esquibel <bje@ripco.com> - 2016-09-25 11:37 +0000
      Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-25 09:17 -0400
        Re: Sierra install accessed an external drive during install Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-09-26 05:03 +0000
          Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-26 17:56 -0400
            Re: Sierra install accessed an external drive during install Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-09-27 01:16 +0000
              Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-28 19:20 -0400
                Re: Sierra install accessed an external drive during install Lewis <g.kreme@gmail.com.dontsendmecopies> - 2016-09-29 04:26 +0000
                  Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-29 13:13 -0400
                    Re: Sierra install accessed an external drive during install Jolly Roger <jollyroger@pobox.com> - 2016-09-29 17:50 +0000
      Re: Sierra install accessed an external drive during install Alan Browne <alan.browne@freelunchvideotron.ca> - 2016-09-25 09:24 -0400
      Re: Sierra install accessed an external drive during install "Happy.Hobo" <Happy.Hobo@Spam.Invalid> - 2016-09-25 17:23 -0500

Page 1 of 2  [1] 2  Next page →

#94732 — Sierra install accessed an external drive during install

In the last 10 minutes or so of the install, the lights on one of my 
external drive was blinking mightily.

I checked the Time Machine backup time stamps and it wasn't that ...

Just poured thru /var/log and can't spot anything...

System Log:    "unable to read the file"   ??? WTF?  Deleted?

Any ideas?


-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

[toc] | [next] | [standalone]

#94735

On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>
> In the last 10 minutes or so of the install, the lights on one of my 
> external drive was blinking mightily.
>
> I checked the Time Machine backup time stamps and it wasn't that ...
>
> Just poured thru /var/log and can't spot anything...
>
> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>
> Any ideas?

Try lsof.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

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

#94738

On 2016-09-24 12:55, Jolly Roger wrote:
> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>
>> In the last 10 minutes or so of the install, the lights on one of my
>> external drive was blinking mightily.
>>
>> I checked the Time Machine backup time stamps and it wasn't that ...
>>
>> Just poured thru /var/log and can't spot anything...
>>
>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>
>> Any ideas?
>
> Try lsof.

	lsof | grep .log
	
  	located 4 files.  All having to do with various apps and services - 
none install;

I guess I don't get what you want me to try.




-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94740

On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> On 2016-09-24 12:55, Jolly Roger wrote:
>> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>>
>>> In the last 10 minutes or so of the install, the lights on one of my
>>> external drive was blinking mightily.
>>>
>>> I checked the Time Machine backup time stamps and it wasn't that ...
>>>
>>> Just poured thru /var/log and can't spot anything...
>>>
>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>>
>>> Any ideas?
>>
>> Try lsof.
>
> 	lsof | grep .log
> 	
>   	located 4 files.  All having to do with various apps and services - 
> none install;
>
> I guess I don't get what you want me to try.

No, I would filter the list by the volume in question to see what files
are being accessed on the volume.

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

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

#94742

On 2016-09-24 13:41, Jolly Roger wrote:
> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>> On 2016-09-24 12:55, Jolly Roger wrote:
>>> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>>>
>>>> In the last 10 minutes or so of the install, the lights on one of my
>>>> external drive was blinking mightily.
>>>>
>>>> I checked the Time Machine backup time stamps and it wasn't that ...
>>>>
>>>> Just poured thru /var/log and can't spot anything...
>>>>
>>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>>>
>>>> Any ideas?
>>>
>>> Try lsof.
>>
>> 	lsof | grep .log
>> 	
>>   	located 4 files.  All having to do with various apps and services -
>> none install;
>>
>> I guess I don't get what you want me to try.
>
> No, I would filter the list by the volume in question to see what files
> are being accessed on the volume.

Accessed during install wouldn't show in an lsof list ... (?)

-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94743

Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> On 2016-09-24 13:41, Jolly Roger wrote:
>> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>> On 2016-09-24 12:55, Jolly Roger wrote:
>>>> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>>>> 
>>>>> In the last 10 minutes or so of the install, the lights on one of my
>>>>> external drive was blinking mightily.
>>>>> 
>>>>> I checked the Time Machine backup time stamps and it wasn't that ...
>>>>> 
>>>>> Just poured thru /var/log and can't spot anything...
>>>>> 
>>>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>>>> 
>>>>> Any ideas?
>>>> 
>>>> Try lsof.
>>> 
>>> lsof | grep .log
>>> 
>>> located 4 files.  All having to do with various apps and services -
>>> none install;
>>> 
>>> I guess I don't get what you want me to try.
>> 
>> No, I would filter the list by the volume in question to see what files
>> are being accessed on the volume.
> 
> Accessed during install wouldn't show in an lsof list ... (?)

Oops I missed that it was happening during installation. Probably just
indexing happening or something. Were any files actually modified in the
volume?

-- 
E-mail sent to this address may be devoured by my ravenous SPAM filter.
I often ignore posts from Google. Use a real news client instead.

JR

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

#94745

On 2016-09-24 14:11, Jolly Roger wrote:
> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>> On 2016-09-24 13:41, Jolly Roger wrote:
>>> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>>> On 2016-09-24 12:55, Jolly Roger wrote:
>>>>> On 2016-09-24, Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>>>>>
>>>>>> In the last 10 minutes or so of the install, the lights on one of my
>>>>>> external drive was blinking mightily.
>>>>>>
>>>>>> I checked the Time Machine backup time stamps and it wasn't that ...
>>>>>>
>>>>>> Just poured thru /var/log and can't spot anything...
>>>>>>
>>>>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>>>>>
>>>>>> Any ideas?
>>>>>
>>>>> Try lsof.
>>>>
>>>> lsof | grep .log
>>>>
>>>> located 4 files.  All having to do with various apps and services -
>>>> none install;
>>>>
>>>> I guess I don't get what you want me to try.
>>>
>>> No, I would filter the list by the volume in question to see what files
>>> are being accessed on the volume.
>>
>> Accessed during install wouldn't show in an lsof list ... (?)
>
> Oops I missed that it was happening during installation. Probably just
> indexing happening or something. Were any files actually modified in the
> volume?

Dicked if I know.  W/o digging into the actual folders in there, the 
latest mod time at the top folder level was before I did the install.


-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94748

>>>>>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?

There are plenty of scenarios where this can happen.

Consider the backup scans a directory for list of files to backup. But
by the time it gets to the 4th file, that file was deleted or was
re-created with same name but different file ID/node number).

If the same file generates the same message over multiple backups, then
it is time to investigate as this would no longer be a "fluke".

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

#94754

On 09-24-2016 14:35, JF Mezei wrote:
>
>>>>>>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>
> There are plenty of scenarios where this can happen.
>
> Consider the backup scans a directory for list of files to backup. But
> by the time it gets to the 4th file, that file was deleted or was
> re-created with same name but different file ID/node number).
>
> If the same file generates the same message over multiple backups, then
> it is time to investigate as this would no longer be a "fluke".

Can a backup occur during an O.S. install?

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

#94765

On 2016-09-24 21:46, Happy.Hobo wrote:
> On 09-24-2016 14:35, JF Mezei wrote:
>>
>>>>>>>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>
>> There are plenty of scenarios where this can happen.
>>
>> Consider the backup scans a directory for list of files to backup. But
>> by the time it gets to the 4th file, that file was deleted or was
>> re-created with same name but different file ID/node number).
>>
>> If the same file generates the same message over multiple backups, then
>> it is time to investigate as this would no longer be a "fluke".
>
> Can a backup occur during an O.S. install?

No evidence of a TM backup at that time.


-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94772

On 2016-09-24 21:46, Happy.Hobo wrote:

> Can a backup occur during an O.S. install?

The first stage of an install is just staging of files in a new
directory and it doesn't affect the running system. For a while I
suspect launchd still works normally in background so if a backup is
scheduled, it could just proceed.

I am not sure at what point the installation blocks all other activity.
Obviously, when it reboots, it does so in a minimalist system that just
runs the subsequent phases of the installer so during this time, no
"normal" jobs would be runnning as I suspect that if launchd is running,
it is running from a minimalist database.


Remember that when you launch the installer app, it runs under your
account, and as a subprocess of your login. So it can't really kill you
or your parent processes because it would also be killing itself.

But it may be killing your other apps and taking over the screen, but
your login would have to remain and so would the parent processes.

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

#94747

On 2016-09-24 13:49, Alan Browne wrote:

> Accessed during install wouldn't show in an lsof list ... (?)


In the early stages of the installation, I think command line is sill
available. The installer is just another app in early stages.

And once it has taken control of the GUI, it wouldn't susprise me if
telnet/ssh might still be available.

And it isn't clear to me that prior to first boot, normal launchd
activity continues in background.

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

#94749

On 2016-09-24 15:30, JF Mezei wrote:
> And once it has taken control of the GUI, it wouldn't susprise me if
> telnet/ssh might still be available.

A little late for me to drop in, however.

>
> And it isn't clear to me that prior to first boot, normal launchd
> activity continues in background.

Perhaps.  But there is no evidence left of "what" was going on. 
Certainly not TM and no other time stamps that I can find.

Possibly indexing.


-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94761

Alan Browne <alan.browne@freelunchvideotron.ca> wrote:

> In the last 10 minutes or so of the install, the lights on one of my 
> external drive was blinking mightily.

> I checked the Time Machine backup time stamps and it wasn't that ...

> Just poured thru /var/log and can't spot anything...

> System Log:    "unable to read the file"   ??? WTF?  Deleted?

> Any ideas?


For what it's worth, if you are used to using Console and or grepping thru
files in /var/log, it seems apple depreciated the traditional syslog.

They added something in Sierra simply called "log" that is supposed to give
a much finer detail of events, if you can figure out how to use it.

If you have a few minutes to kill, open a terminal window and simply type:

log show

and sit back for a few minutes. I'm sure there is some way of narrowing down
the output but I didn't get any of the examples in the man page (man log) to
work, but only messed with it for a few minutes.

-bruce
bje@ripco.com

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

#94764

On 2016-09-25 07:37, Bruce Esquibel wrote:
> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>
>> In the last 10 minutes or so of the install, the lights on one of my
>> external drive was blinking mightily.
>
>> I checked the Time Machine backup time stamps and it wasn't that ...
>
>> Just poured thru /var/log and can't spot anything...
>
>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>
>> Any ideas?
>
>
> For what it's worth, if you are used to using Console and or grepping thru
> files in /var/log, it seems apple depreciated the traditional syslog.
>
> They added something in Sierra simply called "log" that is supposed to give
> a much finer detail of events, if you can figure out how to use it.
>
> If you have a few minutes to kill, open a terminal window and simply type:
>
> log show
>
> and sit back for a few minutes. I'm sure there is some way of narrowing down
> the output but I didn't get any of the examples in the man page (man log) to
> work, but only messed with it for a few minutes.

Thanks, you're right, that does spew a lot.  I'll try filtering that 
down with volume names and see what pops.

-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94800

In message <GvGdnanVLfDGU3rKnZ2dnUU7-XednZ2d@giganews.com> 
  Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> On 2016-09-25 07:37, Bruce Esquibel wrote:
>> Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>
>>> In the last 10 minutes or so of the install, the lights on one of my
>>> external drive was blinking mightily.
>>
>>> I checked the Time Machine backup time stamps and it wasn't that ...
>>
>>> Just poured thru /var/log and can't spot anything...
>>
>>> System Log:    "unable to read the file"   ??? WTF?  Deleted?
>>
>>> Any ideas?
>>
>>
>> For what it's worth, if you are used to using Console and or grepping thru
>> files in /var/log, it seems apple depreciated the traditional syslog.
>>
>> They added something in Sierra simply called "log" that is supposed to give
>> a much finer detail of events, if you can figure out how to use it.
>>
>> If you have a few minutes to kill, open a terminal window and simply type:
>>
>> log show
>>
>> and sit back for a few minutes. I'm sure there is some way of narrowing down
>> the output but I didn't get any of the examples in the man page (man log) to
>> work, but only messed with it for a few minutes.

> Thanks, you're right, that does spew a lot.  I'll try filtering that 
> down with volume names and see what pops.

log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info



-- 
Well boys, we got three engines out, we got more holes in us than a
horse trader's mule, the radio is gone and we're leaking fuel and if we
was flying any lower why we'd need sleigh bells on this thing... but we
got one little budge on those Roosskies. At this height why they might
harpoon us but they dang sure ain't gonna spot us on no radar screen!

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

#94818

On 2016-09-26 01:03, Lewis wrote:
> log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info

Even less so!  That would have to have been enabled before and started 
during the install re-boot process ...  and sending its o/p to a file. 
Since I had no idea such would happen; no idea what process (not 
necessarily TM) - I doubt that could be of much help.

No idea what it was doing, but the Time Machine updates (at the time, 2 
disks) were for before I launched the update to Sierra.

Nothing in the log showed access to any of the 4 external drives by 
their volume names.

-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94827

In message <A4udnXIBWODrBHTKnZ2dnUU7-XXNnZ2d@giganews.com> 
  Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> On 2016-09-26 01:03, Lewis wrote:
>> log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info

> Even less so!  That would have to have been enabled before and started 
> during the install re-boot process ...  and sending its o/p to a file. 

Yes. If you want to check previous events, you would not use stream,
obviously.

> Nothing in the log showed access to any of the 4 external drives by 
> their volume names.

I'm not sure why you think there would be?

-- 
Ahahahahaha! Ahahahaha! Aahahaha!  BEWARE!!!!!  Yrs sincerely  The Opera
Ghost

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

#94888

On 2016-09-26 21:16, Lewis wrote:
> In message <A4udnXIBWODrBHTKnZ2dnUU7-XXNnZ2d@giganews.com>
>   Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>> On 2016-09-26 01:03, Lewis wrote:
>>> log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
>
>> Even less so!  That would have to have been enabled before and started
>> during the install re-boot process ...  and sending its o/p to a file.
>
> Yes. If you want to check previous events, you would not use stream,
> obviously.
>
>> Nothing in the log showed access to any of the 4 external drives by
>> their volume names.
>
> I'm not sure why you think there would be?

Going back to the purpose of the post - trying to find what/why install 
time was accessing my external volumes.


-- 
She hummed to herself because she was an unrivaled botcher of lyrics.
   -Nick (Gone Girl), Gillian Flynn.

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

#94917

In message <4q2dncjjE-2qzXHKnZ2dnUU7-IGdnZ2d@giganews.com> 
  Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
> On 2016-09-26 21:16, Lewis wrote:
>> In message <A4udnXIBWODrBHTKnZ2dnUU7-XXNnZ2d@giganews.com>
>>   Alan Browne <alan.browne@freelunchvideotron.ca> wrote:
>>> On 2016-09-26 01:03, Lewis wrote:
>>>> log stream --style syslog  --predicate 'senderImagePath contains[cd] "TimeMachine"' --info
>>
>>> Even less so!  That would have to have been enabled before and started
>>> during the install re-boot process ...  and sending its o/p to a file.
>>
>> Yes. If you want to check previous events, you would not use stream,
>> obviously.
>>
>>> Nothing in the log showed access to any of the 4 external drives by
>>> their volume names.
>>
>> I'm not sure why you think there would be?

> Going back to the purpose of the post - trying to find what/why install 
> time was accessing my external volumes.

But you've produced no evidence the dive was accessed. And no, a light
on the drive doesn't mean it was accessed. It would have been spinning
down the drive, or clearing the buffers, or any number of things.

-- 
I intend to live forever -- so far, so good!

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

Page 1 of 2  [1] 2  Next page →

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

csiph-web