Pudd takes 12 hours to backup 500GB?

[hundido]

Pudd:
Trying to back up the sda1 partition.
It seemed pretty straightforward. sda1 is 500 GB. The usb I'm trying to copy to is 2 TB. Using Pudd in Fossapup 9.5. It's been going for about 12 hours now.

Are there any Pudd secrets I should know? Did I find a creative way to break it?

I clicked on another drive to try to listen to something while it was being copied. It looked like it opened, but nothing ever started playing. I tried to get to the puppy linux forum from that computer, and the loading circle spins forever. I tried to unmount the drive I clicked on to get something to listen to while it copies, and I get a pink error box saying:

Code: Select all

FAILURE! One or more processes (programs) are currently using the partition.  Here they are: kernel 9099

How did I break it? What do I do?

[Clarity]

Have you tried to Cntrl-Alt-Bksp to get to console? Or does Cntrl-Alt-F2 take you to a console login screen?

Or, if you can start a desktop app, navigate the desktop Menu and how about Leave to Shutdown/Reboot/Console.

[hundido]

Just clicking console gets me to the console.

How do I know if Pudd is stuck or if it's still copying?

[hundido]

@Clarity
I tried the things you suggested.
Cntrl-Alt-F2 didn't seem to do anything.
Cntrl-Alt-Bksp shut off x, and what did it tell me to type, something jwm, to get back into the desktop.

I no longer have the box that Pudd is copying. I clicked on sdc1, and it has the list of my top level folders, all in red, with exclamation points next to them.

My goal is to copy sda1 to sdc1. How do I find out if Pudd is still trying to do that, or did leaving jwm shut down Pudd, and now I need to start over?

[Clarity]

Wow! Seems that PUDD is misbehaving on your PC.

I would cross-my-fingers, shutdown. Reboot your PC and try again.

I would not expect PUDD to have the necessary understanding to pick up where it left off or recover, but it might be worth it to see. SO, Once back on desktop, mount the sdc1 partition and see if a ???.img file is present. This file would be the outcome of what PUDD was suppose to complete for you.

Fingers crossed that sda1 was not clobbered by PUDD

[Clarity]

Based on your earlier post, I ask:

• Are you trying to create an "image" of your partition?

• OR, Are you just trying to replicate the partition on sdc1?

If you are trying to merely make a copy of the partitions contents on sdc1, try "rsync" terminal command to accomplish that.

Just an idea

[dogcat]

Just clicking console gets me to the console.

How do I know if Pudd is stuck or if it's still copying?

Pudd gives no feedback in the terminal until it finishes.
Patience is required, it takes my system 19 hours to image a 500MB drive using Pudd writing to an SSD drive attached to a USB3 port.

I check progress on Pudd by opening a separate terminal and running the command

Code: Select all

df

Then I wait a minute and run the command again in the same terminal window.

The command df will show all drives and how much data is on each drive. Look at the drive Pudd is copying to, the total data on that drive will increase each time you run df if Pudd is still running.

[Flash]

Yes, rsync might be the better choice. Copy fast uses rsync.

copy-fast-2.7.pet

(12.6 KiB) Downloaded 30 times