ShALLaX.com Forums

I am following your guide and when I try:

cp -av /mnt/loopback/* /mnt/hda2

I get an error about option v not supported. When I try again with:

cp -a /mnt/loopback/* /mnt/hda2

It runs for awhile and blows up with:

Journal-601. buffer write failed.
kernal bug at prints.c:341!
invalid operand:0000

followed by a bunch of hex code.

There's a couple people getting the same errors with the latest releases over FTP installs. The only solution I've found is to slowly copy the file system over bit by bit and if it fails, restart, remove what was being copied and try again =/ Took me a long time to get Home copied over (Pro went much faster).

is this the right commands to copy the folders?

mkdir /mnt/hda2/bin && cp -a /mnt/loopback/bin/* /mnt/hda2/bin
mkdir /mnt/hda2/boot && cp -a /mnt/loopback/boot/* /mnt/hda2/boot
mkdir /mnt/hda2/dev && cp -a /mnt/loopback/dev/* /mnt/hda2/dev
mkdir /mnt/hda2/etc && cp -a /mnt/loopback/etc/* /mnt/hda2/etc
mkdir /mnt/hda2/home && cp -a /mnt/loopback/home/* /mnt/hda2/home
mkdir /mnt/hda2/lib && cp -a /mnt/loopback/lib/* /mnt/hda2/lib
mkdir /mnt/hda2/lost+found && cp -a /mnt/loopback/lost+found/* /mnt/hda2/lost+found
mkdir /mnt/hda2/mnt && cp -a /mnt/loopback/mnt/* /mnt/hda2/mnt
mkdir /mnt/hda2/opt && cp -a /mnt/loopback/opt/* /mnt/hda2/opt
mkdir /mnt/hda2/proc && cp -a /mnt/loopback/proc/* /mnt/hda2/proc
mkdir /mnt/hda2/root && cp -a /mnt/loopback/root/* /mnt/hda2/root
mkdir /mnt/hda2/sbin && cp -a /mnt/loopback/sbin/* /mnt/hda2/sbin
mkdir /mnt/hda2/sys && cp -a /mnt/loopback/sys/* /mnt/hda2/sys
mkdir /mnt/hda2/tmp && cp -a /mnt/loopback/tmp/* /mnt/hda2/tmp
mkdir /mnt/hda2/usr && cp -a /mnt/loopback/usr/* /mnt/hda2/usr
mkdir /mnt/hda2/var && cp -a /mnt/loopback/var/* /mnt/hda2/var

Yep, but you'll find that at least some of those will repeatedly fail. Especially /usr since it's huge. You'll likely have to do the same thing from the /usr reference. ie. Go inside /usr/share and copy each individually and then in /usr/lib and do the same, etc.

i would get a similar kernel.c message after running magic that updated my kernel to linux-2.4.34.2-Gentoox, after manually going back to linux-2.4.32-Gentoox I havent seen the problem since. Donno if its related but something to check.

Hmm. I haven't seen any issues of the like since I got both my Home and Pro boxes up and running. The only time I've seen it is copying from the fatx mounted rootfs file.

Are you running fatx on a partition that was being used at all when you saw the message orochi? Wonder if it's just a fatx thing...

I would be curious to know if you are all using ext3 as Reiserfs support had to be dropped because apparently its so flaky? I did a native install on bios 6.7 with pro 4.2 on a ext3 200Gb Disk what are you lot using?

Yup, ext3.

cheesyboofs, I am following your guide for the native install, but my hdd is 80GB.

//forums.shallax.com/viewtopic.php?t=3092

Here is my fdisk info:

Device Boot Start End Blocks Id System
/dev/hda1 1 993 500440+ 82 Linux swap
/dev/hda2 * 994 155009 77624064 83 Linux

He's asking if you formatted it resierfs or ext3. After you ran fdisk, did you use "mke2fs -j" or "mkresierfs"? Assuming you followed the latest tutorial, it's likely ext3, but he only changed that from reiserfs in the last couple weeks.

I formatted with "mke2fs -j"

I found where is blows up:

mkdir /mnt/hda2/usr/man && cp -a /mnt/loopback/usr/man/* /mnt/hda2/usr/man

mkdir /mnt/hda2/usr/share && cp -a /mnt/loopback/usr/share/* /mnt/hda2/usr/share

That will blow it up every time...

share dir is rather large. I had to copy it piece by piece.

I like GenooX, and really wanted to use it, but with it not being able to get it installed for several days, I decided to switch to Xebian. With Xebian, I was able to get my xbox configured with LAMP within a few hours. I am still using the GentooX RescooX cd as my boot loader

*sigh* That's the problem with people these days. They have no perseverance =)