Cannot unmount partition to shut down
Cannot unmount partition to shut down
Hi
I have worked with puppy linux since 2010, but this is the first time I have to report this problem:
I'm have been using xenial pup 64 since released 2 months ago, everything ok, but recently, during shut down or reboot, the system freezes, as you can see in the picture. This happens with save file or without save file. That message appears just before it should reboot or shut down, and freezes.
When loaded as an original pup, without save file, it says it cannot unmount the ext4 partition.
What do you think? Thanks
I have worked with puppy linux since 2010, but this is the first time I have to report this problem:
I'm have been using xenial pup 64 since released 2 months ago, everything ok, but recently, during shut down or reboot, the system freezes, as you can see in the picture. This happens with save file or without save file. That message appears just before it should reboot or shut down, and freezes.
When loaded as an original pup, without save file, it says it cannot unmount the ext4 partition.
What do you think? Thanks
- Attachments
-
- 66.png
- (182.97 KiB) Downloaded 662 times
This is after you do a complete power off of computer for minimum of 1 minute?
Xenialpup is installed on what device?
Hard drive, USB flash drive, CD, etc.....?
What format is the device's partition Xenialpup is installed on?
Is the partition it is talking about the one Xenialpup is installed on?
Can you get it to boot from a live USB or CD of Xenialpup not using a save?
If yes.
Try using Gparted to do a check of the partition.
If it finds any errors.
Keep running checks on it until no errors.
My first idea is the ext4 file system is corrupted or has errors.
Xenialpup is installed on what device?
Hard drive, USB flash drive, CD, etc.....?
What format is the device's partition Xenialpup is installed on?
Is the partition it is talking about the one Xenialpup is installed on?
Can you get it to boot from a live USB or CD of Xenialpup not using a save?
If yes.
Try using Gparted to do a check of the partition.
If it finds any errors.
Keep running checks on it until no errors.
My first idea is the ext4 file system is corrupted or has errors.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
Hi Bigpupbigpup wrote:This is after you do a complete power off of computer for minimum of 1 minute?
Xenialpup is installed on what device?
Hard drive, USB flash drive, CD, etc.....?
What format is the device's partition Xenialpup is installed on?
Is the partition it is talking about the one Xenialpup is installed on?
Can you get it to boot from a live USB or CD of Xenialpup not using a save?
If yes.
Try using Gparted to do a check of the partition.
If it finds any errors.
Keep running checks on it until no errors.
My first idea is the ext4 file system is corrupted or has errors.
This is when I reboot or shutdown. Just before it should power off or boot the system.
My xenial pup is installed in an usb flash drive, fat32.
The partition with the problem is an ext4, it is accessible and writable.
I can boot xenial pup without save file but the problem persists.
I will try with gparted, as you suggest
- Mike Walsh
- Posts: 6351
- Joined: Sat 28 Jun 2014, 12:42
- Location: King's Lynn, UK.
I think that ext4 file-system's your problem, TBH.
It's standard practice to use ext4 on the majority of mainstream distros.....all of which are designed for a 'full' install (where the OS 'takes over' the partition).
Folks come to Puppy from other Linux OSes, and immediately they're flummoxed when you tell them that Puppy works best with ext3.
'But I've always used ext4. Why should I change now?' And so they go ahead and install, using ext4.....and 9 times out of 10, they're here on the forum a while later, complaining that Pup's not working properly. And then get all snotty when you try to point out it was their mistake because they ignored the advice given.
I'm not saying that's the case here.....especially if you've been using Pup for a few years. But ext4 is something of an 'oddball' file-system where Pup's concerned.....
Have you always used it.....or was this something of an experiment?
Mike.
It's standard practice to use ext4 on the majority of mainstream distros.....all of which are designed for a 'full' install (where the OS 'takes over' the partition).
Folks come to Puppy from other Linux OSes, and immediately they're flummoxed when you tell them that Puppy works best with ext3.
'But I've always used ext4. Why should I change now?' And so they go ahead and install, using ext4.....and 9 times out of 10, they're here on the forum a while later, complaining that Pup's not working properly. And then get all snotty when you try to point out it was their mistake because they ignored the advice given.
I'm not saying that's the case here.....especially if you've been using Pup for a few years. But ext4 is something of an 'oddball' file-system where Pup's concerned.....
Have you always used it.....or was this something of an experiment?
Mike.

Hi, I have ever used ext4 with previous puppy linux versions, without problems like this. By the way, I made memtest, no problems, and used the same puppy usb in other pc, and it boots, reboot and shut down perfectlyMike Walsh wrote:I think that ext4 file-system's your problem, TBH.
It's standard practice to use ext4 on the majority of mainstream distros.....all of which are designed for a 'full' install (where the OS 'takes over' the partition).
Folks come to Puppy from other Linux OSes, and immediately they're flummoxed when you tell them that Puppy works best with ext3.
'But I've always used ext4. Why should I change now?' And so they go ahead and install, using ext4.....and 9 times out of 10, they're here on the forum a while later, complaining that Pup's not working properly. And then get all snotty when you try to point out it was their mistake because they ignored the advice given.
I'm not saying that's the case here.....especially if you've been using Pup for a few years. But ext4 is something of an 'oddball' file-system where Pup's concerned.....
Have you always used it.....or was this something of an experiment?
Mike.
Did you make this ext4 format, using Gparted in Puppy or did some other Linux OPS?
There is now a 64bit ext4 format and Puppy does not know how to use it correctly.
Gparted in Puppy does 32bit ext4 formats.
There is now a 64bit ext4 format and Puppy does not know how to use it correctly.
Gparted in Puppy does 32bit ext4 formats.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
I did the ext4 with Ubuntu, 3 years ago.bigpup wrote:Did you make this ext4 format, using Gparted in Puppy or did some other Linux OPS?
There is now a 64bit ext4 format and Puppy does not know how to use it correctly.
Gparted in Puppy does 32bit ext4 formats.
If I run the precise puppy, this problem is not present. It is just happening with xenial 64 or 32.
I found a similar issue here: https://www.linuxquestions.org/question ... ow-898764/
Anything on this ext4 partition that has anything to do with Xenialpup?
You are using Xenialpup64 7.5?
You are using Xenialpup64 7.5?
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
Yes, I'm using xenialpup 7.5. Nothing in ext4, except the save file, but the problem is present with or withou save file.bigpup wrote:Anything on this ext4 partition that has anything to do with Xenialpup?
You are using Xenialpup64 7.5?
In this moment, I'm using the pup artful 17.11 as an alternative. It's very good, just that it is 32 bits. But it reboots and shui down perfectly, as was my xenial installation 2 month ago.
How exactly are you doing the boot so it does not use the save?
If the save is on the ext4 partition that is the common thing. Something could be wrong with it.
You could try checking the save for errors.
The save file can not be in use.
Mount the partition the save is on.
Open a terminal, and enter:
e2fsck /path to savefile
For example:
e2fsck /mnt/sda1/pupsave.2fs
To check a save folder use the method for checking a partition.
Check the partition the save folder is on.
To do the whole partition:
Need to boot from a live Puppy or a Puppy on a different partition to do a partition check.
(the partition must be unmounted)
Example:
partition sda1
e2fsck /dev/sda1
If the save is on the ext4 partition that is the common thing. Something could be wrong with it.
You could try checking the save for errors.
The save file can not be in use.
Mount the partition the save is on.
Open a terminal, and enter:
e2fsck /path to savefile
For example:
e2fsck /mnt/sda1/pupsave.2fs
To check a save folder use the method for checking a partition.
Check the partition the save folder is on.
To do the whole partition:
Need to boot from a live Puppy or a Puppy on a different partition to do a partition check.
(the partition must be unmounted)
Example:
partition sda1
e2fsck /dev/sda1
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
I will try as you said, however, the problem is present even is I run xenial pup without save filebigpup wrote:How exactly are you doing the boot so it does not use the save?
If the save is on the ext4 partition that is the common thing. Something could be wrong with it.
You could try checking the save for errors.
The save file can not be in use.
Mount the partition the save is on.
Open a terminal, and enter:
e2fsck /path to savefile
For example:
e2fsck /mnt/sda1/pupsave.2fs
To check a save folder use the method for checking a partition.
Check the partition the save folder is on.
To do the whole partition:
Need to boot from a live Puppy or a Puppy on a different partition to do a partition check.
(the partition must be unmounted)
Example:
partition sda1
e2fsck /dev/sda1
Earlier you posted this:
STRANGE!!
Run the check several times to see if it always says no errors.
Wonder if you have a drive going bad
Just Puppy luck it is acting up when using Puppy.
This is what I would do.
Delete the partition.
Make a new partition from the now unallocated space.
Format it to ext 3.
Try to copy anything on the ext4 partition you want to keep to some other location.
Boot Xenialpup from something other than the hard drive.
A live install on a USB flash drive or a CD/DVD.
The drive the partition is on cannot be mounted or at least the partition cannot be mounted.
Run Gparted and delete, partition, and format.
The thing is Gparted is doing the check using this same program. e2fsck.Tested with Gparted, no errors found...
STRANGE!!
Run the check several times to see if it always says no errors.
Wonder if you have a drive going bad

Just Puppy luck it is acting up when using Puppy.
This is what I would do.
Delete the partition.
Make a new partition from the now unallocated space.
Format it to ext 3.
Try to copy anything on the ext4 partition you want to keep to some other location.
Boot Xenialpup from something other than the hard drive.
A live install on a USB flash drive or a CD/DVD.
The drive the partition is on cannot be mounted or at least the partition cannot be mounted.
Run Gparted and delete, partition, and format.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
Maybe, I will need to do your suggestion. However, it's very strange that I can use this partition perfectly with precise puppy or artful, and Gparted found no errors.bigpup wrote:Earlier you posted this:The thing is Gparted is doing the check using this same program. e2fsck.Tested with Gparted, no errors found...
STRANGE!!
Run the check several times to see if it always says no errors.
Wonder if you have a drive going bad
Just Puppy luck it is acting up when using Puppy.
This is what I would do.
Delete the partition.
Make a new partition from the now unallocated space.
Format it to ext 3.
Try to copy anything on the ext4 partition you want to keep to some other location.
Boot Xenialpup from something other than the hard drive.
A live install on a USB flash drive or a CD/DVD.
The drive the partition is on cannot be mounted or at least the partition cannot be mounted.
Run Gparted and delete, partition, and format.
Thanks for your help, Bigpup. I have learned with you in this and other topics in this forum. Best wishes
I agree this is a strange one!
Xenialpup may be more sensitive to any errors in the file system.
You did post running e2fsck gives superblock errors.
Here is some good info on superblocks and how to fix the problem.
https://joshua14.homelinux.org/blog/?p=2294
Xenialpup may be more sensitive to any errors in the file system.
You did post running e2fsck gives superblock errors.
Here is some good info on superblocks and how to fix the problem.
https://joshua14.homelinux.org/blog/?p=2294
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
What is more strange is that this partition writes and reads normally, and can be mount and unmount as well, even when running xenial. The issue happens just when rebooting or shuting downbigpup wrote:I agree this is a strange one!
Xenialpup may be more sensitive to any errors in the file system.
You did post running e2fsck gives superblock errors.
Here is some good info on superblocks and how to fix the problem.
https://joshua14.homelinux.org/blog/?p=2294
I put a post in the Xenialpup64 7.5 topic about this issue.
666philb the developer of Xenialpup. May have some clue as to what may be happening or needs to know about the problem.
http://www.murga-linux.com/puppy/viewto ... 361#979361
666philb the developer of Xenialpup. May have some clue as to what may be happening or needs to know about the problem.
http://www.murga-linux.com/puppy/viewto ... 361#979361
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected
YaPI(any iso installer)
When I was a kid I wanted to be older.... This is not what I expected

YaPI(any iso installer)
Hi Bigpup. Great! I hope he has a solution.bigpup wrote:I put a post in the Xenialpup64 7.5 topic about this issue.
666philb the developer of Xenialpup. May have some clue as to what may be happening or needs to know about the problem.
http://www.murga-linux.com/puppy/viewto ... 361#979361
I made a new analysis, this time with Testdisk. It found no errors in the partition. More strange things