HDD failure imminent. What to do?
Let me repeat again, the thumb drive was not inserted during the attempted data transfer, when there was a problem with booting as lived CD instead of frugal install.
Two differenf things are going on here. (1) I am trying to set up a temporary frugal install with savefile on USB drive, until my new drive gets delivered next week, In the meantime, (2) I realize that the full drive sda2 is going to be problematic until I move some data off it, so I am interested in transferring some date between drives.
As I recall, there is no option in the savefile dialog to put it on a USB thumb drive.
Two differenf things are going on here. (1) I am trying to set up a temporary frugal install with savefile on USB drive, until my new drive gets delivered next week, In the meantime, (2) I realize that the full drive sda2 is going to be problematic until I move some data off it, so I am interested in transferring some date between drives.
As I recall, there is no option in the savefile dialog to put it on a USB thumb drive.
Last edited by nubc on Sat 09 Sep 2017, 04:46, edited 1 time in total.
I understand that.
Maybe I am misunderstanding this statement by you.
Maybe I am misunderstanding this statement by you.
I understand that as saying it is running in the pupmode for a live CD and not the pupmode for a USB flash drive.Slacko was running as a live CD.
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 thought transferring data was a problem, because the hard drives where not working correctly.I realize that the full drive sda2 is going to be problematic until I move some data off it, so I am interested in transferring some date between drives.
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)
The flash drive is not relevant during the data transfer operation, as it has been completely removed from the system. Instead, one or both hard drives are connected, and I want the frugal install to boot. Instead, with both drives connected, the CD does not boot the frugal install, but instead it boots as a live CD. Sorry if I am repeating myself. I would say there is a problem with boot order in BIOS.
Well, as you can see, there are issues. But I did get the 2TB hdd to boot as a single drive, frugal install. You are right, I need to move some data off the full drive. I'm not sure what pupmode is, but I am not running a live USB thumb drive in any way. There WAS a savefile on the USB drive, that is all. That savefile has been deleted, and I have quickly brought this new session up to a satisfactory quitting place. Before long I will attempt to create another savefile on the USB. It's going to be a long 4 days before I get a new drive.
Last edited by nubc on Sat 09 Sep 2017, 05:08, edited 1 time in total.
If you do what I said about changing pmedia=cd to pmedia=usbflash.As I recall, there is no option in the savefile dialog to put it on a USB thumb drive.
It for sure will offer saving to USB.
To make sure any save you have made for the USB thumb drive is not an issue.
Delete it and start with a fresh save, after making the pmedia change.
And booting fresh with no save.
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)
That is why I suggested checking settings in the bios and making sure all settings look correct for your setup.I would say there is a problem with boot order in BIOS.
Bios's can hick up and sometimes need setting checks and resets.
Just something to make sure is correct.
Boot device order, is something that always needs changed in the bios, if you are changing the normal boot device to use.
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)
On acting up hard drives.
do not overlook the possibility of corrupted or fragmented file system.
Gparted can check Linux formats.
Have to use Windows chkdsk and defrag programs to check ntfs or fat32 formats.
do not overlook the possibility of corrupted or fragmented file system.
Gparted can check Linux formats.
Have to use Windows chkdsk and defrag programs to check ntfs or fat32 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)
Even though I deleted the savefile, there exists a mounted directory by the same name in the upper level of directories. Now deleted.
Can you be more specific about the location of that pmedia setting. Is pmedia limited to the USB drive, or does it relate to the entire session? I did a pfind search for pmedia, got nothing.
Except for sda1 (mounted) all the directories in the upper level of the USB are empty.
Can you be more specific about the location of that pmedia setting. Is pmedia limited to the USB drive, or does it relate to the entire session? I did a pfind search for pmedia, got nothing.
Except for sda1 (mounted) all the directories in the upper level of the USB are empty.
This is about making the USB flash drive install of Puppy, boot in the proper pupmode, for running Puppy from a USB flash drive.
On the USB flash drive will be a boot config file.
The file should be one of these:
isolinux.cfg
OR
syslinux.cfg
If Grub4dos bootloader is on the USB flash drive and used to boot it.
menu.lst is used.
In Rox file manager navigate to the file you have.
Left click on it to open it in a text editor.
Example:
isolinux.cfg
That tells the Puppy boot process that it is on a USB flash drive and to operate for running from a USB flash drive.
If Puppy is installed by using the Puppy Universal Installer.
The installer would have made this change based on what you installed Puppy on.
On the USB flash drive will be a boot config file.
The file should be one of these:
isolinux.cfg
OR
syslinux.cfg
If Grub4dos bootloader is on the USB flash drive and used to boot it.
menu.lst is used.
In Rox file manager navigate to the file you have.
Left click on it to open it in a text editor.
Example:
isolinux.cfg
Change pmedia=cd to pmedia=usbflash.default puppy
display boot.msg
prompt 1
timeout 50
F1 boot.msg
F2 help.msg
F3 help2.msg
label puppy
kernel vmlinuz
append initrd=initrd.gz pmedia=cd
That tells the Puppy boot process that it is on a USB flash drive and to operate for running from a USB flash drive.
If Puppy is installed by using the Puppy Universal Installer.
The installer would have made this change based on what you installed Puppy on.
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)
There is no such boot file on the thumb drive. Maybe a file gets created during the process of creating the savefile. So perhaps I have to go through the motions of creating the savefile, and then go back and edit some file that was created. But as I recall, there was no such file on the thumb drive when I created the first savefile, or at least I didn't see one, and I was looking. By the way, the process of creating the savefile was very lengthy, like 20 minutes. Is that normal? This is a frugal install that boots from a CD. As far as I kmow, I'm not booting a USB drive. I'm only storing the savefile there.
Sorry, somehow I got the idea you where booting from and running Puppy installed on a USB flash drive.
So, unless both are USB 3.0. Writing a save to the USB flash drive can be slow.
Even USB 3.0 is not as fast as a hard drive.
Also, how much needs to be written to the save, can affect the time it takes to initially make the savefile or update it.
The read write speed of the USB flash drive and the USB port you have it connected to, controls the speed.This is a frugal install that boots from a CD. As far as I know, I'm not booting a USB drive. I'm only storing the savefile there.
the process of creating the savefile was very lengthy, like 20 minutes. Is that normal?
So, unless both are USB 3.0. Writing a save to the USB flash drive can be slow.
Even USB 3.0 is not as fast as a hard drive.
Also, how much needs to be written to the save, can affect the time it takes to initially make the savefile or update it.
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)
Okay, this time the USB savefile worked. When I reacquired Desktop there was a floppy disc icon, named save. I clicked it, and got this message
What is this? What did I do?
EDIT: For some reason, every other reboot is a live CD rather than the frugal install.
Code: Select all
Saving RAM to savefile...
EDIT: For some reason, every other reboot is a live CD rather than the frugal install.
Usually if the save file or folder is on a USB flash drive.
A save icon is placed on the desktop.
Use it to manually save any time you wish.
Normally, to keep the number of writes to the flash drive as low as possible. Saves are only updated at shutdown or reboot.
Suppose to make the flash drive last longer, because they have a limited number of writes before failure.
A save icon is placed on the desktop.
Use it to manually save any time you wish.
Normally, to keep the number of writes to the flash drive as low as possible. Saves are only updated at shutdown or reboot.
Suppose to make the flash drive last longer, because they have a limited number of writes before failure.
USB flash drives can withstand between 10,000 to 100,000 write/erase cycles, depending on the memory technology used.
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)
Do not have the live CD in the CD player when you boot.For some reason, every other reboot is a live CD rather than the frugal install.
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)
When the computer reboots to live CD, it does not read the /slackosave.3fs file, but instead reads only puppy_slacko_5.7.0.sfs main file. When the computer reboots to frugal install, it reads the /slackosave file, and then the puppy_slacko.sfs file.
Last edited by nubc on Sun 10 Sep 2017, 20:15, edited 2 times in total.
That doesn't work. The frugal boots from CD.bigpup wrote: Do not have the live CD in the CD player when you boot.
EDIT: Maybe if I remove the CD just before "Searching for Puppy files..."
Nah, that's too tricky. Every other reboot, it does not load the slackosave file. In the case where it boots to live CD, it may be getting the Puppy files off the CD instead of the USB. When it boots frugal, it gets the slackosave file and the sfs files off the USB, probably.
So, the problem is the save file is only getting seen sometimes.nubc wrote:When the computer reboots to live CD, it does not read the /slackosave.3fs file, but instead reads only puppy_slacko_5.7.0.sfs file. When the computer reboots to frugal install, it reads the /slackosave file, and then the puppy_slacko.sfs file.
I am having confusion by how you are stating what you are booting.
I am understanding that as you are booting using Slacko installed on a CD.When the computer reboots to live CD
It sometimes finds the save file and sometimes does not.
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)
When you burn the Slacko iso image to a CD, you have installed Slacko on the CD.Slacko installed on CD, probably not. Slacko .iso burned to CD, and yes
Usually called a live Slacko CD.
Exactly where is the savefile located?
Be very specific with location details!!!!!
Is this the only save file or are there other slackosaves?
If there are other slackosaves.
Exact names and locations.
Be specific with info!!!!
Where the savefile is located can affect how the live Slacko CD finds a savefile to use.
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)