Server :: Mounting Ext3 File System As Ext2 On Slackware With Custom Build Kernel?
May 16, 2010
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.
I have dual boot system..i.e, windows XP and ubuntu 9.10(insatlled side by side). when i try to boot ubuntu, Im gettin sh:grub > prompt
[Code]...
I am getting something like this.. root mount file system failed.. ext2 ext3 ext4 ....... kernel panic message and hanged at kenelthreadhelpper+ what can i do.. I cant reinstall ubuntu again.. Because I have installed nany application there..
I have an image of an ext3 file system done with dd. I know that the file system is corrupted but I want to try to recover some files. Whatever I dd it again to the original partition or assign the dd image to a loop device, that's what happens:
- dumpe2fs -h gives me a valid ext3 superblock.
- as I try to mount the device read only, it fails with a bad magic number error.
- executing dumpe2fs -h again gives bad magic number error.
- trying debugfs or fsck with backup superblocks fails the same way.
For me it seems that in spite of mounting the device as read-only, mount command do something wrong with the superblock as before the mount the superblock is correct and it's there.
How well is the ext4 new file system mounting compatibility with the older ext3 previous Linux installations ? I refer to Ubuntu 9.04 and the new Fedora 11 which have the option to install with the ext4 file format. Will it be better if I install with the older ext3, so that I will be able to mount all other Linux from each other in a multi-boot system ?
I compiled my own custom kernel for the first time. I tinkered with different options, nothing to difficult. I actually didn't expect it to work the first time.
I had kept the original lilo boot config just in case something was to go wrong. Now when I try to boot the system, I always get a "VFS: cannot mount root system on (8,3)". I googled this and found that my kernel did not support my root filesystem (btrfs). So I made an initrd with btrfs kernel module, but it didn't help. I then got a string of errors about how /dev could not be mounted.
My question is two-fold. First, how come when I configure the system back to when it was first installed, it still won't boot? Im using the same kernel (2.6.37.6-smp). Second, how can I get myself out of this rut without reinstalling?
lilo.conf
Code: lba32 append=" vt.default_utf8=0" boot=/dev/sda vga = normal # Linux - Slackware image = /boot/vmlinuz-huge-smp-2.6.37.6-smp root = /dev/sda3 label = Linux read-only
BTW, I have been maintenancing the system by chrooting into the device off of my slackware boot disk. Im on slack 13.37
i m not able to copy a file over 16 gigs on an EXT2 or EXT3 partition. Is there a way to do this. I even tried to split my iso file too. I splitted my iso file in 4 files then copy them on the ext2 or ext3 partition. But as soon as I was trying to join the files together it never went over 16 gigs. Actually it stops at 16,843,020 kb exactly. is there a limit for those partitions or is there an another way to see my 20gigs iso file in one piece?
I compiled a 2 custom kernels so far (many custom kernels just 2 that I have used) however, both of the kernels display an error message about EXT3-Fs and unable to load custom options even though all my partitions are ext4.
I have looked around and the only reason I find for those are that the file systems are corrupt beyond repair,However the problems always ments EXT3-fs is a ext3 file system problem and EXT4-fs is a ext4 file system poblem. Why is mine saying EXT3 and some times EXT2 when im using EXT4?
Custom Kernels
Debian 2.6.26.Something with RT patch Debian 2.6.33 with Rt patch
When I build the kernel 2.6.30 source, the rpm package is very big and needed or root filesystem 800-900 Mb. I use "make rpm" as described in Configure, Build and Install a Custom Linux Kernel - openSUSE.
I am trying to build a custom kernel but I couldn't. Here are the steps to reproduce it: 1. Set Up an RPM Build Environment as its is explained in [URL] 2. Then follow the instructions in [URL] 3. When I try to install the kernel source rpm I get the following error:
[matias@Centos ~]$ rpm -i [URL warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root . . . warning: user mockbuild does not exist - using root warning: group mockbuild does not exist - using root error: unpacking of archive failed on file /home/matias/rpmbuild/SOURCES/linux-2.6.18.tar.bz2;4ba24901: cpio: read
My Redhat Enterprise Linux 4 with 6x partitions (/, /boot,/home, /usr, /var, /tmp) of 6.0 GB IDE Hardisk was working quite fine. I decided to create LVM on /home and /var partitions but due to some errors occured and I delete the /home partitions. That's why partition table altered. I then delete 4,5,and 6th partitions (/home, /var, /tmp) partitions and now try to create one by one but following error is coming:-
[Code]....
The Super block could not be read or do not describe a clear ext2 file system. E2fsck b 8193 <device> I have tried following commands,but could not successful:- e2fsck -p /dev/hda7 (where hda7 was created but afterthat it was deleted) e2fsck -a /dev/hda7
I used make-kpkg to build the 3.0.0 source debian wheezy on a dual 3.4GHz Xeon/L1-16k/L2-1mb/800Mhz bus with 4GB PC2-3200 ECC ram and Ultra 320 SCSI, using CONCURRENCY_LEVEL=4 (2 hyperthreading cpus=4 cores). The build was slower than molasses in January! Top reported cpu usage total between 10% and 25%. Why won't the build use the amount of machine it has available. One footnote: I wasn't using swap space. It literally took over an hour to build the deb kernel package.
My notebook from 2003 is at least three times faster building the 3.0.0 debian kernel source. Is it possible that this might cause improvement: make -j4 KDEB_PKGVERSION=version deb-pkg
Could amd64 vs. i386 have some influence? Could the small processor caches on the XEON cpus have an effect. The 64-bit machine absolutely flies doing everything else. I'm miffed! I've used debian since woody, although I am not an expert, but I'm no slouch!
I'm new to linux and recently installed openSUSE 11.1 on my Lenovo Thinkpad SL500. So far it's great... only problem is the hotkeys and brightness control don't work. Digging around online I found this "experimental" driver that purportedly works fine, but I have no idea how to compile, install, or otherwise use it. Here... tetromino's lenovo-sl-laptop at master - GitHub I'm not sure what to do with the makefile and C file provided. For example, what do I do with this instruction...
"To enable the brightness control, load the module with the "control_backlight=1" module parameter (i.e. insmod lenovo-sl-laptop.ko control_backlight=1 )" I know someone on here will be able to explain how to do this in a "computer engineering for chemists" language! I'm comfortable enough working in the terminal with commands, but have found no real straightforward explanation of how to do so (only "programming" experience is MATLAB m file writing).
I have lost the data of my drive having file system ext3, please tell me the most reliable softwares for data recovery, please try to tell also GUI software.
I have configured a "Syslog" server on /var directory as a separate ext3 partition - to receive the logs and events from the clients & the firewall as well. The directory needs to grow dynamically as the logs are populated. Is there a way i can make the filesystem grow dynamically as and when the directory is full.
scanning them with Avast! and Malwarebytes Anti-Malware or by running registry cleaners like Ccleaner.However, I think it would be cool to have a Live system that I could boot from my flashdrive that I could have programs installed to do all this with.It would be cool if I could use Puppy Linux, since it loads and runs from RAM, which gives a huge speed boost when compared to running a live version of a distro like Ubuntu, but I don't really know my way around Puppy, or how to make my own "pupplet". Also, from what I could tell, Puppy Linux didn't have a package manager like Pacman or Aptitude.Here's a list of programs I would like to have a Linux alternative to use:-Avast! Anti-virus-Ccleaner (registry cleaner)-Malwarebytes Anti-Malware/Superantispyware (malware/spyware cleaner)-Perhaps also a Defrag program like Defraggle
I am kinda stuck while providing solution for the above problem. I have achieved the fail over using keepalived but not sure how can we replicate the data from one server to other seamlessly and have them in sync with each other. My prime requirement for this project is end user should not notice the fail over and replicated copy of data should be available on the secondary as well.
I am planning on dual-booting Windows XP and Ubuntu on a new laptop, and because I have a program that lets me mount an ext2 filesystem on Windows, I was thinking of installing Ubuntu with ext2 instead of ext3. I am concerned, however, that it might open up a security risk for my Ubuntu partition. Would this cause a problem? (In case it's relevant, I use AVG Free antivirus in Windows.)
I use 8GB USB sticks for backup of Ubuntu 10.04. I have had a variety of problems with ext3 format (security tar file not readable, etc) and have reformatted to ext2, so far without a problem.
But - am I missing something by not using ext3 (or even ext4)? Should I be sticking with ext3 and try to resolve the problems - bearing in mind that as the USB stick is my backup I need it to be secure!
I would like to convert my /tmp and /boot partitions from Ext3 to Ext2 on my Arch Linux setup. I don't see any use in having journaling for either partition. I want to make sure that I have the right steps lined up so could someone verify that this is correct (from a live cd):
Code: #sudo tune2fs -O ^has_journal /dev/sda7 #sudo e2fsck /dev/sda7 #sudo tune2fs -O ^has_journal /dev/sda5 #sudo e2fsck /dev/sda5 I then edit /etc/fstab to reflect these changes (ext3 to ext2 for both lines)
Does it matter what order I do it in (/dev/sda7 is /tmp and /dev/sda5 is /boot).
When installing fedora 10 from scratch on an acer aspire one 150L, which filesystem should be used? ext2 or ext3? a basic explanation of the reason would be great too.
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 have a new Vertex2 Solid State Drive. When I try to install any distributions, formating the drive in EXT3 or EXT4 (or LUKS with EXT3, or EXT4). My hard drive times out during a copy process. (OpenSUSE 11.2 for example would crash after the 2nd file of X11. Debian got ~12% done when it crashed.)
We are running debian off of an SD card and want to know what's best for /var?
- Plenty of room on 2GB SD card, so do we, make /var as large as possible (everything else is read only) to reduce block overwrites, or do we make /var as small as possible, hopefully reducing the load 'pdflush' places on the 200 Mhz system?
That said, why not ext2? Is there damage that can happen in /var due to insta-crash or power loss that will prevent proper system function? We heard ext4 is more optimized, but ext4 on 2.6.29, not sure.
If we must use a journaled file system for /var, then which is lowest load on system, or "better": jfs, ext3, jffs2 ...
I have a question, i accidentally formatted an lvm volume as ext2 after creating it. Then of course, we copied a ton of data to it before I realized it was ext2. (I guess ext2 was the default when using mkfs without a -t) Anyway - can I just use tune2fs -j on the LVM just like I would a /dev/sdx device?
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.