Mount Error 22 Mounting Ext3 Centos
Contents |
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Thanks for posting this. I wanted to do this once or twice in the past, but never bothered to figure it out. I
Ext3 Fs Unable To Read Superblock Raid
will be trying it soon... I have a Mondo Backup of a server that unable to read superblock ext3 I want to move to less powerful hardware, and hopefully this will do the trick. Dennis -----Original Message----- From: centos-bounces at centos.org
Unable To Read Superblock Ext4
[mailto:centos-bounces at centos.org] On Behalf Of dan1 Sent: Monday, April 09, 2007 11:22 AM To: CentOS mailing list Subject: Re: [CentOS] SOLVED: hard disk move to another server >You can at least try to prepare a new initrd (name it differently and >create a different entry in grub.conf) with mkinitrd. >mkinitrd has a nice feature called --with=module so you can try to >mkinitrd --with=sata_via to include this module even if not 'already' >specified in /etc/modprobe.conf (don't forget also to change this after >the machine has correctly booted : 'alias scsi_hostadapter=') I've >never tested such hdd migration but it should work ... Hello, Fabian. Sorry for the very late answer. You are right, this did the trick. However, there was a thing to add to make it work, we need to mount the /proc filesystem on the destination root directory for the mkinitrd to work properly. Else, thank you very much for the help you provided! The quick fix is to simply copy the /boot/initrd-xx.img file from a working installated drive on the destination server to the old drive partition, and it will work (you must update the grub entry of course). However, if you don't have such a working hard drive, you will need to recompile this initrd file. Therefore I post the complete procedure below to move a hard disk drive with a working CentOS 4 system from one server to another one, not having the same SATA chips, or from a PATA to an SATA or vice/versa. If you don't do this, then you might receive this kind of error: Uncompressing Linux... Ok, booting the kernel. Red Hat nash version 4.2.1.8 starting mount: error 6 mounting ext3 mount: error 2 mounting none switchroot: mount failed: 22 Kernel panic - not syncing: Attempted to kill init! Here is my procedure for those who would need it: 1. To recreate the initrd file, we will do it by booting from a successful boot partition on the destination server, like th
to read superblock General support questions including new installations Post Reply Print view Search Advanced search 8 posts • Page 1 of 1 cen201 Posts: 3 Joined: 2010/09/27 23:27:54 [SOLVED] EXT3-fs: unable to read superblock Quote Postby cen201 » 2010/09/27 23:39:03 Hi,I am unable to boot my server and it is erroring with the message "Kernel panic - not syncing: Attempted to kill init!". Here are the details:I have a brand new Dell PowerEdge T110 server with Quad-Core Xeon CPU and 2GB 1333MHz RAM. I have installed a hard disk (SATA, 7.2rpm) on this machine that I https://lists.centos.org/pipermail/centos/2007-April/036154.html removed from another Dell PowerEdge T100 server with Dual-Core Xeon CPU that was running software RAID 1.Now when I boot the new T110 server, it displays the following error messages:Creating root device.Mounting root filesystem.EXT3-fs: unable to read superblockmount: error mounting /dev/root on /sysroot as ext3: Invalid argumentSetting up other filesystems.Setting up new root fssetuproot: moving /dev failed: No such file or directoryno fstab.sys, mounting internal defaultssetuproot: error http://www.centos.org/forums/viewtopic.php?t=16335 mounting /proc: No such file or directorysetuproot: error mounting /sys: No such file or directorySwitching to new root and running init.unmounting old /devunmounting old /procunmounting old /sysswitchroot: mount failed: No such file or directoryKernel panic - not syncing: Attempted to kill init!I am running CentOs v5.5 x86-64. If I put the hard disk back into T100, it boots fine. I do not know why it is not working with T110 server. Please help!!! Top pschaff Retired Moderator Posts: 18276 Joined: 2006/12/13 20:15:34 Location: Tidewater, Virginia, North America Contact: Contact pschaff Website [SOLVED] EXT3-fs: unable to read superblock Quote Postby pschaff » 2010/09/30 20:20:29 I expect it boots fine when in the array because the other member is being used for booting. Are you sure the RAID is functioning properly and is not degraded? What does Code: Select allcat /proc/mdstatshow on the T100?Another possibility is that the hardware is different enough that the initrd needs to be updated. Can you boot the T110 from installation media in rescue mode and mount the installed system? Top majun Posts: 137 Joined: 2010/03/11 11:33:59 Re: EXT3-fs: unable to read superblock Quote Postby majun » 2010/09/30 21:23:28 Funny... I've just had to d
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about http://serverfault.com/questions/364178/kernel-panic-on-linux-red-hat-server Stack Overflow the company Business Learn more about hiring developers or posting ads with https://communities.vmware.com/thread/418662?start=0&tstart=0 us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Kernel unable to panic on Linux Red Hat server up vote 1 down vote favorite Linux server has been running fine, no updates installed recently, but out of the blue this morning the server stopped responding. I went to check it and it was saying there is a problem with the filesystem, and stated 'you should run fsck manually'. I ran fsck on the relevant partition and fix all the inode problems suggested. After unable to read restarting I am now shown the following messages: JBD: no valid journal superblock found EXT3-fs: error loading journal mount: error 22 mounting ext3 Switching to new root ERROR opening /dev/console!!!!:2 Kernel panic - no syncing: Attempting to kill init Does anyone have any idea how I can resolve this? I am not particularly familiar with Linux so please be verbose when suggestions solutions. I don't want to reinstall Linux if I can avoid it as the server has about 5 years worth of valuable data on there. Any help appreciated! linux linux-kernel redhat share|improve this question edited Feb 27 '12 at 16:53 Kyle Smith 7,6751730 asked Feb 27 '12 at 16:03 HathawayP 612 migrated from stackoverflow.com Feb 27 '12 at 16:23 This question came from our site for professional and enthusiast programmers. 2 Your partition is corrupted. Your hard drive might have failed. –Blender Feb 27 '12 at 16:06 Do you have backups? –Kyle Smith Feb 27 '12 at 16:54 First, copy as much as you can to another disk. If the drive is failing, some data may be unrecoverable soon. –ninjalj Feb 27 '12 at 21:00 add a comment| 4 Answers 4 active oldest votes up vote 2 down vote Boot with a rescue cd
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vCenter™ > VMware Converter Standalone > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 7 Replies Latest reply: Sep 2, 2014 7:18 AM by kellyer RHEL 4 machine converted fine, but get kernel panic when I start the VM hawkeye11 Sep 18, 2012 6:31 PM So I have a bunch of old Red Hat 4 servers that I need to convert to VMs. I am using the standalone converter 5.0 and the VMs range from Red Hat version 2.6.9.-11 to 2.6.9-42. Some of the machines I can P2V with out any issues but a majority of them fail withmount: error 6 mounting ext3mount: error 2 mounting noneswitchroot: mount failed: 22umount /initrd/dev failed: 2 (see pic for more details)So I get a 100% complete when I use the Converter but when I boot up the VM I get that error. I have followed the directions from http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002402 but I still not having any luck. I made changes to /etc/fstab, /boot/grub/grub.conf, /boot/grub/device.map etc... I am also having issues with rebuilding the ramdisk. I ran the command with the existing version on the drive but I get an error about about no modules found. I have also found another article saying the version of TAR might be an issue so i've upgrade the version to 1.14-15 and re-ran converter and it still failing. Anyone have any ideas what is wrong? I am windows admin with some linux background so please go detailed on the linux commands. 8163Views Tags: none (add) This content has been marked as final. Show 7 replies 1. Re: RHEL 4 machine converted fine, but get kernel panic when I start the VM sparrowangelstechnology Sep 18, 2012 8:34 PM (in response to hawkeye11) change the scsi controller type of the vm Like Show 0 Likes (0) Actions 2. Re: RHEL 4 machine converted fine, but get kernel panic when I start the VM