Hi all !
I followed directives from http://www.funtoo.org/wiki/Creating_Sys … CD_Modules to create installation media. It doesn't work at all. Wether I boot from CD or USB stick modprobe does not find zfs modules. The only difference is when booting from CD and selecting C (standard). modprob killed zsh and console is unusable. Must switch to another console to reboot.
So... from USB, options C and E give modules not found after depmod and modprobe -v zfs. From CD, standard kills zsh and alter does the same as from USB.
there is pre-built ZFS SRM, available at:
try to use it.
there is pre-built ZFS SRM, available at:
try to use it.
That's where files were downloaded from.
I created USB following Funtoo guide again. I got same error messages when booting into Sysresc and issuing depmod and modprobe. Somehow I investigated further and found zfs command in /sbin.
Standard 64 : you get a message like zsh is killed after modprobe -v zfs is ran;
Alter64 : you get a fatal error along with zfs modules not found;
In either case, zfs command is in /sbin.
When you run lsmod after modprobe, PC is frozen. If you start the GUI (wizard) you're in somtething like 800x600 and there's no way to use highger resolution.
I'll try some other solutions and be back with results.
There is no srm for alter64 so don't try that.
Check to see if you compiled zfs-0.6.0-rc14.. that one as of right now is causing problems for me. Go back to rc13 and try that for now. Let me know what happens.
Bad news again...
Contents of temp :
drwxr-xr-x 2 guy guy 4,0K 4 fév 08:52 iso -rwxr--r-- 1 guy guy 1,5K 12 jan 20:31 make_iso.sh drwxr-xr-x 2 guy guy 4,0K 28 jan 15:27 srm -rwxr--r-- 1 guy guy 1,3K 12 jan 20:33 usb_inst.sh -rwxr--r-- 1 guy guy 294 28 jan 15:28 vars.sh -rw-r--r-- 1 guy guy 2,5M 4 fév 06:15 zfs-3.4.27-std330-amd64.tar.bz2
USB was created using a brand new key. Scripts was run like this :
sudo bash usb_inst.sh
Boot on USB, select STANDARD 64.
If depmod and modprobe are run in GUI, blank screen.
If depmod and modprobe are run in console messages are:
insmod /lib/modules/3.4.27-std330-qmd64/addon/spl/spl/spl.ko.gz zsh: killed modprobe -v zfs
lsmod does not reply. ALT+F2 to reboot.
dual screen not supported as is when you create a Sysrecs media with iso downloaded from SysrescueCd site (sourceforge).
there is newer SRM available, try, please with rc14
http://ftp.osuosl.org/pub/funtoo/distfi … 14.tar.bz2
Please read fearbliss' reply. There's something not working with rc14. Whether I use rc14 or the other one, issues are the same. I really don't kwow how you are successfull, but it doesn't work on my side.
OK angry_vincent :-)
I'll test later.
For now I updated my kernel to support devtmpfs. I installed zfs and added it to boot run-level. I didn't reboot yet. I simply launch rc command. So I can use zfs from my current installation. It means I now can chroot from it instead of SystemRescueCd.
delta ~ # gdisk /dev/sdb GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: not present BSD: not present APM: not present GPT: not present Creating new GPT entries. Command (? for help): x Expert command (? for help): z About to wipe out GPT on /dev/sdb. Proceed? (Y/N): y GPT data structures destroyed! You may now partition the disk using fdisk or other utilities. Blank out MBR? (Y/N): y delta ~ # zpool create -f -o ashift=12 -o cachefile= -O compression=on -m none -R /mnt/funtoo rpool /dev/sdb delta ~ # zpool export rpool delta ~ # gdisk /dev/sdb GPT fdisk (gdisk) version 0.8.5 Partition table scan: MBR: protective BSD: not present APM: not present GPT: present Found valid GPT with protective MBR; using GPT. Command (? for help): p Disk /dev/sdb: 976773168 sectors, 465.8 GiB Logical sector size: 512 bytes Disk identifier (GUID): E666924E-6C15-F147-A040-DD3875A97B63 Partition table holds up to 128 entries First usable sector is 34, last usable sector is 976773134 Partitions will be aligned on 2048-sector boundaries Total free space is 2029 sectors (1014.5 KiB) Number Start (sector) End (sector) Size Code Name 1 2048 976756735 465.8 GiB BF01 zfs 9 976756736 976773119 8.0 MiB BF07 Command (? for help): q delta ~ #
this is newer SRM uploaded today.
Same results... doesn't work.
I think SystemRescueCd iso is the source of problems. Even option to boot from first hard disk doesn't run, menu is refreshed and countdown starts.
The srm should definitely be working for you on 3.3.0. Make sure you are using rescue64. It's working for me and other people, but it's hard for me to fix problems when I don't really have all the tools that System Rescue CD has. Unfortunately System Rescue CD isn't the ideal way for us to install ZFS .
I tried to create an usb stick today with the latest images from http://ftp.osuosl.org/pub/funtoo/distfiles/sysrescuecd/:
systemrescuecd-x86-3.4.2.iso 02-Apr-2013 22:15 386M systemrescuecd-x86-3.5.0.iso 02-Apr-2013 22:15 390M zfs-3.4.37-std350-amd64_0.6.1.tar.xz 02-Apr-2013 22:15 2.4M zfs-3.4.37-std350-amd64_0.6.1.tar.xz.hash.txt 02-Apr-2013 22:15 72
(local sha256 is ok)
The var.sh inside the srm wants systemrescuecd-x86-3.5.0.iso, so I successfully created the stick with that iso.
But after booting "rescue64" from that stick, zfs is not loaded automatically.
I can insmod spl wiithout errors, but the zfs module says "Unknown symbol in module"
The kernel booted from sysresccd is 3.4.37-std350-amd64.
To me it looks like this combination doesn't work and I couldn't find any older versions on the funtoo ftp server. It would be nice if there was at least an older version to match the systemrescuecd-x86-3.4.2.iso.
The 3.4.2 srm was mistakingly removed. We normally keep 2 versions of sysresccd precisely because things like this can happen.
I just retested the 3.5.0 srm by downloading it from our website and remaking the .iso myself and it is working fine.
Here is a screenshot of my VM with some outputs: http://i.imgur.com/6Esh1qq.png
For now you can download the 3.4.2 SRMs here: http://jonathanvasquez.com/files/sysresccd/
EDIT: Do not use insmod. The proper way to do it is to use modprobe zfs. This loads each module that zfs depends on before loading the zfs module. Insmod only loads the module you target and doesn't load it's dependencies. Hense you will get a "Unknown symbol error" (Because the dependency that has that symbol did not load yet).
Once you boot into sysresccd, try the following:
# depmod # modprobe zfs # dmesg | tail
It should say that zfs loaded fine.
Last edited by fearedbliss (2013-04-03 03:55:49)
I had tried modprobe, too.
But I forgot depmod, now it works with 3.5.0