Can only boot Fatdog 710 if I do not load savefile
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
Can only boot Fatdog 710 if I do not load savefile
It's funny, I had been away from my Fatdog 710 machine for about 3 or 4 months due to other work on different machines and I noticed two things:
1) I was missing my wireless dongle (this means I borrowed it for another machine)
and
2) It will not boot unless I choose NOT to use a savefile, in which case it boots fine.
3) I found a dongle laying on my desk from another computer and put it in so I have wireless now.
But the big question is, how can I get my read/write OS back again. Currently, I cannot write to the hard drive sda1. But I noticed something by comparing to another machine's fd64save.ext4:
The permissions on the machine that works are: Read for Owner Group and World, and Write for Owner, nothing for Exec. On the machine where the savefile will not load it is: Read Owner Group and Exec Owner Group, with nothing able to Write. Unfortunately, I cannot write so if I change the flag it won't persist.
When it boots, it mentions something about aufs/new_root or new root
I don't really know what to do - I could try deleting the savefile - is that a good idea and start over?
I tried redoing the savefile a couple times but it didn't work.
Any ideas appreciated for how to get my hard-drive reading and writing properly again.
Thanks.
1) I was missing my wireless dongle (this means I borrowed it for another machine)
and
2) It will not boot unless I choose NOT to use a savefile, in which case it boots fine.
3) I found a dongle laying on my desk from another computer and put it in so I have wireless now.
But the big question is, how can I get my read/write OS back again. Currently, I cannot write to the hard drive sda1. But I noticed something by comparing to another machine's fd64save.ext4:
The permissions on the machine that works are: Read for Owner Group and World, and Write for Owner, nothing for Exec. On the machine where the savefile will not load it is: Read Owner Group and Exec Owner Group, with nothing able to Write. Unfortunately, I cannot write so if I change the flag it won't persist.
When it boots, it mentions something about aufs/new_root or new root
I don't really know what to do - I could try deleting the savefile - is that a good idea and start over?
I tried redoing the savefile a couple times but it didn't work.
Any ideas appreciated for how to get my hard-drive reading and writing properly again.
Thanks.
Could you print your menu.lst file listing for fatdog,
especially the savefile=......... portion.
http://distro.ibiblio.org/fatdog/web/fa ... tions.html
There is a certain depth of folders that fatdog will dig in to find the savefile.
You could also try ---> savefile=ask
_____________________________________
Something I do in an emergency --->
I run grub4dos by shinobar (available in most puppies)
and it makes a new menu.lst
______________________________
especially the savefile=......... portion.
http://distro.ibiblio.org/fatdog/web/fa ... tions.html
There is a certain depth of folders that fatdog will dig in to find the savefile.
You could also try ---> savefile=ask
_____________________________________
Something I do in an emergency --->
I run grub4dos by shinobar (available in most puppies)
and it makes a new menu.lst
______________________________
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
Fatdog menu.lst file
I boot that Fatdog machine either of two ways - either off of a CD or off of a flash stick. I don't have a menu.lst that I'm aware of. At least I can't yet find one. I'll keep looking for it.
don570 wrote:Could you print your menu.lst file listing for fatdog,
especially the savefile=......... portion.
http://distro.ibiblio.org/fatdog/web/fa ... tions.html
There is a certain depth of folders that fatdog will dig in to find the savefile.
You could also try ---> savefile=ask
_____________________________________
Something I do in an emergency --->
I run grub4dos by shinobar (available in most puppies)
and it makes a new menu.lst
______________________________
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
I can try the savefile= but it will take me longer than 9 s
Can I set it to longer than 9s? I guess I can hit escape to get a prompt but it crashed - I'll try again.
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
I have to get the syntax of savefile=
At the prompt.
I need to boot and find any savefiles I have and somehow figure out how to issue:
savefile=local:path
A simple example would help so I know I have the syntax.
But I wonder if I go to the prompt are there a bunch of other things that need to be on the command line? It complained that it couldn't find the kernel.
I need to boot and find any savefiles I have and somehow figure out how to issue:
savefile=local:path
A simple example would help so I know I have the syntax.
But I wonder if I go to the prompt are there a bunch of other things that need to be on the command line? It complained that it couldn't find the kernel.
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
My savefile is on sda1
So would savefile=local:sda1/fd64save.ext4 work at the command prompt?
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
Also, can I dynamically load the savefile?
I have booted the machine without the savefile currently.
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: I have to get the syntax of savefile=
I am usingPappyPuppy wrote:savefile=local:path
A simple example would help so I know I have the syntax.
Code: Select all
savefile=direct:device:sda3:/fatdog710/fd64save
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
I've decided to create a save directory a new one
so it's /dev/sda1/fd64save
now.
now.
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
I'll try yours if this doens't wokr
It's booting off the flash now. OIt takes 5 minutes.
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
Creating a new savefile does not work
I have no idea why it won't boot.
Is there a log I could post?
Is there a log I could post?
- L18L
- Posts: 3479
- Joined: Sat 19 Jun 2010, 18:56
- Location: www.eussenheim.de/
Re: I've decided to create a save directory a new one
PappyPuppy wrote:so it's /dev/sda1/fd64save
now.
Why not
Code: Select all
savefile=direct:device:sda1/fd64save.ext4
-
- Posts: 409
- Joined: Sat 01 Oct 2016, 00:27
I will try your idea I just can't do it for a couple days
I'll post when I try.