Delete a pup-save file - how to?

Booting, installing, newbie
Post Reply
Message
Author
User avatar
LNSmith
Posts: 126
Joined: Thu 28 Mar 2013, 14:24
Location: A little north fr. Sydney, AU

Delete a pup-save file - how to?

#1 Post by LNSmith »

G'day all.

I wish to delete the pup-save file stretch-save-pup.2fs
I try this with Rox Filer.
When I select the file and 'delete' I read the error message:
Input/output error.
and
There was one error.

I cannot delete the file - even when I run Tahr Pup,
advice about what's going on here is welcome!

Leslie

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

Re: Delete a pup-save file - how to?

#2 Post by musher0 »

LNSmith wrote:G'day all.

I wish to delete the pup-save file stretch-save-pup.2fs
I try this with Rox Filer.
When I select the file and 'delete' I read the error message:
Input/output error.
and
There was one error.

I cannot delete the file - even when I run Tahr Pup,
advice about what's going on here is welcome!

Leslie
Hi Leslie.

You cannot delete a pupsave file while in use.

So it is quite surprising indeed that you cannot delete a save file for stretch
while the TahrPup is using its own.

Do you remember playing with its permissions, perhaps?

IHTH.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

User avatar
LNSmith
Posts: 126
Joined: Thu 28 Mar 2013, 14:24
Location: A little north fr. Sydney, AU

#3 Post by LNSmith »

Hello Musher:

Thank you for your reply. You ask, "Did I play with permissions?"
Your "Q" prompted me to consider the symptoms.
i NOW CONSIDER THE PROBLEM IDENTIFIED AND POTENTIALLY RESOLVED.
THANKS MUSHER!
For anyone interested: Read below.

I note that permissions are given as: rwx, rwx, rwx.
I am operating as root.
I can write to sda1 - the drive where stretch-pup-save is located.
This is a frugal installation.
I confirm I am using Tahr-Pup - booted without the Tahr-save option.
This info strongly supports the idea that I have a hardware problem.

Recent discovery: Dr. Google says: "Input/Output errors during file-system access attempts generally mean hardware issues."

Sometimes a 'nudge' is enough to set the grey matter on the right track.

Extra info:
(1) I note that some files on sda1 are accessible. (Checked one or two)
(2) I note the the file system on sda1 is NTFS.
(3) I observed that I could NOT boot stretch puppy WITH THE SAVE FILE.
I am booting with a live CD.
(4) I observed that I CAN boot stretch puppy WITHOUT the save file.
(5) Using Puppy Linux identifying/resolving the problem will be straightforward.
(6) Using Windows I would need to re-install everything.

Puppy Linux is a friendly OS!!
THANKS MUSHER

Leslie

Leslie.

User avatar
puppyluvr
Posts: 3470
Joined: Sun 06 Jan 2008, 23:14
Location: Chickasha Oklahoma
Contact:

#4 Post by puppyluvr »

:D Hello,
Boot into ram, and without mounting the drive, open the terminal and:
e2fsck /dev/sda1
Close the Windows, and open your eyes, to a whole new world
I am Lead Dog of the
Puppy Linux Users Group on Facebook
Join us!

Puppy since 2.15CE...

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#5 Post by bigpup »

Please help to keep some order to this forum.

In the future, do not start topics asking questions in the How To section of the forum.
This section is for posting topics where you tell people how to do something.
You provide the information on how to do it.

If you have a question in general.
Ask it in the Beginners Help or Users sections.
About a specific Puppy version, you can ask in that Puppy version topic.
Hardware issues can be asked in the Hardware section.
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 :shock:
YaPI(any iso installer)

User avatar
Mike Walsh
Posts: 6351
Joined: Sat 28 Jun 2014, 12:42
Location: King's Lynn, UK.

#6 Post by Mike Walsh »

@Les:-

One small point. I do hope that when you re-create a new 'stretch-save', you create it as ext3 instead.

Ext2 is known to corrupt easily, despite the fact it's the recommended one to use with,say, a flash drive.....because of the lack of overhead of the 'journalling' that's built-in to ext3. That additional overhead is what enables an ext3 file-system to recover from errors, when combined with the e2fsck command.


Mike. :wink:

musher0
Posts: 14629
Joined: Mon 05 Jan 2009, 00:54
Location: Gatineau (Qc), Canada

#7 Post by musher0 »

HI Leslie.

I'm glad that I could be of some help.
Best of luck with your new hard drive!

BFN.
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)

Post Reply