• Todas as comunidades
    • Todas as comunidades
    • Fóruns
    • Idéias
    • Blogs
Avançado

O que você está procurando? Pergunte a um especialista!

Kudos0

Scanning Stops

When every I try to scan my hard disk it simply stops part way through. Any suggestions?

Respostas

Kudos0

Re: Scanning Stops

I ran into the same problem. The process crashes after about 450K files.

Kudos0

Re: Scanning Stops

Can you please try the steps I gave in this thread here: HD Scan never completes

Thanks,

Ryan 

Ryan McGann Technical Director Norton Business Unit, Symantec
Kudos0

Re: Scanning Stops

Sorry, no SymAVScan or navx in Crash Report in Console.

I'm running Leopard 10.5.6 on a MacBook Pro with 2GB RAM with Norton 11.0, by the way.

It doesn't crash...it hangs up. It seems to hang up on PDF files. 

Kudos0

Re: Scanning Stops

Actually crashing is usually the most likely cause of this symptom. All scans are performed in a seperate process, and if that process exits, the process that shows the interface/scan progress will just sit there. We've had several reports of that, so I was assuming that it was a crash.

If it's not a crash, then can you please try and identify which file it is paused on? This should be the filename displayed in the UI. If you don't know where that file is at, you can use Spotlight to try and find it. If you are able to lcoate it, please try scanning that file only using the Norton AntiVirus application. If the file scans fine in the application, I'm not sure what else is going on--almost 100% of the time this issue is caused by a crash, or a corrupted compressed file.

Thanks,

Ryan

Ryan McGann Technical Director Norton Business Unit, Symantec
Kudos0

Re: Scanning Stops

Apparently, I had some bad clusters on the HD. I rebooted, held down the Command-S.  When the command line was displayed, I ran   

  

     /sbin/fsck -fy 

This corrected the HD issues.  After rebooting, I re-ran the scan and it worked fine. 

Kudos0

Re: Scanning Stops

That's interesting to know. Glad you figured it out.

Ryan

Ryan McGann Technical Director Norton Business Unit, Symantec
Kudos0

Re: Scanning Stops

If this post needs to go in a new thread let me know and I can repost, otherwise here I go... 

My mac is also having a "scanning stops" problem. I am running Mac NAV 11.0.2 (35) and it has been crashing on auto scans for some time and I can not seem to get it figured out.  The scanning notifier window prepares to scan then stalls and the notifier window will not close.  Strangely the NAV Recent Activities Log is indicating that these scans have had "No Problems."

I appreciate any help anyone might offer. 

Here is some truncated (due to character max) crash info from the console (there are 35 more crash logs if you need more info):

Process:         NortonAutoProtect [55]

Path:            /Library/Application Support/Symantec/AntiVirus/NortonAutoProtect.bundle/Contents/MacOS/NortonAutoProtect

Identifier:      NortonAutoProtect

Version:         ??? (???)

Code Type:       X86 (Native)

Parent Process:  launchd [1]

Date/Time:       2009-04-29 21:16:40.361 -0600

OS Version:      Mac OS X 10.5.6 (9G55)

Report Version:  6

Exception Type:  EXC_BAD_ACCESS (SIGBUS)

Exception Codes: 0x000000000000000a, 0x000000000615e000

Crashed Thread:  3

Thread 0:

0   libSystem.B.dylib             0x936981c6 mach_msg_trap + 10

1   libSystem.B.dylib             0x9369f9bc mach_msg + 72

2   com.apple.CoreFoundation       0x9035c0ae CFRunLoopRunSpecific + 1790

3   com.apple.CoreFoundation       0x9035cd34 CFRunLoopRun + 84

4   com.symantec.nortonautoprotect 0x00003cbb main + 1735

5   com.symantec.nortonautoprotect 0x00002832 0x1000 + 6194

6   com.symantec.nortonautoprotect 0x00002759 0x1000 + 5977

Thread 1:

0   libSystem.B.dylib             0x936981c6 mach_msg_trap + 10

1   libSystem.B.dylib             0x9369f9bc mach_msg + 72

2   libSystem.B.dylib             0x9370d1e7 mach_msg_server + 675

3   ...ec.sharedsettings.framework 0x0006e292 ZssStString::operator=(ZssSymbol*) + 1508

4   libSystem.B.dylib             0x936c9095 _pthread_start + 321

5   libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 2:

0   libSystem.B.dylib             0x936981c6 mach_msg_trap + 10

1   libSystem.B.dylib             0x9369f9bc mach_msg + 72

2   com.apple.CoreFoundation       0x9035c0ae CFRunLoopRunSpecific + 1790

3   com.apple.CoreFoundation       0x9035cd34 CFRunLoopRun + 84

4   com.symantec.uiagent.framework 0x000d48fa RunLoopMain(void*) + 222

5   libSystem.B.dylib             0x936c9095 _pthread_start + 321

6   libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 3 Crashed:

0   libSystem.B.dylib             0xffff06b0 __bzero + 176 (cpu_capabilities.h:244)

1   NAVLIBX                       0x00404fd8 0x400000 + 20440

2   NAVLIBX                       0x004051dc 0x400000 + 20956

3   NAVLIBX                       0x004055a3 0x400000 + 21923

4   NAVLIBX                       0x00411258 0x400000 + 70232

5   NAVLIBX                       0x004123be 0x400000 + 74686

6   NAVLIBX                       0x0041a6d2 NAVLibXQueryInterface + 5978

7   NAVLIBX                       0x0041aa1e NAVLibXQueryInterface + 6822

8   com.symantec.nortonautoprotect 0x00004a72 main + 5246

9   com.symantec.nortonautoprotect 0x0000620b main + 11287

10  com.symantec.nortonautoprotect 0x000065ac main + 12216

11  libSystem.B.dylib             0x936c9095 _pthread_start + 321

12  libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 4:

0   libSystem.B.dylib             0x93698226 semaphore_timedwait_signal_trap + 10

1   libSystem.B.dylib             0x936ca1ef _pthread_cond_wait + 1244

2   libSystem.B.dylib             0x936cba73 pthread_cond_timedwait_relative_np + 47

3   com.symantec.nortonautoprotect 0x00006e45 main + 14417

4   com.symantec.nortonautoprotect 0x000065ac main + 12216

5   libSystem.B.dylib             0x936c9095 _pthread_start + 321

6   libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 5:

0   libSystem.B.dylib             0x93698226 semaphore_timedwait_signal_trap + 10

1   libSystem.B.dylib             0x936ca1ef _pthread_cond_wait + 1244

2   libSystem.B.dylib             0x936cba73 pthread_cond_timedwait_relative_np + 47

3   com.symantec.nortonautoprotect 0x00006b34 main + 13632

4   com.symantec.nortonautoprotect 0x000065ac main + 12216

5   libSystem.B.dylib             0x936c9095 _pthread_start + 321

6   libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 6:

0   libSystem.B.dylib             0x93698bce read + 10

1   com.symantec.nortonautoprotect 0x000065ac main + 12216

2   libSystem.B.dylib             0x936c9095 _pthread_start + 321

3   libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 7:

0   libSystem.B.dylib             0x936c8906 kevent + 10

1   com.symantec.nortonautoprotect 0x000065ac main + 12216

2   libSystem.B.dylib             0x936c9095 _pthread_start + 321

3   libSystem.B.dylib             0x936c8f52 thread_start + 34

Thread 3 crashed with X86 Thread State (32-bit):

  eax: 0x00000000  ebx: 0x00404a2f  ecx: 0xffa521c0  edx: 0x0000002c

  edi: 0x0670be40  esi: 0x04aa1000  ebp: 0xb0183e88  esp: 0xb0183e84

   ss: 0x0000001f  efl: 0x00010286  eip: 0xffff06b0   cs: 0x00000017

   ds: 0x0000001f   es: 0x0000001f   fs: 0x0000001f   gs: 0x00000037

  cr2: 0x0615e000

Kudos0

Re: Scanning Stops

This scan log, while useful, is actually from our background scanning application, Norton AutoProtect. It is possible it is related to the problem you are seeing, but if you are seeing a scanning window, then AutoProtect is not performing the automatic scan you are referring to.

How are you initiating the scan? If you aren't sure, you can post a screenshot of the "scanning notifier" window you refer to. You could also try looking for crash logs from "SymAVScanServer", which is normally the process that is responsible for scans initiated by the user. NortonAutoProtect runs in the background and doesn't really display UI unless it finds a virus. 

Finally, if you could run the following command from  the Terminal application, we'll know the file that is causing the problems. First, open the Terminal application (in Applications/Utilities). Then, initiate the scan, and switch back to the Terminal application, and copy & paste the following command:

sudo fs_usage SymAVScanServer

(You'll be prompted for your password when you press return). Hopefully, if we time things right, this command will print out what file activity SymAVScanServer is performing. When you notice the scan window is not displaying progress anymore, press command-C if necessary to stop the command, and  copy & paste the output here. If we can't time it right, then possibly you could try and note what the last filename (if any) is displayed in the notifier window.

Thanks,

Ryan 

Ryan McGann Technical Director Norton Business Unit, Symantec
Kudos0

Re: Scanning Stops

Ryan,

Thanks for the quick reply.

The scans are automatic scans that occur when I connect an external drive or insert a CD/DVD. As you can see in the attached screen capture there can be multiple instances of NAV with nothing going on.

 

I did not find any crash logs for SymAVScanServer in the console.

I attempted to run terminal and the sudo fs_usage command and you can see my output in the screen capture above.  Did not seem to work. 

Also command-c did not stop the scan. 

Sometimes the NAV scan notification will say preparing to scan and then it will go blank like the one on the left above and then other times it will say scanning and get to 0 of xxxxx files and stall like on the left above.

Hope this helps... 

Message Edited by timjorourke on 04-30-2009 12:44 AM
Kudos0

Re: Scanning Stops

When you insert a DVD, this is the Auto Disk Scan feature. Its process name is called DiskMountNotify. If you have any crash logs for that process (which will be in your user ~/Library/CrashReports folder instead of /Library/CrashReports) please post them.

However DiskMountNotify uses SymAVScanServer to do its scanning, so if you don't have any crash reports for SymAVScanServer then something else is going on. Hopefully there will be some crash reports from DiskMountNotify to tell us more.

Unfortunately your screenshot didn't post correctly. If you send me a private message it might work better.

Thanks, 

Ryan

Ryan McGann Technical Director Norton Business Unit, Symantec
Kudos0

Re: Scanning Stops

I have had a look in my user ~/Library/Logs/CrashReports and I do not see any recent crashes.  There is one crash for DiskMountNotify from August 2006 but I do not think that is relevant since it is a version 10.1 crash on OS 10.4.7.

There are no other crashes listed other than all of the logs for NortonAutoProtect in my /Library/Logs/CrashReports.

Therefore no DiskMountNotify or SymAVScanServer crashes located.

I did PM the screenshot so let me know if it works.

Thanks,

Tim 

This thread is closed from further comment. Please visit the forum to start a new thread.