ReisierFS upgrade?

[Gaccm]

I remember that when i installed reiserfs that i needed to do something each time i try out a new kernel, but i cant remember what it was. I hope its not that i have to format and reinstall reiser, but i cant remember, and cant seem to find the info on the webpage.

[bdg1983]

Maybe that's the reason any of the kernels I try will not boot. 2.4.5, 2.4.6 and I've downloaded 2.4.7 to try out.

All the steps work fine as I've written a script to do all including error checking and exiting. Reboot, select new kernel and it just sits there with a blank screen. Tried Reiser as a module and builtin.

[bdg1983]

One thing I found with a bit of searching, is RAM and INITRD need to be enabled. Going to try now.

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_LOOP is not set
# CONFIG_BLK_DEV_NBD is not set
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_INITRD=y

I rebuilt the ramdisk included with 2.4.2, copied the new modules (including reiser) into it, re-gz'p and renamed to 2.4.6, but that didn't work.

[Gaccm]

i figureed it out, if you set it up as a module, then you need to recreate the module. thats it. I was able to get 2.4.7 to read my fs fine.

[bdg1983]

How did you recreate it as a module? Anything else to download? Thanks...

[ronmon]

I must have configured and compiled 2.4.7 at least 8 times yesterday and kept getting an Oops trying to boot it. At first I thought it was something to do with i2c and lm_sensors patches, so I tried the cvs as well as 2.6.0 to no avail. Then I tried the 2.4.7 patch to my known good 2.4.6 source, still no joy. I tried a virgin source with no patches and even DL'd a fresh .bz2, did everything again, STILL got an Oops! So I slept on it.

After reading this thread, I decided to try saying yes to RAM and INITRD, though I did not do a mkinitrd or add an initrd= to my lilo.conf, since I'm all SCSI and it's built in, not modularized. I really don't think that this did anything for me.

Another thing that I noticed was under General Setup > ACPI support > ACPI Bus Manager > Processor. The config help for this talks about idle handling (important on my SMP system) and the Oops message showed idle task errors also. Turning this on is what I think fixed my problem. The only thing that still won't work is lm_sensors. Both i2c and lm patches are there, but mainboard interfaces do not show up in config. Winbond does, but enabling it doesn't get me temps or fan speeds. DRI compiled and built new modules just fine afterwards. They work great.

I don't know if this will help, but it's what I've gone through and it might. For reference, here's what I'm running.

BP6 w/2x550 cely's
Radeon DDR
Ram = plenty
All SCSI drives on Fireport40 (Symbios driver)

All reiserfs partitions
devfs

Nothing above has been changed from the good running 2.4.6. Again, everything works now (maybe better) except for sensors. Got any ideas there?

[bdg1983]

Thanks for your suggestion Ron.

I just can't get the 2.4.6 or even the 2.4.5 kernel to boot. All the kernel compile are clean (wrote a script for all the steps with error checking), but it just won't boot. Usually just a blank screen and the last time using the defconfig from the original 2.4.2 kernel, I got the boot screen although nothing started as in 'loading kernel'.

I'm using the new Caldera Workstation 3.1 and have upgraded X to 4.1 with no problem, but this damn kernel. Caldera does use the initrd.gz and I've taken the original, renamed, unziped and copied the new modules into it, zipped it backup.

I've compiled the 2.4.6 kernel using the defconfig from 2.4.2, but that doesn't work either.

All I can think of is I selected the whole '/' as ReiserFS during the install (not recommended I've heard), but it works for the default 2.4.2 except for a new kernel.

Tried Reiser as modules and as builtin.

Since I'm just testing out one of my newly built pc's, I might just reinstall with ext2 or create a /boot ext2 and the rest as reiserfs. How does it work now though?

If you have anymore suggestions, I would certainly welcome them. Other than that, I'll just keep on trying.

And yes I've searched at Google. ;)

numerous times...

[ronmon]

I have no ext2 partitions, only reiser and vfat. Reiser is built in same as SCSI because I don't like using initrd's. If you use one, I'm pretty sure you have to build one specifically for the kernel you're going to boot. It's been a while (like 2 years) since I've done it, but it goes something like:

mkinitrd 2.4.7 initrd-2.4.7

That tells it to use /lib/modules/2.4.7 to build the file and name it initrd-2.4.7. If you do this from /boot, it will end up there. Check the options for the command before you do it because I'm really not sure. Anyway, then you add a line in the section of lilo.conf that pertains to that kernel:

initrd=/boot/initrd-2.4.7

Overall, I think you'd be better off building in anything you need at boot time and ditch the initrd. It's an unnecessary complication. Stick with the all reiser, it'll work. Do you want me to email you my .config file?

[sans-hubris]

Why compile as a module? It makes things harder. When it comes to filesystems, I always compile it into the kernel and since 2.4.0, it's a part of the main kernel tree now.

The only time you have to do anything is with an upgrade to ReiserFS because many times, past versions are not compatible with newer versions.

[bdg1983]

The only time you have to do anything is with an upgrade to ReiserFS because many times, past versions are not compatible with newer versions.


I wonder if that would be the case. The installed version of Reiser is from the 2.4.2 kernel and I've tried the 2.4.5 and 2.4.6 so far with no luck.

I've tried Reiser as a module and included in the kernel, still with nothing.

I'm back to work today after a week's vacation and I'll try the 2.4.6 kernel on my pc there that has the same distro but no Reiser just to try and narrow down the problem.

Thanks for all the suggestions.

[ronmon]

Then you're still missing something. There are several new options available in 2.4.7, some of which may be important like the one that was messing me up. Your version of reiser is still compatible. Mine was first installed with a 2.2.19 kernel and works fine. Do the config again and read the help on any new features that you see.

Heh, just checked the lm_sensors home page and found this.

July 22th, 2001 Mkpatch fails for kernel 2.4.7. Sorry. Fixed in CVS

Off to update my cvs and recompile AGAIN.

[ 23 July 2001: Message edited by: ronmon ]

[Dave2001]

Mmm i never had that problems with Reiser . I didnt had to add anything in lilo.conf or anywhere else . The only thing i did was that i built in the Reiser FS support . Did work out every time now . Maybe it is different with SCSI ? Because i dont have it .

David

[ronmon]

Finally got sensors working with 2.4.7. After some more Oops boots gkrellm is dutifully reporting that yes, my box is pretty hot :) I still haven't figured out what the sticking poing was, but it's possibly related to devfs.

I agree Dave, initrd's are a pain. Modules are great for some things, but for boot time necessities they are more trouble than they're worth.

[bdg1983]

Thanks for your suggestions. First time in 5,400 posts that I've actually asked for help.

Had hoped to try on my 2nd pc at work that I've installed OpenLinux 3.1, but I forgot I also installed ReiserFS. Only had time to upgrade to X4.1.

Why do they keep giving me work to do when I have my own stuff to do?

Will try on Tuesday but with 2.4.7 and if that fails, I will reinstall with ext2 just to see if ReiserFS is the cause.

[sans-hubris]

BTW, I'm not sure if you did this already, but did you make sure your fstab file was setup correctly?

[bdg1983]

devpts /dev/pts devpts gid=5,mode=620 0 0
/proc /proc proc defaults 0 0
none /proc/bus/usb usbdevfs defaults 0 0
/dev/cdrom /mnt/cdrom iso9660 ro,user,noauto,exec 0 0
/dev/fd0 /mnt/floppy auto defaults,user,noauto 0 0
/dev/hda5 / reiserfs defaults 1 1
/dev/hda9 /mnt/hda9 vfat rw,defaults 0 0
/dev/hda8 /mnt/hda8 vfat ro,defaults 0 0
/dev/hda7 /mnt/hda7 vfat ro,defaults 0 0
/dev/hda2 /mnt/hda2 vfat ro,defaults 0 0
/dev/hda6 swap swap defaults 0 0

hda5 is the root partition and was setup during the original install using the 2.4.2 kernel and works fine. See anything out of the ordinary? Thanks...

[Screamin' Soulman]

If your root partition is reiserfs you absolutely need reiserfs support compiled into the kernel.

Here's a look at my fstab:


/dev/hdg1 / reiserfs notail 0 0
/dev/hdg6 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/fd0 /floppy auto defaults,user,noauto 0 0
/dev/scd0 /cdrom iso9660 defaults,ro,user,noauto 0 0
/dev/scd1 /cdrw iso9660 defaults,rw,user,noauto 0 0
/dev/hdg7 /var reiserfs rw 0 2
/dev/hdg8 /usr reiserfs rw 0 2
/dev/hdg9 /home reiserfs rw 0 2
/dev/hdg5 /boot ext2 rw 0 2
/dev/hdd1 /var/spool/squid reiserfs defaults 0 2

[ronmon]

Here's what my fstab looks like. I've gotten away without the notail on my / so far. Maybe that's a problem. Well, I don't plan on rebooting any time soon.

/dev/sda1 swap swap defaults 0 0

/dev/sda7 / reiserfs defaults 1 1
/dev/sda8 /usr reiserfs defaults 1 1
/dev/sda5 /home reiserfs defaults 1 1
/dev/sdb1 /store1 reiserfs defaults 1 1

/dev/sda2 /win2k vfat defaults 1 0
/dev/sda6 /common vfat defaults 1 0
/dev/sdc1 /store2 vfat defaults 1 0

/dev/cdroms/cdrom0 /dvd iso9660 ro,noauto,user,exec 0 0
/dev/cdroms/cdrom1 /cdr iso9660 ro,noauto,user,exec 0 0
/dev/floppy/0 /floppy auto rw,noauto,user,exec 0 0

trav:/home /traveller/home nfs rw,user,noauto,timeo=14,intr

none /proc proc defaults 0 0

[bdg1983]

Strange this is, it's running as is with the original 2.4.2 kernel and reiser as a module and works fine. I've also tried including reiser in the kernel, but still the same as it won't boot. Read about the notail and since it's not in my original fstab, didn't think it necessary.

Must be the initrd I am using for 2.4.6. I copied the 2.4.2 initrd, unzipped, mounted, deleted the old modules, copied in all the new modules and gzipped it backup. Followed the exact procedures posted by Caldera.

Like I previously stated, I will try to reinstall as ext2 and see if I'm able to compile and boot a newer kernel.

Thanks again for your suggestions.

[bdg1983]

Just to update my progress. I compiled 2.4.7 on the work pc that already has ReiserFS installed and is actually listed in lsmod.

Compiled as a module, rebooted and this time I got the kernel panic while doing the same at home, I just get a blank screen and nothing else.

I've tried ReiserFS as builtin at home, but that didn't work either. Tomorrow at work I will try to also include Reiser in the kernel so as to rule that out. If all else fails, it's time to reinstall and use ext2 for everything and see if I can get the new kernel to boot.

Actually got the penguin logo that I've heard others talk about with the kernel panic.