Warning: file_exists(): open_basedir restriction in effect. File(/srv/http/vhosts/aur.archlinux.org/public/web/locale//en/LC_MESSAGES/aurweb.mo) is not within the allowed path(s): (/srv/http/vhosts/aur-dev.archlinux.org/:/etc/aurweb/) in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/streams.php on line 90
AUR (en) - systemrescuecd

Notice: Undefined variable: name in /srv/http/vhosts/aur-dev.archlinux.org/public/web/lib/pkgfuncs.inc.php on line 248

Package Details: systemrescuecd 4.9.2-1

Git Clone URL: https://aur-dev.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: 13
Popularity: 1.822657
First Submitted: 2012-11-01 19:01
Last Updated: 2017-01-31 13:50

Latest Comments

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.

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.

Voice commented on 2014-09-24 06:36

You are right, that is the error I saw. The disk has /boot on the same partition as everything else. I made the change you suggested. It worked but with other problems. At some stage the system rescue boot process says

!! Cannot find device with sysrescue/sysrcd.dat. Retrying...

and apparently loops in a retry cycle. I manually rebooted as I had already waited some time to see that much.

Thank you

PyroDevil commented on 2014-09-23 08:00

I can boot the sysrescue without problem.
Do you have /boot on a seperate partition?
If not, that might be the reason.

But grub shouldn't throw '/systemrescuecd/rescue64 not found'. I should instead throw '/sysrescue/rescue64 not found', in case it has problems locating the kernel.

You might try to change all directories in '/etc/grub.d/25_systemrescuecd' from '/sysrescue/' to '/boot/sysrescue/', rerun 'grub-mkconfig -o /boot/grub/grub.cfg' and report your findings.

Voice commented on 2014-09-23 00:19

GRUB emits a file not found error on boot, something like:

File '/systemrescuecd/rescue64' not found
you need to load the kernel first

Actual folder is /boot/sysrescue on disk. That's where the missing file lives.
So it's not the same as the full dir name in the error message.

The /boot/grub/grub.cfg seems to have that right, give or take a parent dir.
Is the full dir name used inside the ISO image?