"superblock could not be read" + lvm2

Hello guys,
after a power failure my system stop working, the boot procedure stops with the following msg:
:: Checking Filesystems
/dev/VolGroup00/LogVol02:
The superblock could not be read or does not describe a correct ext2 filesystem. 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 with an alternative superblock: e2fsck -b 8193 <device>
I commented the fstab line '/dev/VolGroup00/LogVol02 /home ext3 defaults 1 2', now I can loging and try to recover my data. In order to solve the problem I was following this thread http://bbs.archlinux.org/viewtopic.php?id=35412
I did the following steps:
1) Identify superblock backup #mkfs.ext3 -n /dev/sdb1
2) Run the e2fsck using an alternative superblock #e2fsck -y -b 98304 -B 4096 /dev/sdb1
/dev/sdb1 was not cleanly unmounted, check forced.
Resize inode not valid. Recreate? yes
Pass 1: Checking inodes, blocks, and sizes
Programming error? block #768 claimed for no reason in process_bad_block.
Programming error? block #768 claimed for no reason in process_bad_block.
Root inode is not a directory. Clear? yes
Inode 1476116 has illegal block(s). Clear? yes
Illegal block #464945 (1270814839) in inode 1476116. CLEARED.
Special (device/socket/fifo/symlink) file (inode 4751932) has immutable
or append-only flag set. Clear? yes
... TONS OF LINES ...
Inode 28966974 has illegal block(s). Clear? yes
Illegal block #1 (3644916482) in inode 28966974. CLEARED.
Illegal block #2 (150118149) in inode 28966974. CLEARED.
Illegal block #3 (1090716163) in inode 28966974. CLEARED.
Illegal block #4 (4087285209) in inode 28966974. CLEARED.
Illegal block #6 (2667960641) in inode 28966974. CLEARED.
Illegal block #8 (98124035) in inode 28966974. CLEARED.
Illegal block #10 (3644916482) in inode 28966974. CLEARED.
Illegal block #11 (150380293) in inode 28966974. CLEARED.
Illegal indirect block (1090716163) in inode 28966974. CLEARED.
Illegal double indirect block (4154394073) in inode 28966974. CLEARED.
Inode 28966974 is too big. Truncate? yes
Block #102763539 (768) causes directory to be too big. CLEARED.
Error storing directory block information (inode=28966974, block=0, num=3215973): Memory allocation failed
after a long time e2fsck ends but the problem remains.
I don't know if this may be the source of the problem... but insted 'normal' ext3 partition I have lmv.
# fdisk -l /dev/sdb
Disk /dev/sdb: 250.0 GB, 250000000000 bytes
255 heads, 63 sectors/track, 30394 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xe990e990
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 30394 244139773+ 8e Linux LVM
Bellow some information about lvm system:
# lvmdiskscan
Incorrect metadata area header checksum
/dev/sdb1 [ 232.83 GiB] LVM physical volume
0 disks
0 partitions
0 LVM physical volume whole disks
1 LVM physical volume
# pvdisplay
Incorrect metadata area header checksum
"/dev/sdb1" is a new physical volume of "232.83 GiB"
--- NEW Physical volume ---
PV Name /dev/sdb1
VG Name
PV Size 232.83 GiB
Allocatable NO
PE Size 0
Total PE 0
Free PE 0
Allocated PE 0
PV UUID AEEN6h-tCQ2-rGmL-NdCa-JQSY-puP9-6D6sCU
It seems that all information about my old lvm(VolGroup00/LogVol02) was lost?!?! I have no experience with lvm stuff. Please, any help will be appreciated.

Thank you for your reply.
sad to hear that...
but if I remember correctly, even in the begging of the problem I was not able to find /dev/VolGroup00/LogVol02 anymore, so I've tried vgcfgrestore and other stuff; latter on I've tried fsck on /dev/sdb1.
by using testdisk, I could see something:
Results
Linux 0 1 1 30393 254 63 488279547
EXT3 Large file Sparse superblock Backup superblock, 249 GB / 232 GiB
Linux LVM 0 1 1 30393 254 63 488279547
LVM2, 249 GB / 232 GiB
HPFS - NTFS 12111 1 1 30392 254 63 293700267
NTFS found using backup sector!, 150 GB / 140 GiB
Is it possible recover the data? I saw on internet people reporting success by using explore2fs under windows.

Similar Messages

[SOLVED] "Superblock could not be read" error on install

I've been trying desperatly to install Arch Linux on my main computer but this error almost always shows up after 1 or two reboots (usually when I'm finished installing base system and about to install Xorg):
:: Checking Filesystems
/dev/sdc3:
The superblock could not be read or does not describe a correct ext2 filesystem. 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 with an alternative superblock: e2fsck -b 8193 <device>
I installed Arch by following the install guide and choosing Auto-prepare partitioning where I chose EXT4 as FS for /home and / I believe, so Im guessing the filessytems are set-up properly.
I have no idea why this error keeps coming back reinstall after reinstall (with complete format of HD in each reinstall). First I thought the HD might have gone bad so I tried installing arch to another HD and the error still shows.
Sometimes if I reboot enough times the error doesn't show and sometimes it just doesn't go away, seems like it's kind of random.
The harddisk I am installing to is a 30GB IDE Maxtor harddisk (a couple of years old) and I also tried with a 40GB Seagate IDE harddisk both with no success. When I installed I had 2 other harddisks in my system; a 60GB OCZ agility SSD and a 640GB Wester Digital both on SATA channels, but they are unplugged now.
I'm really lost as what to do here, I love Arch Linux and have used it for some time on my laptop but I never had any kind of problems like this.
Here's output from 'fdisk -l' run from the "maintanence mode" I get into when the error shows "Give root password for maintenance".
I find it weird that Arch tells me the error is on "/dev/sdc3:" when my harddisk is /dev/sda (my other two harddisks are unplugged, but it shows the error both with and without them so I guess it doesnt matter):
fdisk -l
Device Boot Start End Blocks Id System
/dev/sda1 * 1 13 104422 83 Linux
/dev/sda2 14 587 4610655 82 Linus swap /Solaris
/dev/sda3 588 1544 7687102+ 83 Linux
/dev/sda4 1545 3738 17623305 83 Linux
Regards,
John
Last edited by johnrl (2010-01-28 14:42:15)

How many hard drives you have installed at the moment?
Atm I have 3 HDs installed; my Arch HD, my OCZ agility and my Western Digital.
Peasantoid wrote:
PirateJonno wrote:To find your UUID look in /dev/disk/by-uuid and use readlink to find the equivalent sdXX.
...or use `blkid`.
Thanks, I used blkid and set-up UUID in /etc/fstab and it seems to be working now.
Can anyone explain how come that the /dev/sdx assignments seems to be randomly distributed among my HDs on each reboot - is this normal? I tried using 'blkid' on a few reboots and noticed that the problem occured everytime the HD arch is installed on was NOT assigned to /dev/sdc, but when it was assigned to /dev/sdc (which was in fstab) it worked fine.
Isn't it weird that Arch seems to assign a different /dev/sdx number to each harddisk on reboots? I mean, if this is normal, why doesn't Arch use UUIDs by default? At first I thought the different /dev/sdx assignments was caused by changing boot order in the BIOS, but the assignments seem to change even when I don't enter the BIOS and just reboot without touching a thing - one reboot it works and one it doesn't (due to differnet /dev/sdx assignment to my Arch hd).
EDIT:
I found the answer to my question on http://wiki.archlinux.org/index.php/Per … ice_naming - Arch randomly assigns device nodes so it seems the UUID fix is the way to avoid unbootable systems.
Is it possible to make Arch use UUIDs in the install so I don't have to configure it manually afterwards? (Why doesn't it use UUIDs by default?)
Thanks for the answers,
John
Last edited by johnrl (2010-01-27 15:20:12)

[SOLVED] "The superblock could not be read..."

Good Evening.
In the beginning, I want to apologise if my English isn't as correct and comprehensible as I want it to be.
I am rather clueless Linux user with penchant for learning. I have used Slackware for some time, but I wanted to try out Arch because of it's superior package management, rolling release system and minimalism. I read through installation guides, and performed basic installation using 2009.08 CD without any problems. When I tried to boot into my new system I got following message:
:Mounting Root Read-only [DONE]
:Checking Filesystems [BUSY]
/dev/hda1:
and then
The superblock could not be read or does not describe a correct ext2 filesystem. 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 with an alternate superblock:
e2fsck -b -8193 <device>
and finally
FILESYSTEM CHECK FAILED
Please repair manually and reboot. Note that the root file system is currently mounted read-only. To remount it read-write type:
mount -n -o remount,rw /
When you exit the maintenance shell the system will reboot automatically.
I tried to run fsck, of course, as well as e2fsck or remounting / read-write but I always got the second message "The superblock could not be read... etc.".
My partitioning scheme is kinda tricky, because I make no distinction beetween production and testing machine. What is interesting, when I wanted to look at it using cfdisk from my indispensable Knoppix DVD I got something like:
FATAL ERROR: Bad primary partition 0:
Partition ends in the final partial cylinder.
Press any key to exit cfdisk.
But when I tried with root privileges it worked, and my 80GB hard drive looks something like that:
hda1 Primary Linux ext3 (/)
hda2 Boot Primary NTFS
hda3 Primary Linux
hda5 Logical W95 FAT32
hda6 Logical BeOS fs
hda7 Logical Linux ext2 (boot)
hda8 Logical Linux ReiserFS (tmp)
hda9 Logical Linux ReiserFS (usr)
hda10 Logical Linux ReiserFS (var)
hda11 Logical Linux ext3 (home)
hda12 Logical Linux Swap/Solaris (swap)
Only hda1, hda7, hda8, hda9, hda10, hda11 and hda12 are part of my Arch installation. I'm currently booting Windows XP through GRUB from NTFS partition (hda2) too.
Does anyone know how to make my Arch working installation?
Last edited by Schirase (2010-07-14 13:14:03)

My bad, I actually didn't read Begginers' Guide very carefully. I didn't realize that setting this UUIDs in fstab is so important. Now my fstab looks something like that (mind that this is slightly different partitioning scheme):
# /etc/fstab: static file system information
# <file system> <dir> <type> <options> <dump> <pass>
devpts /dev/pts devpts defaults 0 0
shm /dev/shm tmpfs nodev,nosuid 0 0
/dev/cdrom /media/cd auto ro,user,noauto,unhide 0 0
/dev/dvd /media/dvd auto ro,user,noauto,unhide 0 0
#/dev/fd0 /media/fl auto user,noauto 0 0
UUID=7a6e9456-69d4-4346-bf4d-803e5f61f100 / ext3 defaults,noatime 0 1 #/dev/hda5
UUID=bf4e4d66-2658-4e39-b1f8-b84cc157ba72 /boot ext2 defaults 0 2 #/dev/hda6
UUID=d3a5e92f-454e-47f9-8bfa-86804a322e55 /tmp reiserfs defaults,notail 0 2 #/dev/hda7
UUID=5333292d-4f3d-45a9-aa44-9df8c930244b /usr reiserfs defaults,notail 0 2 #/dev/hda8
UUID=bb25bd08-eeaa-4732-93a6-87e238c06029 /var reiserfs defaults,notail 0 2 #/dev/hda9
UUID=38298476-ea3d-4d15-a5d2-8c221a20ebe8 swap swap defaults 0 0 #/dev/hda10
UUID=de1d9d94-09ef-4429-b63e-fddea5e81195 /home ext3 defaults,noatime 0 2 #/dev/hdb1
and I am happily using Arch right now. However, I have got strange non-critical issues with partitions and disks which I explained in http://bbs.archlinux.org/viewtopic.php? … 82#p791582.

Superblock could not be read - sometimes

Hi all,
I recently installed Arch Linux on one of my desktops and have been noticing the "superblock could not be read" error on some of the bootups. It doesn't happen all the time, only sometimes. I don't know what's causing it or why it's happening. Here is a picture of the error:
Here is a picture of my /etc/fstab:
Sorry for the poor quality images. My phone was the only camera I had available at the time.
Last edited by solarwind (2010-04-18 09:14:09)

ichbinesderelch wrote:reading that i have exactly the same problem, sometimes, but it all started since i set up my arch box with 64bit and ext4, nevery had that kinda of error with ext3, so could this be ext4 related, or faulty hardware?
I am running 64 bit on ext4 as well.
Update: I did some searching and updated my fstab to use UUIDs instead. I tried a few bootups and I'm not getting the error anymore. I'll post another update.

Cannot sync, error message "could not be read" for an iPod no longer in use

I have two problems. I upgraded iTunes to 7.2 and the very next morning my iPod died. It is completely unresponsive. Maybe it's coincidental. So I bought a new 80 gig iPod and gave it a different name than the old dead iPod. Now when I try to sync the new iPod, it goes for about 10 minutes, then it fails with this message:
Attempting to copy to the disk "old iPod name" failed. The disk could not be read from or written to.
It is complaining that it can not read the old dead iPod that is NOT hooked up to the computer! Somehow, minutes into syncing, iTunes has forgotten which iPod it is looking at. I have seen the article about the "cannont be read" message and it is not relevant. I need to make iTunes forget about the old dead iPod so it will stop looking for it. I've tried removing the files from "Documents and Settings" but iTunes still remembers the old unit. Where else does it store information? Any recommendations?
Windows XP

Attempting to copy to the disk "old iPod name" failed. The disk could not be read from or written to.
It is complaining that it can not read the old dead iPod that is NOT hooked up to the computer!
Okay, that can sometimes be caused by a Windows drive letter confusion. For troubleshooting advice on that possibility, see the following document:
Windows confuses iPod with network drive or hard drive and may keep iPod from mounting or songs may seem to disappear

IPod Error Message: "The disk could not be read from or written to."

Hello!
I was syncing my sister's video iPod (30GB) and this error message pops up "Attempting to copy to the disk. "SARAH'S IPO" failed. The disk could not be read from or written to."
I have restored it three times already, but once it starts putting the music and files back onto the iPod it pops up with that error message. I have updated to the latest version of iTunes and iPod software available. My OS is Windows XP.
Is this something serious? Will I be able to fix it myself or will I need to send it in to be fixed by Apple? Will that be expensive? We didn’t get the Apple replacement plan. D=
Any help would be greatly appreciated. Thank you in advance. ^_^
PowerBook G4 Mac OS X (10.4.3) 15" PowerBook 1.5 GHz PowerPC G4, 1.5GB RAM - Windows XP with iPod 5 Generation

Okay I went thru that entire list and here's what I got...
(1) My OS is XP and is running fine.
(2) I've updated my windows
(3) I don't know of any software that might be interfering.
(4) There are no damaged files.
(5) My Windows hard-drive is not damaged and I've tried restoring my iPod's disk thru iTunes but it still doesn't work.
(6) I don't have an iPod photo and I can't find the folder to delete the cache if if I did.
(7) The USB cord is firmly connected into my USB port and my iPod
(8) My music is on my external hard-drive so I need to keep 3rd-party hardware connected
(9) I will try another USB cord to see if that works.
Is there anything else that I can do? Can Apple fix this?
Please let me know.

IPod cannot be synced because external hard drive could not be read

I moved my music folder to an external hard drive to create space on my laptop, and changed the location under Preferences / Advanced. Since I did this, my iPod trys to automatically sync but gives the error message "The iPoD "[name]" cannot be synced. The disk could not be read from or written to." The external hard drive is on and working. Is there some reason that the iPod will not sync with this external hard drive? What do I need to do to fix it? Thanks, Bill

First question, since you made
the change, can you still play your music from within
iTunes?
Patrick
Sorry for the delay in answering as I have been traveling. Yes, I can play music from iTunes. The music is located on my external hard drive. iTunes software is on my laptop, and the music library points to the music folder on my external hard drive.
Thanks, Bill
Dell Laptop Windows XP

Disk could not be read from or written to

I'm a new ipod user. I can get songs on my ipod. But when I go to get photos I get an error message saying, "ipod cannot be updated. The disk could not be read from or written to."
In itunes I can see the ipod. When I go to look at My Computer, it does not show the ipod as a disk drive.
Thanks!

I'm a new ipod user. I can get songs on my ipod.
But when I go to get photos I get an error message
saying, "ipod cannot be updated. The disk could not
be read from or written to."
In itunes I can see the ipod. When I go to look at My
Computer, it does not show the ipod as a disk drive.
Thanks!
It's so simple, dont worry. Just connect your ipod to the computer. iTunes must open. In iTunes clcik on the small ipod icon which appears at the right bottom of the itunes window. click on that icon and another window with some options will be opened. Click on "enable disk use" and make this selection marked and click ok.
it'll certainly help!

Disk could not be read from

Suddenly my Ipod will not sync. The error message says "...disk could not be read from or written to..." We tried the HOLD TOGGELING. But that didn't work. It won't let me restore the Ipod either because it says other programs are currently in use.
Suggestions would be greatful!

Welcome to the discussions,
if the reset did not work, did you try to put it into disk mode? http://support.apple.com/kb/HT1363

Error Message: "Disk could not be read from or written to".

New 5th Gen. was downloading CD's I loaded into iTunes just fine; when uploading tunes into iPod yesterday this error message appeared: "Attempting to copy to the disk (iPod name) failed. Disk could not be read from or written to". Restored iPod with 1/10/06 update of iPod Install; using iTunes 6.0.2; operating system 10.3.9. Frustrated. iPod useless at this point. Anyone found a fix to this vexing problem?
Thanks,
John

Thanks Jeff. Only thing that rings true is updating OS; when I tried to downoad 10.4 message said I 'could not on this computer'. Since I purchased and installed 10.3 a year ago I don't understand. Also, iPod was downloading perfectly until two days ago when -36 appeared. Bummer. I am not a techie, Apple tech support does not have a clue, and iPod is useless. Ideas?

"The disk could not be read from or written to"??

When I try to sync my ipod it gives me following error message "Attempting to copy to the disk 'My Ipod' failed. The disk could not be read from or written to."
Have not reset or restored it yet, wondering if there is anything I can do that doesn't involve me deleting all the songs on my ipod.
5th Gen 80g Ipod, G5 Imac Mac OS X (10.4.9)

See if this troubleshooting article helps.
Disk cannot be read from or written to error syncing iPod in iTunes.

Attempting to copy to the disk Ipod failed. the disk could not be read from

Keep getting error message Attempting to copy to the disk.....Ipod failed. The disk could not be read from or written to. I can copy to Ipod from my laptop however, can not sync with my G-4 tower. I keep my library on an external HD Lacie d2. I've tried all the possibilities from the support page to no avail.. Need help... When error refers to disk is it referring to my external HD

Hi c2xist,
And you did follow all of the suggestions from this article?:
"Disk cannot be read from or written to" when syncing iPod
Also, you could go through these iPod troubleshooting steps, and see if they are of any help:
The Five Rs
-Kylene

9.1.1 sync problems: "The disk could not be read from or written to."

Using OSX 10.6.3 and upgraded to iTunes 9.1.1. Once I did, I keep getting the following error message: "Attempting to copy to the disk [my ipod] failed. The disk could not be read from or written to." This is followed by another error message: "iTunes could not copy {name of file} to the iPod {iPod name} because the file could not be read or written."
I tried deleting the files mentioned in the error message, but then the message returns with the name of a different file. At this rate, I'll be deleting all my files!
I tried checking everything on the Knowledge Base article: http://support.apple.com/kb/HT1207
I tried restoring my iPod (twice), but it didn't help.
All my software is up to date. I haven't added any new software since I upgraded iTunes.
NOW...when I try to sync my iPhone, I get the same error message.
What's going on, and can anyone help?
This is very annoying since I can't sync my iPhone which I need or my iPod which I would like.

ArizonaDAK wrote:
"iTunes could not copy {name of file} to the iPod {iPod name} because the file could not be read or written."
check if you have read & write permissions for your iTunes music folder. in finder, right-click on it and +get info+. unlock the little padlock (you may have to enter your admin password) and change the permission settings. next, click on the little gear-shaped icon and +apply to enclosed items+ like so
you may also give everyone read & write access. if this doesn't help, try the same on your iTunes folder (not just the iTunes music folder).
if that make no difference, try reinstalling iTunes. click here and follow the instructions. next, download a fresh copy from here: http://www.apple.com/itunes/download/.
you might also try to _*remove and reinstall the Apple Mobile Device Service*_
JGG
edited by the Jolly Green Giant (where Green stands for environmentally friendly)

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any

My LR 4 suddenly no longer recognized my memory cards. I am using the same cards and cameras but consisitently get the error message:"files not imported because the files could not be read. they are jpg and nef files...I am stuck without my workhorse! Any advice is helpful. This has never happened in 6 years

answered in your other thread LR 4 suddenly no longer recognizes files.

In trying to update I received this message: Firefox 3.6.3(2).dmg.part could not be saved, because the source file could not be read.

In trying to download an update I first received: "There were problems checking for, downloading, or installing this update. Firefox could not be updated because: No data was received (please try again)" It also gave a link to download manually. When I tried from the Firefox website I got: /Users/(deleted for privacy)/Desktop/Firefox 3.6.3(2).dmg.part could not be saved, because the source file could not be read.
Try again later, or contact the server administrator. I tried this 3 times.
== This happened ==
Not sure how often
== Mon around 11 am, central time, May 17, 2010

I have tried downloading the file several times and get the same message: "No data received." I have no other system problems, I navigate well to other sites, but I'm unable to download this upgrade. Any suggestions?

"superblock could not be read" + lvm2

Similar Messages

Maybe you are looking for