Main Forum > Tweaking.com Support & Help

Deceptive progress counter in disk clean-up, (Scan & Repair drive)

<< < (2/2)

Boggin:
Okay, but I'm not sure why you are doing a disk cleanup, or do you mean something else ?

Catullus:
Sorry about that, I used the wrong term, I should have said 'Scan and Repair'. I was thinking 'diskclean'. Of course, running overnight did not work out, I would not have been able to monitor the progress counter, so I had to postpone to yesterday, March 17. I started the Scan and Repair process at 0800 and it ran until 1545. At 1545 the scan stopped, for a moment or two, the PC screen showed the WIN start up screen, and then immediately the P.C. launched into' Scan and Repair' again. That had me worried, because it looked as if the software  system had gone recursive. My concern was 'how do I stop this recursion without severely damaging my software environment?' I let the system run while I tried to formulate a plan of action, eventually, the only reasonable interrupt that I could think of was to let the Scan and Repair process run to completion and to intervene when the WIN start up screen popped up again. To my great relief the second pass of the Scan and Repair process terminated after it had finished its work on the first HDD, removing the need for manual intervention.

My original post about the 'frozen' progress counter was confirmed, it sat  there stubbornly indicating '10% complete' during the entire seven and three quarter hour process pass for the three HDD. I followed your process rigorously, yes, including complete disconnect from the primary a.c. supply by the simple expedient of disconnecting the a.c. supply connector, and a one minute wait to allow capacitors in the p.s.u. to discharge fully.

I can confirm that I used my sysadmin account and that 'safe mode with networking' was the mode of operation, also that the wireless communication path was shut off, as indicated by the red cross on the icon.

The P.C. is connected to my DSL gateway and router via a hard wired connection, not WIFI. I consider the wireless link to be less secure than the hard wired connection.

In case you need to know these things, I have included some system information about the P.C. I am using:

HP TouchSmart 310-1125f, 8GB RAM, HP Product number BV551AA#ABA, serial number 4CS1150KP9. AMD Vision c.p.u.
I internal HDD, 2 external HDD via USB 2.

Operating system WIN 10 Home, 64 bit.

Boggin:
When you say "Scan and Repair" are you talking about a chkdsk ?

When you ran the Windows Repair program as well as the Scan and Repair did you have the external drives connected ?

While you can run a chkdsk against ext. drives you must put their drive letter into the cmd such as chkdsk d: /f or chkdsk d: /r with c: being the volume on the internal drive.

I think it would be best to run the Windows Repair program with the ext. drives unplugged.

Catullus:
O.K. I note your comments about chkdsk and the two external HDD.

There seems to be a little confusion between my use of two different names for the disk clean up utility involved with this incident. The only HDD clean-up tool used during the current exercise was the one incorporated in the 'Tweaking' utility, (Scan and Repair module). Knowing no better, I simply worked my way step by step through the process defined by the row of module names on the home page of 'Tweaking', working from left to right on the screen; starting with the hard reset and Safe Mode set-up.

Why should I run the 'Tweaking' disk cleaner " Scan and Repair" on the external drives separately from the internal HDD?
Your software seems to handle the task well, apart from the 'frozen' progress counter. ( And the recursion! it is of interest to note that the recursion event mentioned did not happen during a previous pass through the complete 'Tweaking' process a few days ago, so it took me by surprise this time round the loop.

I tend to think of the three HDD in my hardware system as a single large storage resource, hardware partitioned.
Each HDD is dedicated to a different function; e.g:
 Internal HDD, operating system, hardware drivers etc, and application software, (e.g. FireFox, Open Office, Tweaking etc.).
 HDD 1, Library,
 HDD 2, Back-up repository.

Boggin:
I assume you are talking about Option 3 where the second option will run a chkdsk on the next reboot ?

That will only scan the internal drive by default.

When you have ext. drives plugged in, that could confuse the operation.

Say your ext. drives are F: and G:

To perform a chkdsk /f or chkdsk /r on those you would need to open a Command Prompt (Admin) and enter chkdsk x: /f or /r where x is the drive letter.

The program would not perform a chkdsk on ext. drives.

Navigation

[0] Message Index

[*] Previous page