CentOS 5 Server :: Can't Mount Ext4 Filesystem In Centos 5.6?
Sep 7, 2011
Summary of issue: EXT4 filesystem won't mount--with error = mount: unknown filesystem type 'ext4'. Is no ext4 in kernel the issue? Or is something corrupted?Really perplexed by this. I updated Centos 5.5 to 5.6 to get ext4 (5.6 is supposed to have full support of ext4). I built several arrays and put the ext4 filesystem on them. All went well until I tried to mount them. BTW, this array (below) is set up as a RAID6 using partition 1 of #8 2TB drives.Bear with me here; just trying to be complete and not waste your time.
Attempting to mount give this:[root]# mount -v /dev/md1 /asc/array1mount: unknown filesystem type 'ext4'Note: it does "fake" mount with ption (which apparently does everything except the system call):[root]# mount -f -v /dev/md1/dev/md1 on /asc/array1 type ext4 (rw,grpquota,usrquote)e2fsprogs:Package e2fsprogs-1.39-23.el5_5.1.x86_64 already installed and latest version (for Centos 5.6; CentOS 6x uses the 1.41...)
I have successful tar an existing CentOS 5.2 partition from Fefora10. The idea is to move a working CentOS 5.2 reside in an internal hard drive to a portable hard drive. I know how to edit a stencil in menu.lst to boot the clone CentOS5.2. During boot, I encountered
Red Hat nash version 5.1.19.6 mount: could not find filesystem /dev/root setuproot: moving /dev failed No such file or directory setuproot: mounting /proc: No such file or directory setuproot: mounting /sys: No such file or directory
I had a LiveUSB of CentOS 5.5, so I decided the install it.With no installer,I just copied the files to my hard drive.his was in a multi boot with Windows 7, Ubuntu 9.10, and FreeDOS.I updated GRUB2 and it detected CentOS. I loaded my entry and it failed to mount the root filesystem.I took the initrd0 file from the LiveUSB syslinux folder and added that ramdisk to the entry. Now it finds the root filesystem (/dev/sda9 as Ext3).But it fails shortly after loading /sbin/init. It talks about an init error where it says "File not found!!!".The previous lines involved umounting old filesystems, like /dev.
i am trying to compile kernel 2.6.23 on Fedora 12 After fixing a few bugs (getline error, %dil ,etc) i was able to compile the kernel made initramfs img using dracut updated grub and then booted up the new kernel 2.6.23 but it fails to boot with following error mount: unknown filesystem type 'ext4'
I have installed 2 extra 1.5TB drives on a stable Centos 5.5 system. They are set up with 2 unequal partitions on each - with 2 raid 1 arrays. The largest of the raid arrays is used as a new volgeoup with 2 unequal LVMs. The larger of the LVMs is around 1.3TB. I installed an ext4 filesystem (default parameters) on the larger LVM.I went to mount the LVM - the system hung. No keyboard or network response and no response to the soft shutdown button.It was the deadest I have ever seen it - and this system has been incredibly stable.
In the absence of any other suspects - I am tempted to blame ext4 - since I have never used it before - and since wikapeadia tells me ext4 isn't supposed to be in the 2.6.8 kernels...:
[URL]
I will do some more testing on this tomorrow to try to confirm my suspicions. I will try to repeat the crash - then try mounting it as ext3 to see if it behaves differently. Any other tests I should do?What is the status of ext4 in RHEL5.5. Has it been added to the 2.6.18 kernel by RH? Is this what is meant by a "back port"?
It is any possibility to install centos 5.5 on ext4 by anaconda ? Is ext4 filesystem is secure for files server (samba) ?? In anaconda installer there is only ext2, ext3 choice.
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 am running CentOS 5.5 with a 14T ext4 volume. We are sharing out a few sub-directories via NFS. Our customer was doing some penetration testing with our web app that writes to one of those NFS shares. We are not sure if they did something to cause the metadata to grow so large or if it is corrupt. Here is the listing:drwxrwxr-x 1 owner owner 470M Jun 24 18:15 temp.badI guess the metadata could actually be that large, however we have been unable to perform any operations on that directory to determine if the directory is just loaded with files or corrupted. We have not run an fsck on the volume because we would need to schedule downtime for out customers to do so. Has anyone come across this before
I have two CentOS 5.4. One is real/host and the other one in VMware-Server.
IP of host is 192.168.200.0/24 and IP of guest is 192.168.210.0/24
I can use ftp,samba,http .. between them but can't mount nfs in the guest and vice-versa since, they are in different network. showmount -e , shows the nfs shared list
I had a centos Linux 64bit installed on my server. Unfortunately I don't know how but my OS crashed and now I have no way to get back my DATA except for rescue disk. I have a Linux 64bit loaded in my server with rescue but I have tried many ways to mount my hdd in Linux and was not succeed.
I dont know if this is possible or not but here what I would like to do. I have 6 linux server and each has 100GB disk space. All of these 6 box are compute nodes and space are not used really. However, If I can combine 6 servershard disk that will in total 6*100GB gives you quite a bigger space. Is there any tool or ways to mount these drive in one volume instead of mounting individually ?
We are running our website on a VPS Centos 5.6 box, and I am trying to set it up as an NFS client to a remote NAS server box. The script (remote_mount) I'm using (copied inline below) works fine when I run it on another Linux server box running Slackware, but when I run the same script on the Centos box I get the following error message. code...
I'm having a consistent problem with instances on Amazon EC2, which a lot of searching including here has resulted in no solution.During boot I see the following message on the console (or "System Log" in the Amazon console):Code:Mounting local filesystems: mount: /dev/sdg already mounted or /apps busy(I'll append a extract from the full log below).Once I log into the instance, I can access the filesystem so it's mounted somehow but I can't figure out what's going on:
Code: # df -k /apps Filesystem 1K-blocks Used Available Use% Mounted on
I'm having a problem accessing files via nfs where an iso has been mounted through the loop device on the nfs server. Basically what I am attempting to do is access the 6 CentOS 5.2 ISO's via NFS from one of my client machines. The client is able to mount the share and see its sub directories leading up to the mount point of the ISO, but the contents of the mounted ISO image are simply not visible (on the client, they are visible on the server).
We have a Centos 5.6 server mounting two iSCSI volumes from an HP P2000 storage array. Multipathd is also running, and this has been working well for the few months we have been using it. The two volumes presented to the server were created in LVM, and worked without problem.We had a requirement to reboot the server, and now the iSCSI volumes will no longer mount. From what I can tell, the iSCSI connection is working ok, as I can see the correct sessions, and if I run 'fdisk -l' I can see the iSCSI block devices, but the O/S isn't seeing the filesystems. Any LVM command does not show the volumes at all, and 'vgchange -a y' only lists the local boot volume, not the iSCSI volumes. My concern is that, the output of 'fdisk -l' says 'Disk /dev/xxx doesn't contain a valid partition table' for all the iSCSI devices. Research shows that performing the vgchange -a y command should automatically mount any VG's that aren't showing, but it doesn't work.
There's a lot of data on these iSCSI volumes, and I'm no LVM expert. I've read that some have had problems where LVM starts before iSCSI and things get a bit messed up, but I don't know if this is the case here (I can't tell), but if there's a way of switching this round that might help, I'm prepared to give it a go.There was absolutely no indication there were any problems with these volumes, so corruption is highly unlikely.
The mount appears to complete cleanly, however when I browse the directory /winfiles it is always empty.The smbclient command works properly using the same credentials.The /root/credentials file looks something like this
I installed NFS and portmap for export a folder to another PC. /usr/local. ftp is server's hostname and ws01 is client's hostname. I edited file /etc/exports with next text: /usr/local ws01(rw,root_squash) *(ro)
I restarted service portmap and nfs. From client, I try check connection with server with command: showmount -e ftp and result is: mount clntudp_create: RPC: Port mapper failure - RPC: Unable to receive
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 am trying to set up an atom D525 low power PC 64-bit with a 40 GB solid state disk drive. Is it possible to specify ext4 during the install for proper SSD suupport? I read somewhere that after install I can place a -discard line in fstab to enable trim.
Edit: should I have asked this in the x86_64 forum, as I was planning on installing 64 bit?
I am noticing RHEL 5.4 is in beta. Does anyone know what 5.4's plans are for ext4? Is it still going to be a non-bootable addon? Or, will GRUB now boot off it?
With the release of CentOS 5.5 ext4 is considered stable in this distribution so I decided to migrate to it. Luckily I started from migrating fresh server with CentOS 5.5 using some instruction I found on the internet. I think I shouldn�t say, that I screwed the whole thing up ;) After about 6 hours cursing, kicking, and crying I solved the task and figured the correct sequence of actions. The small problem with migrating root partition is that you can�t unmount it BTW.
During migration task, I found, that CentOS 5.5 rescue mode is somewhat broken a little in terms of ext4 support. It can mount ext4 partitions successfully. But its e2fsprogs package (tune2fs, e2fsck etc.) doesnt see ext4 partitions and say, that superblock is corrupted on a partition once is converted to ext4 (at least it did it for me. May be I should force filesystem type with -t ext4 switch?). Keep in mind, that if you screw your system up too badly, you will not be able to run tune2fs and e2fsck on it from rescue modeBut you will still able to mount it if it is not corrupted badly. In all below examples,Boot your system normally and login as root. Upgrade kernel if you wish (I usually use yum upgrade to upgrade all on new machines). Then upgrade/install some other packages
Which file system uses Centos 5.6 by default, Ext3 or Ext4? I have installed on Ext3, it's upgrade from 5.5, but howto convert into Ext4 without damage or lost data?
I have a problem with compiling of mod_ruby-1.3.0 After a succesfull configure i get a error in the make, it say "make: *** [apachelib.o] error 1" . Here below you can find the results of de configuring and the make.I was following the roles in Howtoforge " The perfect server - Centos 5.3" everything goes perfect till mod_ruby-1.3.0
./configure.rb --with-apr-includes=/usr/include/apr-1 checking for a BSD compatible install... /usr/bin/install -c checking whether we are using gcc... yes
