Slackware :: Compiling Kernel - Ext4 Is Read As Ext3?
Jan 25, 2010
I compiled a kernel using a previous kernel config after I switched to the ext4 file system. Previously it was using ext3 and the kernel compiled and ran fine. I added support for ext4 to the config but when I went to boot I had a kernel panic. The error was "kernel can't mount vfs on (8,5)". Root is on sda5, I don't know what the 8 is. I started over, using mrproper and made a new config, but got the same error. I created an initrd with the ext4 file system but then the kernel said it couldn't mount root on ext3 because of unique options. (something along those lines) I booted back into the default kernel and saw that it had a similar error right after the bios check, but it loaded fine. I'm wondering why the kernel is saying that the ext4 file system is ext3.
I had 5.4 machine. Upgraded to 5.5 today via yum upgrade. All went fine. Rebooted. Wanted to convert root partition to ext4 (I have three partitions: /boot, / and swap). All of them on software RAID 1 (root is /dev/md2). I did the following for converting
yum install e4fsprogs tune2fs -O extents,uninit_bg,dir_index /dev/md2 nano /etc/fstab # I indicated here that my /dev/md2 is of ext4
I haven't used slackware for many years. There used to be a sticky thread with a great kernel compiling guide for slackware. It feels somewhat unnatural to me to use slackware without a shiny new kernel. Does that guide still exist? I'm working from memory right now.
I want to compile a kernel to add a few options that are not enabled in the huge-smp-22.214.171.124 that comes with slackware. specifically, i want to add TASK_DELAY_ACCT and TASK_IO_ACCOUNTING so that I can use iotop. I just want to add those 2 options to the new kernel, everything else I'd like to keep the way it is as the system has been running just fine. Will running 'make menuconfig' in /usr/src/linux default to the options that are used in the stock kernel?
I am currently having an issue installing the FGLRX driver in slackware 13.1. I use a customer kernel due to buggy acpi on my toshiba laptop. The steps i took to compile my kernel are as followed. hu
make mrproper in /usr/src/linux directory patch /usr/src/linux directory copy kernel config from /boot directory make menguconfig and load config the make all make modules install i have also tried make install as well then i mopy system.map the kernel file and config file into /boot directory edit lilo reboot ... everything works fine acpi works properly like before.. now the problem comes.. I try to install the fglrx drivers and i get the error message Code: Error: kernel includes at /lib/modules/126.96.36.199-smp/build/include do not match current kernel. they are versioned as "" instead of "188.8.131.52-smp". you might need to adjust your symlinks: - /usr/include - /usr/src/linux ERROR: I don't have make module Am I doing something wrong setting up my kernel. Issue on my gentoo box I have.
Anyone able to compile kernel 184.108.40.206 on Slackware 13.37 successfully using the config from testing/220.127.116.11? I was able to get .4 and .5 to compile successfully, but with .6 I get the following after running "make modules".
Code: WARNING: modpost: Found 11 section mismatch(es). To see full details build your kernel with: 'make CONFIG_DEBUG_SECTION_MISMATCH=y' Running "make CONFIG_DEBUG_SECTION_MISMATCH=y 2>&1 > outfile" gives me a bunch of WARNINGS as follows:
Code: WARNING: vmlinux.o(.text+0xe656a): Section mismatch in reference from the function build_all_zonelists() to the function .meminit.text:setup_zone_pageset.clone.56() The function build_all_zonelists() references the function __meminit setup_zone_pageset.clone.56(). This is often because build_all_zonelists lacks a __meminit annotation or the annotation of setup_zone_pageset.clone.56 is wrong.....
WARNING: drivers/watchdog/nv_tco.o(.devinit.text+0x14): Section mismatch in reference from the function nv_tco_init() to the function .init.text:nv_tco_getdevice() The function __devinit nv_tco_init() references a function __init nv_tco_getdevice(). If nv_tco_getdevice is only used by nv_tco_init then annotate nv_tco_getdevice with a matching annotation.
I just rebuild the kernel for slackware 13, everything works, but root file system which is ext3 is mounted as ext2. Normally I've build ext3, ext4 and so on as modules, not in the kernel... but if I do this, then the kernel mounts the file system as ext2, which is build in the kernel. I also modified rc.modules so I can make sure that ext3,ext4,jbd are loaded, but it doesnt work.
Is there guide for converting ext3 to ext4 on Fedora? I use Fedora 12 which is regularly updated. How safe is procedure for data, I have only one ext3 partition on disk which has one ntfs and that ext3 partition (and also one small swap partition).
I'm using CentOs 5.4 (2.6.18-164.15.1.el5 #1 SMP Wed Mar 17 11:30:06 EDT 2010 x86_64). I tested out ext4 on a partition for the last few months and it seems to work fine. The issue is that quotas dont seem to work correctly on it. Is there a way to revert back to ext3? Mainly the quota tools do not work on it.
I tried to compile a 2.6.33 kernel following Alien's guide.
I pretty much used the default values for every (NEW) option avaiable. I used "make localmodconfig" on my current config (zcat /proc/config.gz) and then tried to use "make menuconfig" to check if I could change anything. I didn't understand most of the options, so I skipped it. Then I used "make bzImage modules" and "make modules_install", copied the files mentioned on the wiki and run lilo.
But when I try to boot using my custom kernel, it gives an error like "Cannot remount read-only filesystem as read-write! This can cause serious problems."
If I try to continue the boot, it hangs when trying to launch the syslog script...
The new kernel entry on lilo.conf is:
Code: image = /boot/vmlinuz-custom-2.6.33 root = /dev/sda4 label = newkernel read-only just like the default kernel entry.
By the way, one thing I changed is the kernel compression format, which I set LZMA. But it didn't seem to be the problem, since it at least started...
I run an upgrade and an update on a lucid lynx beta 2. --- got no problems. but about the filesystems i have some questions because it seems for me that at every system boot the system will run an fsck. somtimes it's shown up, somtimes not. but in /var/log/messages and in syslog
I have always following messages ( occured in beta 2 too ).
But first before i continue - here my disk layout:
And here my filesystem types:
This is my problem because those values are seems to be static ! ( note: this partiton is mounted but not in use ) and last not least: the drive is an external usb scsi disk. but on the other side lucid lynx is running fine on my box.
I am going to do network upgrade of my 8.04 to 10.04 LTS. I have a dual boot with Vista, and currently I can read Ubuntu partition from Vista using Ext2fsd. However, I read that using Ext2fsd with ext4 (default in 10.04) is problematic because of "extents".
My questions: Will the upgrade convert my current ext3 partition into an ext4 one? How can I keep the ext3 partition? The release notes for 10.04 say:
The simplest way to select a different file system such as ext3 at installation time is to add the partman/default_filesystem=ext3 boot parameter when starting the installer.
I have a drive with ext3 that was my old /home drive.When I moved to 9.04 I went with ext4 and just linked to my old home drive.My old ext3 drive is becoming unstable so I want to back it up.I have a 500gb ata drive (unfortunately not a sata drive) thatto wipe and put 10.04 on. I want to move my data from this backup driveIm going to back up to, to the new 10.04 until I get another hd as abackup drive.My question is, I know there is some issue between ext3 and 4 and I dontwant to get into a bind. What would be the best format for moving
I have Debian Squeeze with linux-2.6.32-5-amd64Ok, so what I did is first changed fstab ext3 to ext4, rebooted, everything looked good. Then I enabled extents and other ext4 features on my root and home partitions using commands
tune2fs -O extents,uninit_bg,dir_index /dev/sda3 tune2fs -O extents,uninit_bg,dir_index /dev/sda4 then I ran e2fsck -fDC0 /dev/sda3
It has crashed or failed to install on a known good system for the 5th time now. I have never had that problem with fedora before. I am now installing with ext3 instead of ext4. I am hoping for better success with it and will update. I was able to try MinGW with WINE before the first crash and I liked what I saw there. Only hoping to be able to get a good install this time.
I've recently installed Ubuntu 10.10 on a machine, unfortunately, the hard drive was ext3 partitioned. Is there a way of converting this partition to ext4 without having to re-format and hence reinstall the entire OS ?
I have installed ubuntu to my pc. i made 3 partitions. one for system, one for data and one for swap. two of them were ext4. after some time i have reinstalled ubuntu again. but this time i didn't put to format the second partition, but just mount it using ext4. after that i cannot open my files. checked with gparted shows that 2GB used, but with df 188MB. and in properties writes ext3/ext4 filesystem. i used chown, chgrp but didn't help. please help, these data are ver important. i cannot lose them.
How can I format a USB hard drive to ext3/ext4 or whatever file format and have full permission to read, write and execute all files afterwards? When using the command line (as ROOT of course) mkfs.ext3 /dev/sdb? Restricts the rights to ROOT as does the procedure gParted. The man mkfs did not help much. Configuring the fstab- file is a bit of a hassle, so it would be nice, if there was an option to set the permissions "correctly" right from the beginning. Setting Ubuntu (I'm using Ubuntu 9.10) up, so that it mounts USB devices not as ROOT as default but giving all users all permissions seems to be really complicated, as a guy from my local LUG told me.