Package Details: systemrescuecd 5.0.3-1

Git Clone URL: https://aur.archlinux.org/systemrescuecd.git (read-only)
Package Base: systemrescuecd
Description: Installs a rescue system into the boot partition to allow grub to boot it.
Upstream URL: http://www.sysresccd.org
Licenses: GPL
Submitter: PyroDevil
Maintainer: PyroDevil
Last Packager: PyroDevil
Votes: 15
Popularity: 0.227869
First Submitted: 2012-11-01 19:01
Last Updated: 2017-08-08 10:31

Latest Comments

PyroDevil commented on 2017-08-08 10:33

> docache option is useful when dealing with HDD issues: Using ddrescue, testdisk, etc... and writing the output to a NAS, cloud service or USB HDD...

Only under the assumption that your /boot partition is not on this HDD or can still be read from. I would rather deal with these issues by using a RAID.

timofonic commented on 2017-08-08 01:48

Outdated....

Please change to

http://downloads.sourceforge.net/project/systemrescuecd/sysresccd-x86/5.0.3/systemrescuecd-x86-5.0.3.iso

docache option is useful when dealing with HDD issues: Using ddrescue, testdisk, etc... and writing the output to a NAS, cloud service or USB HDD...

PyroDevil commented on 2017-06-04 06:15

With "memory boot" the "docache" option is activated in the cmdline. With this option the init process copies the sysrcd.dat file into the memory before mounting it as the root file system. So it takes a bit longer to start, but using it is faster, because no program needs to be loaded from disk, but thats more of an issue when booting from an optical disk drive. The main reason why I have this option here is because it allows you to overwrite everything on the harddrive, because your system is in the RAM.

And no, no option here allows you to make persistent changes to the SystemRescueCD. But if you like to do this, you might want to look into the available boot options[0]. The "backstore=xxx" seems to provide what you want. If you find settings that are useful for everyone and can be integrated into this package, message me and I will do so.

Cheers,
Pyro

[0] http://www.system-rescue-cd.org/manual/Booting_SystemRescueCd/

nanners commented on 2017-06-04 05:20

Out of curiosity, what's the difference between normal boot and (Memory) boot? Also, is it possible to permanently alter or make persistent changes to SystemRescueCD using either boot method?

PyroDevil commented on 2016-12-28 02:21

I added more boot targets, but some aren't currently working (4.9.0-1) any improvement ideas are welcome.
(I currently don't have much time to do experimentations with it. Maybe at a later date.)

PyroDevil commented on 2014-09-25 23:47

Also you can load the alternative kernel. Its the 3.14 version.

PyroDevil commented on 2014-09-25 23:46

Oh and you can't disable automount completly, because the kernel has to load the 'sysrcd.dat' file. So in your case the root partition has to be mounted.

PyroDevil commented on 2014-09-25 23:44

You can configure the boot process in the '/etc/default/systemrescuecd' file.
You can and add 'nomdadm' to the boot parameters to disable the software raid.

I now added a variable for the boot base directory, so you have to specify "/boot" if you don't have a extra boot partition.

Voice commented on 2014-09-25 23:38

OK, that did it. Thank you. Here is what worked.
http://pastebin.archlinux.fr/602175

Tip? Add a kernel/boot cheat code (if available) to disable RAID autodetection and general disk automounting. System rescue CD is to repair/admin disks, not use them immediately. The detection and mounting attempts take a long time too.

The current SysRescCD kernel 3.10.X is pretty stale but I guess you're stuck with upstream releases.

PyroDevil commented on 2014-09-24 06:55

He couldn't find 'sysrescue/sysrcd.dat' because the subdir kernel parameter is still wrong.
Try replacing 'subdir=sysrescue' with 'subdir=boot/sysrescue'.
If this works I can implement a configuration option for this case.

All comments