ext3-fs dm-1 error unable to read superblock Ernul North Carolina

21st Century Computers is a locally owned family business started in 1994 by Steve Smith. We pride ourselves on providing excellent service at reasonable prices and with a fast turn around.  We treat our customers with honesty and integrity and we are understanding and companionate to their needs. Regardless of whether you are a business or an individual, we know how important computers are in todays world and we strive to give our customers the very best service possible. We provide all types of computer repairs and we quote prices in advance so you can make an informed decision. We also specialize in virus removal and data recovery and we leave no stone unturned.  Our Remote Help allows us to work on your computer instantly through the Internet. As a certified network specialist, we can expand your Internet coverage throughout your home or business.  When you are ready for a new computer, we can custom build one for you or advise you on what to buy. We also repair phones and IPads and we install security cameras and home entertainment systems.  Call us today and Amanda or Steve will gladly answer your questions. We are here to help.

All computer repairs, virus removal, PC tune-up. We'll speed up your computer and make it faster than it's ever been.

Address 2770 Neuse Blvd, New Bern, NC 28562
Phone (252) 633-5825
Website Link http://www.21stcenturycomputersnc.com

ext3-fs dm-1 error unable to read superblock Ernul, North Carolina

The drive is only about a year old. The filesystem type was confirmed to be ext3 using the file command [email protected]:/home/peter# file -sL /dev/c/c /dev/c/c: Linux rev 1.0 ext3 filesystem data, UUID=3ecd91ba-161a-4d7f-bac7-a3b1a7095be4, volume name "c" (large files) and the I found the culprit a few hours later: openSUSE 10.2. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features.

unmounting old /dev unmounting old /proc unmounting old /sys switchroot: mount failed: No such file or directory Kernel panic - Not syncing: Attempted to kill init! Goleteral View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Goleteral 08-17-2010, 05:22 AM #2 Goleteral LQ Newbie Registered: Aug 2010 Posts: To start viewing messages, select the forum that you want to visit from the selection below. ** If you are logged in, most ads will not be displayed. ** Linuxforums now Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest

Several functions may not work. To confirm it say lvdisplay on the host and see if some snapshots are in INACTIVE state. There were some search results suggesting that newer 3.x Linux kernels have native support of ext3 block sizes above 4k, but I was not able to confirm that (or whether it Forum Operations by The UNIX and Linux Forums

Once CentOS found that information it assembled the devices according to the new superblock enumeration and voila - total chaos ensued.In the end I had to clone the server again and Quick Navigation Home Get Subscription Wiki Downloads Proxmox Customer Portal About Get your subscription! 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 It's not an ideal solution, but it may let you access some data if you're lucky!

the ReadyNAS uses 16KB block sizes, but x86 only supports 4KB blocks (natively). I assume I'd need a special formatting tool as it appears the partition table is gone as well. kjournald starting.Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on dm-1, internal journal EXT3-fs: mounted filesystem with ordered data mode. Not the answer you're looking for?

more hot questions question feed about us tour help blog chat data legal privacy policy work here advertising info mobile contact us feedback Technology Life / Arts Culture / Recreation Science New tech, old clothes What is a type system? kjournald starting.Commit interval 5 seconds EXT3-fs warning: maximal mount count reached, running e2fsck is recommended EXT3 FS on dm-2, internal journal EXT3-fs: mounted filesystem with ordered data mode. Learn More.

As always, caution is advised. –Michael Hampton♦ Mar 28 '13 at 16:28 @GetFree, another way to mount a filesystem without touching its journal is to pass noload to mount, Note that registered members see fewer ads, and ContentLink is completely disabled once you log in. Is is likely to be corrrupt partition tables/other system data or hardware failure? I was able to Restore form a Backup and mount the broken HDD to copy some SQL Databasedumbs.

Kernel panic: no init found. mpost91422 Top cen201 Posts: 3 Joined: 2010/09/27 23:27:54 Re: EXT3-fs: unable to read superblock Quote Postby cen201 » 2010/10/08 22:02:49 I tried all the suggestions that were posted so far. thanks! asked 3 years ago viewed 24707 times active 1 year ago Related 3How to recover deleted files on ext3 fs0LVM+Ext3 - recover the ext3 partition?1How to recover data from re-partitioned hard

Browse other questions tagged mount lvm ext3 or ask your own question. Perform all further operations on the copy Here I assume that you have copied /dev/sdb2 to /dev/sdc2 and that you will recover files to /dev/sdd2. share|improve this answer answered Mar 28 '13 at 7:43 fab4am 493 1 I've just tried that but I get the error EXT2-fs: sdb2: couldn't mount because of unsupported optional features Regards Iain ibuclawApril 27th, 2009, 11:13 PMHi.

They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own. Join Date Sep 2010 Posts 4 [SOLVED] EXT3-fs: unable to read superblock Hi, I am unable to boot my server and it is causing "Kernel panic - not syncing: Attempted to Is there a way I can recover the data in that partition? Not the answer you're looking for?

After that, of course, the previous content won't be recoverable. I did a new installation with Xubuntu 9.04 AMD64 and after the installation I noticed that sda had lost the only partition on that harddrive, sda1. All Rights Reserved. Also, what file system was that partition?

This may take awhile ... Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. share|improve this answer answered Nov 19 '13 at 13:19 steeldriver 31.2k44474 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.

Aug 5 21:15:07 andromeda kernel: ext3_orphan_cleanup: deleting unreferenced inode 104726578 Aug 5 21:15:07 andromeda kernel: ext3_orphan_cleanup: deleting unreferenced inode 104726577 Aug 5 21:15:07 andromeda kernel: EXT3-fs (dm-3): 168 orphan inodes deleted Home Forum Today's Posts | FAQ | Calendar | Community Groups | Forum Actions Mark Forums Read | Quick Links View Site Leaders | Unanswered Posts | Forum Rules Articles Marketplace Why is it a bad idea for management to have constant access to every employee's inbox How do investigators always know the logged flight time of the pilots? There is a suggested workaround in a post by user 'kernst' on the ReadyNAS user forum Using fuse-ext2 to access ReadyNAS-formatted ext3.

LinuxQuestions.org > Forums > Linux Forums > Linux - Server [SOLVED] Server booting issues(EXT3-fs: unable to read superblock 'etc') User Name Remember Me? thanks and regards #1 informant, Aug 5, 2013 Last edited: Aug 5, 2013 ioo New Member Joined: Oct 1, 2011 Messages: 10 Likes Received: 0 Hi! > Aug 5 21:21:16 Please help me :) Looks like the hard drive is either not initialized, or you have deleted the partition off the hard disk. Join our community today!

I do not know why it is not working with T110 server. Stay logged in Proxmox Support Forum Forums > Proxmox Virtual Environment > Proxmox VE: Installation and configuration > Toggle Width Home Contact Us Help Terms and Rules Top About The Proxmox The number of cylinders for this disk is set to 9346 There is nothing wrong with that, but this is larger than 1024 Warning: Invalid flag 0x0000 of partition table 4 current community blog chat Server Fault Meta Server Fault your communities Sign up or log in to customize your list.

Use --list for a list of the available backup and archive files of VolumeGroupName. By continuing to use this site, you are agreeing to our use of cookies.