[PiShrink] Creating new /etc/rc.local does not end - takes forever.

GoodBoy

Hi,

I am trying to run PiShrink on Linux 18.3 VM. I have done everything correctly (I believe!) and when I try to run pishrink on my image (newimage.img) that is 62GB, I get the line:

creating new /etc/rc.local

... which is endless.

I don't really know what to do. I can't find other people with my problem. Any help? Please!

Thank you!

GoodBoy

bump

mitu

Don't bump your topics so soon, this is an international forum and it takes time for other users to see and respond to your questions.
That being said, are you sure that you're waiting long enough for pishrink to create your shrunk down image ? I haven't used pishrink, but I imaging that for a large-ish image, it takes some time to transfer all the files from an existing image to a new one, especially if there are lots of small files on the original image.

KN4THX

@mitu I just used pi shrink for the first time on a 32gb image and it took 5-10 minutes to shrink to a 15gb IMG. I was using a new Evo 860 SSD on my x230 though. I did not receive that error. It almost seems to me as if they are trying to write the original SD card image to the SD card where the image source exists.

Try shrinking the image to to ~/

Ranma

It can take a while, but it's worth it. I have a 64GB image and it's taken Pishrink about half an hour to shrink it. Then, when you pop it back into the Pi, it can take another 30 mins to restore.

Actually, I have a question about Pishrink, but I'll start another thread...

GoodBoy

@mitu

My apologies.

I would say I waited about an hour and it was still trying to create the etc/rc.local

It is a 64GB card, with about 32GB used space. I have just put the image on a 128GB card and I am going to camp this one out for a few hours.

If that doesn't work, I am thinking about removing the etc/rc.local and retrying it. Not too sure what that will achieve but it's worth a go.

mitu

@GoodBoy said in [PiShrink] Creating new /etc/rc.local does not end - takes forever.:

If that doesn't work, I am thinking about removing the etc/rc.local and retrying it. Not too sure what that will achieve but it's worth a go.

Don't remove the file, just check if there's activity on the system while the program runs. If you're running in a VB guest, just look at the disk activity 'led' of the virtual machine, or use the top command to see the system load.

GoodBoy

@mitu I've ran the top command to see the running tasks. I stopped the pishrink.sh script and restarted it - but I did not see a change in the number of running tasks.

From the tutorials that I have watched, the creation of etc/rc.local is fast and then you wait for the shrinkage.

I think I am going to camp this one out 2 hours, and if that doesn't work then maybe retry again from scratch (this is my 3rd time). Not too sure to be honest.

GoodBoy

Unless there would be an alternative way to resize the partitions in Linux? Or delete the empty space?

mitu

@GoodBoy A load average of 4.42 indicates some serious activity on the system. I'd say let it run for a bit.

Unless there would be an alternative way to resize the partitions in Linux? Or delete the empty space?

parted - I think - can do it. It might have a graphical interface, but haven't used it in a while.

cyperghost

@mitu gparted got a gui

GoodBoy

@mitu I think it has been an easy 2 hours now and it is still not budging, but it still has a load average of about 4.2.

I think I should just kill the switch?

Gparted is worth a try. If nothing works at all I suppose I can copy all the roms to my PC and rebuild it entirely onto a new card. Yikes...

ByteThis

@GoodBoy said in [PiShrink] Creating new /etc/rc.local does not end - takes forever.:

@mitu

My apologies.

I would say I waited about an hour and it was still trying to create the etc/rc.local

It is a 64GB card, with about 32GB used space. I have just put the image on a 128GB card and I am going to camp this one out for a few hours.

If that doesn't work, I am thinking about removing the etc/rc.local and retrying it. Not too sure what that will achieve but it's worth a go.

@GoodBoy Why are you trying to shrink the image if you are going to place it on a 128 GB card ? Do a backup of the image..transfer it to the 128GB card and .you will have to expand the filesystem to access the full space on the card