You are not logged in.
BLwillbegreat, if I could suggest using dcfldd instead of dd, uses identical syntax but some extra options that may allow you to see what's getting screwed up in the imaging process to the usb. in particular is has an errlog flag that lists any errors encounter during the process. Plus by default it gives you an actual read out of the percentage in bytes that have been copied as it runs
Heres the man page:
https://linux.die.net/man/1/dcfldd
Last edited by Horizon_Brave (2017-03-27 16:39:29)
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
This explains how to boot the Debian installer from a hard drive rather than a USB stick ISO image:
https://www.debian.org/releases/stable/ … oot-initrd
Basically, the installer is booted from a custom initrd image and this is what must be loaded from the GRUB menu entry
EDIT: for persistence, create a new partition then format and label it appropriately:
mkfs.ext3 -L persistence /dev/sdXY
Then add the text file to flag the partition:
sudo mount /dev/sdXY /mnt
sudo tee /mnt/persistence.conf <<< "/ union"
sudo umount -R /mnt
The partition should then be used if the (Debian) systems are booted with the "persistence" kernel command line parameter
Last edited by Head_on_a_Stick (2017-03-27 16:49:25)
Offline
Hmm..So is the persistence partition that you're using to store the files "permanately", is this to be used by all iso's on the hdd? Basically do you only need 1 persistence partition that's used for all your iso's or do you need 1 persistence partition per iso for each one?
"I have not failed, I have found 10,000 ways that will not work" -Edison
Offline
As usual thanks a lot to Hoas for the helpful info too. Will definitely check it out.
Planning on breaking this dorkishness down into parts and taking on one part at a time. Though atm am burnt out on it for a bit.
It's cool being able to test drive iso's from hdd. At least made it that far. Finding the correct menuentry can for sure be (is) a real f'ing pita!
Vll!
Addition to fun Android weirdness, there are no shortage of server apps someone can install on a android device. So yeah am 100% sure net-boot'ing a pc off the phone or pxe install can fairly easily be done.
Last edited by BLizgreat! (2017-03-28 17:46:46)
Offline
OK I seem to have a problem with booting the latest Deuterium ISO from my home partition as I get "can not mount .." errors spamming the console. the 2 periods are the .. directory.
My 40_Custom:
$ cat 40_custom
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'BunsenLabs Deuterium ISO' {
set isofile='(hd0,6)/myname/ISOs/bl-Deuterium-amd64_20170429.iso'
loopback loop $isofile
linux (loop)/live/vmlinuz boot=live config fromiso=(hd0,6)/myname/ISOs/$isofile
initrd (loop)/live/initrd.img
}
Anything needing to be changed to allow booting from ISO mounted as a loopback via Grub2?
Real Men Use Linux
Offline
@DeepDayze: Try:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'BunsenLabs Deuterium ISO' {
set isofile='/myname/ISOs/bl-Deuterium-amd64_20170429.iso'
loopback loop $isofile
linux (loop)/live/vmlinuz boot=live config fromiso=/dev/sda6/$isofile
initrd (loop)/live/initrd.img
}
Reference: https://wiki.archlinux.org/index.php/Mu … ive#Debian
EDIT: pagination...
Last edited by Head_on_a_Stick (2017-05-28 19:39:36)
Offline
Thanks HoaS I will try using the explicit device name as it could be sometimes (hd0,6) may not be parsing correctly from within the kernel command line from a Grub command.
Real Men Use Linux
Offline
^ Looking again, I copied that stanza from the ArchWiki but I think that perhaps /dev/sda6 shouldn't have a slash before $isofile because that would expand to a double slash in the full path.
I may be wrong though.
Offline
OK got it working. My 40_custom looks like this:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry 'BunsenLabs Deuterium ISO' {
set isofile='/myname/ISOs/bl-Deuterium-amd64_20170429.iso'
loopback loop (hd0,6)$isofile
linux (loop)/live/vmlinuz boot=live config fromiso=/dev/sda6$isofile
initrd (loop)/live/initrd.img
}
Yes thanks @HoaS, I saw that the slash before the directory name was unnecessary as indeed it expanded to a double slash once the $isofile variable got parsed. Also no space between the device name and the $isofile variable.
Hope this all helps anyone who wants to boot the BL ISO from a hard drive. Just need to remember to change the (hd0,6) to your actual partition where you have the ISO on and to replace myname with your user, if you put the ISO in a folder in your home folder.
Last edited by DeepDayze (2017-05-29 01:30:51)
Real Men Use Linux
Offline
^ Thanks for the update DeepDayze, I have edited the ArchWiki piece to reflect your findings here so that the wider community will benefit.
Offline
Thanks Hoas for taking up the slack, totally spaced this off and long moved on to dorking with something else. To tell the truth though, what I'd been doing and had worked as reported in this thread suddenly oneday ceased working for me.
Despite mucho effort to ascertain why and what went wrong, tried this and that, permissions etc etc and nope BL Hydrogen iso simply wouldn't boot for me from partition anymore.
So even I had been paying attention to this doubt I'dve been of much help fellows.
Offline