ext3-fs sdb error unable to read superblock Emerson New Jersey

Address 300 Commons Way, Bridgewater, NJ 08807
Phone (908) 429-9339
Website Link https://stores.bestbuy.com/nj/bridgewater/300-commons-way-544/geeksquad.html?ref=NS&loc=ns100
Hours

ext3-fs sdb error unable to read superblock Emerson, New Jersey

Kernel panic: no init found. As a result, it's unlikely that this tutorial will help. No it's not solved, and it's not restricted to flash drives..........................I have Arch installed on an ide(pata) drive as sdb1 (hd1,0) - runs fine. Reply Link Phillip October 7, 2009, 5:06 pmAwesome.

It is possible that the enclosure is the problem. Have tried all things suggested in comments, still no luck, just get these errorsfreenas:/mnt# mke2fs /dev/ad1 mke2fs 1.41.14 (22-Dec-2010) /dev/ad1: Operation not permitted while setting up superblockordumpe2fs /dev/ad1 dumpe2fs 1.41.14 (22-Dec-2010) Turns out the culprit was the kernel version 2.6.26 that I got with pacman -Syu.So, I just did a pacman -Ud and the problem disappeared.I have i hope it s going to work but anyway your blog is exellent!!so thanks even it won t work!! 71 Thomas Dillinger on October 8, 2011 said: You really help me

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. Every single one gives an error: [I]The superblock could not be read or does not describe a correct ext4 filesystem. That's why I wanted to know what should the correct output be if the operation succeeds… It still sorted the problem somehow, when I restarted the superblock was good again eventhough although i'm using arch, your guide worked perfectly (after all, ext4 is ‘distro-agnostic'🙂.

asked 3 years ago viewed 24707 times active 1 year ago Visit Chat Related 3How to recover deleted files on ext3 fs0LVM+Ext3 - recover the ext3 partition?1How to recover data from I'm glad you were there for me. *thumbs up and slaps on the back to you* 9 evidex on July 12, 2010 said: Brilliant! I might as well shoot myself if I don't get it back. 108 evidex on June 8, 2012 said: Try repeating it with another one of the listed superblocks, such as You should definitely try but I wonder if any tools you ran earlier on will suddenly be able to see or do anything with the drive.

Then, attempt to mount the drive again. On this occasion I am sure that I did that as usual - I double checked - but for some reason the install has overwritten my partition with a default /home yes .......... /dev/sda2: ***** FILE SYSTEM WAS MODIFIED ***** /dev/sda2: 59586/30539776 files (0.6% non-contiguous), 3604682/61059048 blocks Now try to mount file system using mount command: # mount /dev/sda2 /mnt You can I've just run fsck -p and got: [email protected]:~$ sudo fsck -p /dev/sda fsck 1.41.4 (27-Jan-2009) fsck.ext2: Bad magic number in super-block while trying to open /dev/sda /dev/sda: The superblock could not

Thx! I have now bookmarked your site. Reply Link Bryn August 26, 2011, 3:40 pmHi, I still have a problem. but i'm afraid the solution is not this simple: # fsck.ext3 -v /dev/sdh e2fsck 1.38 (30-Jun-2005) fsck.ext3: Attempt to read block from filesystem resulted in short read while trying to open

To that this works, you can boot from your primary HD or rescue with the damaged HD disconnected. I fear that perhaps you've written over the data that was there, though I could be completely wrong. Page 1 of 2 1 2 > Search this Thread 06-28-2010, 12:33 AM #1 ckecbond LQ Newbie Registered: Jun 2010 Posts: 10 Rep: EXT3-fs: unable to read superblock I hear you about the tools - because the proper sector count is there...but the drive is physically removed from the machine at this exact moment and I can't run any

you saved my busted filesystem and the beast lives again! 127 rihend on December 21, 2013 said: Reblogged this on Henri Sekeladi - Sebuah Catatan Perjalanan. 1 mount: wrong fs type, For many more details, say man 8 mount .any clues on this? ckecbond View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by ckecbond 06-29-2010, 09:06 AM #10 ckecbond LQ Newbie Registered: Jun 2010 Posts: Linux ext2/3 filesystem stores superblock at different backup location so it is possible to get back data from corrupted partition.WARNING!

If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck It was really helpfull to me and now I have better overview how ext FS is working. Marking this thread [SOLVED] for posterity. irfan wrote:Poisonblack wrote:Found the solution.!

Thanks a lot, Mike caljohnsmithApril 29th, 2009, 11:22 PMSo you don't have any idea what might have happened that the sda1 partition somehow got deleted? 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 Just like the pic in this link (2nd pic - the order is different and mine instead of RAID component says ‘3TB' ext4): http://community.wdc.com/t5/WD-ShareSpace/HOWTO-Recover-files-from-a-RAID-1-mirrored-drive-when-the/td-p/138448 The problem is that I can't mount Due to a power outage I have been unable to boot from the drive so I've been using a Live DVD.

I have another dedicated box with GoDaddy and I have backups on it and I had planned to do backups of this dedicated box this month...now here I am. You could try to 'dd' the drive image and work from that but if the hdd/enclosure is faulty then 'garbage in = garbage out'. When it rebooted I got all sorts of disc errors; I booted with a live cd and after a bit of searching ran fsck -yfv until it stopped reporting problems. Lesson learned, backup periodically and grandfather.

To try and save some time and since this is a second partition, not the boot partition, I think I should be able to attempt to mount the device. onebuck View Public Profile View LQ Blog View Review Entries View HCL Entries View LQ Wiki Contributions Find More Posts by onebuck View Blog 06-28-2010, 09:29 AM #6 ckecbond LQ That makes me think the device is faulty... The RAID1 is "mirrored" although I set it as not backed up when I installed it on my home server - so it is a mirror with only one member.

Last edited by irfan (2008-08-13 23:48:09) Offline #7 2008-08-15 09:47:31 axel Member Registered: 2007-12-10 Posts: 68 Re: [SOLVED] Usb flah drive not working with Arch..Help.!! NOTE: I can NOT physically access the drive so I can not plug it in, unplug it, or even set it directly as SATA - it has to be USB enclosure sudo mke2fs -n /dev/xxx Down at the bottom of this output, should be a list of the backups Superblock backups stored on blocks: 32768, 98304, 163840, 229376, 294912, 819200, 884736, your post saved 4TB of data!!!

Except for The Holy Hand Grenade of Antioch I doubt there's a Holy Grail for this type of HW problem, especially if you can't have physical access to the HW. Photorec doesn't help either... This looks bad. Join 78 other followers Meta Register Log in Entries RSS Comments RSS WordPress.com This work is licensed under a Creative Commons Attribution-Noncommercial-No Derivative Works 3.0 Unported License.

If no error occurs I should be able to immediately see if the repair process worked by viewing my data. Unable to read /dev/sdbThat's strange - does it still work in the other O/S's?