SSD-troubles with grubs
SSD-troubles with grubs
I have some remastered 64puppies on my hdd that never failed via Grub2 . Recently I bought my first SSD Kingston A400 240GB and the troubles began. Attempts to grub-install grub2 to the ssd always end with "Could not find device for /boot: Not found or not a block device".
So I moved the first time to Grub4dos. Installed it to the mbr of the ssd. The first impression was not bad, but now for change I end with "puppyxxx.sfs not found". Of course it is there, I can load it via the grub2 on my hdd. Tried pfix=ram, pmedia ataflash (which I use in grub2). It seems like my Grub4dos has problems with remastered puppies and even save files.
Any help will be appreciated.
So I moved the first time to Grub4dos. Installed it to the mbr of the ssd. The first impression was not bad, but now for change I end with "puppyxxx.sfs not found". Of course it is there, I can load it via the grub2 on my hdd. Tried pfix=ram, pmedia ataflash (which I use in grub2). It seems like my Grub4dos has problems with remastered puppies and even save files.
Any help will be appreciated.
- Revolverve
- Posts: 255
- Joined: Sat 08 Nov 2008, 21:01
- Location: 45°17'28.8"N 72°16'08.8"W_avatar/ mira.ca
What version of Grub4dos bootloader config are you using?
Is the first partition on the SSD flagged as boot?
Are the remastered Puppies now on the SSD?
Is the SSD the first boot device in the computers boot device order setting?
Try just moving the save to the SSD, to the same location as the remastered Puppy is installed.
Grub4dos bootloader may have problems if you gave the remasters some strange name or put them in a strange name directory.
Is the first partition on the SSD flagged as boot?
Are the remastered Puppies now on the SSD?
Is the SSD the first boot device in the computers boot device order setting?
Try just moving the save to the SSD, to the same location as the remastered Puppy is installed.
Grub4dos bootloader may have problems if you gave the remasters some strange name or put them in a strange name directory.
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 tried
-ext2 and ext4 on the ssd (sdb1)
-grub4dos v1.7, 1.8, 1.9.2 (latest)
-various boot options
-for trial to add a save folder and the original zdrv.sfs which are not present in my remastered puppy
boot flag on sdb is OK
still the same result
https://uloz.to/!R0fQlpgO1NPt/grub4dos-jpg
The relevant part of menu.lst: both entries are almost identical, only the first is renamed. Both fail
# menu.lst produced by grub4dosconfig-v1.9.2
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
# Frugal installed Puppy
title Puppy xenialpup7.0.8.5 (sda8/xen6)
uuid 038b3311-5e6b-4089-abce-114e249289a3
kernel /xen6/vmlinuz pmedia=atahd psubdir=xen6 pfix=fsck
initrd /xen6/initrd.gz
title Puppy xenialpup7.0.8.5 (sdb1/xenssd)
uuid 54b5806d-ecba-40c7-a6bc-481be3cc8de4
kernel /xenssd/vmlinuz pmedia=atahd psubdir=xenssd pfix=fsck
initrd /xenssd/initrd.gz
-ext2 and ext4 on the ssd (sdb1)
-grub4dos v1.7, 1.8, 1.9.2 (latest)
-various boot options
-for trial to add a save folder and the original zdrv.sfs which are not present in my remastered puppy
boot flag on sdb is OK
still the same result
https://uloz.to/!R0fQlpgO1NPt/grub4dos-jpg
The relevant part of menu.lst: both entries are almost identical, only the first is renamed. Both fail
# menu.lst produced by grub4dosconfig-v1.9.2
color white/blue black/cyan white/black cyan/black
#splashimage=/splash.xpm
timeout 10
default 0
# Frugal installed Puppy
title Puppy xenialpup7.0.8.5 (sda8/xen6)
uuid 038b3311-5e6b-4089-abce-114e249289a3
kernel /xen6/vmlinuz pmedia=atahd psubdir=xen6 pfix=fsck
initrd /xen6/initrd.gz
title Puppy xenialpup7.0.8.5 (sdb1/xenssd)
uuid 54b5806d-ecba-40c7-a6bc-481be3cc8de4
kernel /xenssd/vmlinuz pmedia=atahd psubdir=xenssd pfix=fsck
initrd /xenssd/initrd.gz
- Revolverve
- Posts: 255
- Joined: Sat 08 Nov 2008, 21:01
- Location: 45°17'28.8"N 72°16'08.8"W_avatar/ mira.ca
I do use grub4dos always, legacy menu.lst and ataflash for ssd .
.and i usually to keep a ntfs first partition MS OS install or not
As you probably done ,check spelling...
Or your drive could be going bad tool.
My worst ssd experience was a chinese kingspec...bad..
and china can fake any brand these days...
.and i usually to keep a ntfs first partition MS OS install or not
As you probably done ,check spelling...
Or your drive could be going bad tool.
My worst ssd experience was a chinese kingspec...bad..
and china can fake any brand these days...
The name you are giving to the directory Xenialpup is in (xenssd), could be a problem.
A normal install of Xenialpup 7 is in a directory/folder named:
For yours it would be:
xenialpup7085
The boot process is coded to look for that name.
Also, you are using a development version of Xenialpup, that did have bugs and needed fixing.
The final finished release version is Xenialpup 7.5
A normal install of Xenialpup 7 is in a directory/folder named:
For yours it would be:
xenialpup7085
The boot process is coded to look for that name.
Also, you are using a development version of Xenialpup, that did have bugs and needed fixing.
The final finished release version is Xenialpup 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)
Some SSD's are notorious for having problems with booting.
My experience, similar to those who have posted on internet, was with a Samsung. Which would not set the proper size characters so I could read and set the BIOS. In my experience, one way to check if the SSD is not the issue, for a desktop, is to add an older, slower spinning hard drive to the system. which should slow down the polling. Secondly is to speak with the SSD manufacturer.
After trying out many actions and combination I found a stable working solution: renaming puppy_xenialpup7.0.8.5.sfs to anything (p.sfs) + adding this boot option pupsfs=sda1:/xenialpup7085/p.sfs
title Puppy xenialpup7.0.8.5 (sda1/xenialpup7085)
uuid 54b5806d-ecba-40c7-a6bc-481be3cc8de4
kernel /xenialpup7085/vmlinuz pmedia=ataflash psubdir=xenialpup7085 pupsfs=sda1:/xenialpup7085/p.sfs pfix=ram
initrd /xenialpup7085/initrd.gz
Grub4dos is great in its simplicity, but it seems to be a bit capricious when handling remastered puppies.
title Puppy xenialpup7.0.8.5 (sda1/xenialpup7085)
uuid 54b5806d-ecba-40c7-a6bc-481be3cc8de4
kernel /xenialpup7085/vmlinuz pmedia=ataflash psubdir=xenialpup7085 pupsfs=sda1:/xenialpup7085/p.sfs pfix=ram
initrd /xenialpup7085/initrd.gz
Grub4dos is great in its simplicity, but it seems to be a bit capricious when handling remastered puppies.
- Revolverve
- Posts: 255
- Joined: Sat 08 Nov 2008, 21:01
- Location: 45°17'28.8"N 72°16'08.8"W_avatar/ mira.ca