[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.

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)

"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.

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.

Error when syncing iPod: The disk could not be read from or written to!!

I have an iPod mini which worked fine on my Windows XP.
Recently got Windows Vista and I downloaded iTunes and my put my music in the library.
When I plugged my iPod into the Vista, it said it was syncing all the songs to my iPod.
After about 3 hours, whilst syncing the last song a notice came up saying, 'Attempting to copy to the disk failed. The disk could not be read from or written to.'
I restored my iPod and reinstalled iTunes but the same thing happend.
I decided to plug my iPod back into the Windows XP, where I've had no problems. When I did this and started snycing all the songs, I got the notice come up again.
'Attempting to copy to the disk failed. The disk could not be read from or written to.'
I haven't been able to use my iPod now for about 5 weeks because I cannot solve the problem so any help will be much appreciated!
Thanks

You have posted in the Mac forum for problems & questions usting the iTunes store. You will probably find more help in the following forum.
http://discussions.apple.com/forum.jspa?forumID=800

Moving library to external hard drive and get the error "Copying files failed. The disk could not be read from or written to"

Hello,
I'm moving my library to an external hard drive.
I've made sure to use the 'Keep iTunes Media Folder Organized' option when pointing to the new library location.
I select 'File'->'Library'->'Organize Library', I select to 'Consolidate Files', click 'OK' and get ther error message "Copying files failed. The disk could not be read from or written to".
I've read elsewhere that there may be a corrupted file that I need to sequester somehow and perhaps add it back however I'm not certain how I can locate that file because the status window doesn't indicate which file it's attempting to transfer when the error appears.
Any tips?
Thank you,
Greg H
iTunes 10.6.3

OK I figured it out!
It was a dodgy file....I sorted the file folders by date, and as it turned out within the "compilations" folder there was a CD where only about half the tracks seemed to have been copied over. Could not have identified this simply from the time indicated on the finder folder sort, because there were several CDs copied over in the that same minute.
I went back to the original itunes folder, deleted all the files from that CD in itunes, then also deleted all those files from the original disk and the target disk.
Tried the "consolidate library" again, and it completed nicely. 200megs of music and videos.
Very happy to solve this problem after 3 weeks.

The Disk Could not be read from or written too

I just got the new 80gig video ipod yesterday for my b.day. While syncing it to my laptop it gets about halfway through then it stops and i get the error "Attempting to copy to teh disk "my name" failed. The disk could not be read or written too. I know its not the ipod cause it was successful syncing to my work computer however that does me no good. I've got the latest software updates installed, any help?
Mac OS X (10.4.8)

Hi Haleboy!
Have you seen if this Support article helps with your issue at all? -> "Disk cannot be read from or written to" when syncing iPod
-Kylene
If any post helps or solves your issue, please mark it that way accordingly. Thank you for helping the boards!

The ipod "IPOD" cannot be updated. The disk could not be read or written to

"The iPod "IPOD" cannot be updated. The disk could not be read or written to"
"The iPod "IPOD" cannot be updated. An unknown error occurred. (-50)"
I have been dealing with this ever since I installed iTunes 7. I had been getting this message with my previous version, but at least the files would load onto the iPod once I deleted the files in the library and reloaded them. Now, nothing works.
I attempted to restore the iPod, but guess what? I got this message every time:
"The iPod "IPOD" could not be restored. An unknown error occurred (1418)"
When I checked drive E on the Device Manager on My Computer, it said the device was working fine.
Desperate to fix the problem, I began searching online for other solutions when I stumbled upon someone mentioning the option to format the iPod with fat32, suggesting that as a way to solve the problem, so I did so. After that, nothing has worked. The device manager now says that there are no drivers for drive E and iTunes won't let me restore the iPod.
I'm plumb out of ideas. What's left to do? I'm not rich enough to just say, "Oh well! La dee da! Let me go buy another iPod shuffle." Is there any way to fix this?

I finally reinstalled iTunes and my 2G Shuffle on my another station (PC portable + Windows XP) and that functions without trouble.
As I followed exactly the same procedure of installation, it's difficult to me to explain differences.
For each pc :
- No iPod or iTunes previously installed before this one
- All the rights (administrator)
Differences :
- The OS (Windows XP and Windows XP Pro)
- A lot of USB peripherics declared on my first PC.
I tend to think that the problem comes from the detection or the declaration of the port usb, but I'm not at all an expert.
So my trouble is solved, but not with a satisfactory solution.
Patrick
Windows XP Pro

Error "COPYING MUSIC FAILED. The disk could not be read from or written to"

After following the procedurest to move the iTunes music, the computer started whirring away, happily copying and consolidating all the song files to the new target folder.
After copying 68gigs of 130gigs perfectly, it stopped dead and the following iTunes error message appeared:
"COPYING MUSIC FAILED. THE DISK COULD NOT BE READ FROM OR WRITTEN TO"
I am copying to an external LaCie 500g hard disk, and the current music file is split between folders on the laptop and folders and a 2nd external LaCie Hard disk. It did not appear to have any problems copying and consolidating files from both locations, until the error message showed up.
How can I solve this?
I really need to consolidate this music file.
macbook pro Mac OS X (10.4.6)

OK I figured it out!
It was a dodgy file....I sorted the file folders by date, and as it turned out within the "compilations" folder there was a CD where only about half the tracks seemed to have been copied over. Could not have identified this simply from the time indicated on the finder folder sort, because there were several CDs copied over in the that same minute.
I went back to the original itunes folder, deleted all the files from that CD in itunes, then also deleted all those files from the original disk and the target disk.
Tried the "consolidate library" again, and it completed nicely. 200megs of music and videos.
Very happy to solve this problem after 3 weeks.

Failing to sync movies: "The disk could not be read from or written to."

Hello,
I had approx 10 movie files on my ipad which synced and played fine for the first month I had my ipad. I recently tried to add 3 more movies all in the exact same format as the previous 10, however now I get a message saying that the file could not be copied as the disk could not be read from or written to. I haven't made any major changes (that I am aware of) that would have triggered this.
I've checked that my ipad and OS software are up to date, and tried restarting both my ipad and my comuter (a Macbook).
I figured maybe I was out of disk space, and the capacity bar in itunes was wrong, so I removed 3 of the movies and tried to add one of the new ones - same error. I then put one of the old movies back on, and it worked fine.
So, thinking maybe the problem could be solved by restoring my ipad, I created a backup and performed a restore. My apps and photos are safely back on the ipad - but now none of the movies will sync, all of them giving me the same error saying the disk could not be read from or written to.
Has anybody got any idea what's going on? It's extremely frustrating as the ipad is such a good tool for watching movies on the go.
Thanks,
Sam

I have run into the same problems on my iPod Classic. It seems the last couple of movies I have purchased from iTunes are the source of the problem. An interesting thing I have found is that, when purchased, the files causing the issues have saved to my internal HD, instead of the external drive that I have set as my library location.
Another interesting thing is that this is isolated to the last 2 movies I have purchased and 1 of the last 2 rentals. Not with any music I have purchased or the other rental. So there is no consistency in it being only newest files. The only consistency is that it is movies that oddly store in the wrong location.
I have done everything from trying to move my iTunes library location, resetting the ipod, software is up to date in everything (iPod, iTunes, Mac). I have tried disconnecting the external drive, and manually managing music and videos for the iPod sync. Everything will sync with the exception of the recent movies stored in the wrong location. Also, when trying to move the files from my internal hard drive to my external where the rest of my library lives, I get the same "...read or written to" error as I get when trying to sync to my iPod. No other files seem to be having any trouble moving around from internal to external to ipod.
Sorry I don't have a solution yet. Hopefully this helps narrow down the problem, and save some troubleshooting time.

The iPhone cannot be synced. The disk could not be read or written to.

+The iPhone cannot be synced. The disk could not be read or written to.+
That's the message I get when I sync my iPhone now after flawless syncing since the second day they came on sale. I restarted, I repaired permissions. The iPhone is only half full. I have tried a couple of different usb to iPhone chords. After trouble shooting I have found that if I don't sync iPhoto it syncs everything else just fine. I have deleted the iPhoto prefs. I have reinstalled iLife. I have reinstalled iTunes and deleted the iTunes prefs. I have gotten a brand new iPhone from the Apple store. I have backed up and deleted every photo in iPhoto and it still gets the error message.
Starting to get frustrated.

Unfortunately, I'm an Outlook junkie, and I need to sync my iPhone (1st Gen) with Outlook. I had no problems under XP. I even synced my device to Vista Business running out of Boot Camp and via Fusion.
When I upgraded to Vista Ultimate and Office 2007 (freshly installed) my iPhone refused to sync anything but my Contacts, Calendar, and Bookmarks. It didn't matter whether I was running under Fusion or natively via Boot Camp -- I would get a variety of errors, but mostly "the disk could not be read or written to" wtih the occassional "unknown error" thrown in to make my life even more miserable.
It would occasionally sync an audio or video file, but 99 times out of 100 it would die in the middle of the sync, trash something on the phone, and force me to restore it.
Restoration, though, was not possible under Windows. I would try repeatedly to restore the phone from Vista, with no success. In fact, I tried to install the updated 2.0 firmware last week, which "bricked" the phone for about 4 hours. The only way that I could restore the device was under OS X. Naturally, the error returned the first time I tried to sync on Windows again.
I was almost to the point of declaring the iPhone toasted, smashing the overpriced little trinket that's caused me so much agony into iPieces and then dropping it into an envelope and mailing it to Steve J. with a letter stating that a $600.00+ "revoltionary internet device" shouldn't croak 1 year after purchase.
<RANT>
I mean think about it -- getting bent over on pricing 2 months after purchase, Apple releasing a 3G version barely one year later (and for significantly lower price than the original) and having to sign a 2 year contract with the baby Satan that is AT&T isn't exactly what I would call a GOOD experience. Not to mention the activation fiasco, etc.
</RANT>
At any rate, all the Windows jokes aside, I believe I've finally solved my problem and it may help the others having this same problem on dual-core or hyperthreading processors.
With iTunes running, go to the Task Manager, select the Processes tab and find the iTunes processes (AppleMobileDeviceHelper.exe, iTunes.exe, and iTunesHelper.exe). Right-click on each and select "Set Affinity..." from the context menu.
In the "Processor Affinity" dialog, you should see both CPU 0 and CPU 1 checked, which is the default. UN-CHECK CPU 1, so that only CPU 0 is checked, then click "OK".
You may need to retstart iTunes and/or the services, but I didn't need to do that (and technically, you shouldn't have to do that).
Try your sync again. I'm syncing flawlessly again after that little tweak. Perhaps this is something odd about iTunes under Windows on multi-core or hyperthreading processors (read: race condition or something similar)?
I'm keeping my fingers crossed that this will continue to work, otherwise I go the smash-and-mail-to-Steve route.

Application error The memory could not be read 0x00000014

Hi everyone,
I would like to know if any of you have come across this issue.
I'm running an application built by me in a computer with LabVIEW Run-time 9 in which I display a PDF file using an ActiveX control:
The target computer runs Adboe Reader 9.0. Everything works perfect until the application is closed. From time to time (nearly most of the times), I've got the next windows error:
"Application Error: The instruction at "0x0ffd609c" referenced memory at "0x00000014". The memory could not be "read". Click on OK to terminate the program".
Trying to find out the reason, I found a couple of forums which claim that the reason is a bug in Adobe 9.0 (actually, I've tried running the application with Adobe Reader 8 and I cannot repeat the error). Any of you have had this error before and found a solution? Those links weren't about LabVIEW and I have no idea how to get around this issue.
Any help is appreciate it.
Thanks in advance.
Dani
Solved!
Go to Solution.

To who may be interested, I managed to find a workaround for this bug in Adobe Reader 9.0.
It seems that, somehow, LabVIEW, and other programming tools, straggle with this version of Adobe (I assume that this is due to this bug) when closing the reference to Adobe created by the ActiveX container. So the solution would be closing "by hand" this reference, and telling Windows to free all the relation between the application (LabVIEW for us) and Adobe. The idea is that when we've done with the VI which displays the PDF via ActiveX, we should close the reference to the ActiveX control, close the reference to the VI, and:
- process all the Windows messages currently in the message queue (.NET: System.Windows.Form.Application -> DoEvents
- run CoFreeUnusedLibraries in "ole32.dll"
I hope this information can help somebody, as I wasted too much time to figure this out (finding eventually the answer in a forum of Adobe!)
P.S. For those who program in C# as well, check this link; this was my source.

"The instruction at "0x1000865c" referenced memory at "0x1000865c'. The memory could not be "read".

Firefox 7 crahes on startup. I get a dialog that says "The instruction at "0x1000865c" referenced memory at "0x1000865c'. The memory could not be "read". I've tried everything- clean installs, renamed profile, etc., and this happens even when starting in safe mode. Any ideas? Thanks
BTW, I don't have a
"submitted" subfolder in Crash Reports. All I have is two files and neither has the typical crash report ID. Also, I'm running an XP/SP3 laptop. All was find until I accepted the update!
Thanks

On my .Net application, I put this code to solve this problem on exiting the program:
Private Sub BatchOrganizerForm_FormClosing(ByVal sender As Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles Me.FormClosing
If Me.pdfViewFile IsNot Nothing Then
System.Threading.Thread.Sleep(2000)
Me.pdfViewFile.Dispose()Application.DoEvents()
End If
End Sub
I think the problem is you must give time to dispose first the pdf control before the application.
This code worked for me. I hope this helps.

The instruction at "0x0700609c" referenced memory at "0x00000014". The memory could not be read

When viewing a PDF file in a browser using Adobe Reader v9.0 I received - The instruction at "0x0700609c" referenced memory at "0x00000014". The memory could not be read.
This occured in Google Crome after viewing a pdf file and then closing the Crome application. I was also able to reproduce this in a .NET application using the System.Windows.Forms.WebBrowser control and loading PDF files in the browser control.
The error does not occur every time but can be reproduced in my .NET application fairly easily by loading several pdf files quickly then closing the application.
This error does not occur when using Adobe Reader v8.

On my .Net application, I put this code to solve this problem on exiting the program:
Private Sub BatchOrganizerForm_FormClosing(ByVal sender As Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles Me.FormClosing
If Me.pdfViewFile IsNot Nothing Then
System.Threading.Thread.Sleep(2000)
Me.pdfViewFile.Dispose()Application.DoEvents()
End If
End Sub
I think the problem is you must give time to dispose first the pdf control before the application.
This code worked for me. I hope this helps.

The memory could not be read

1. Just download Adobe Reader XI Pro for windows 8.1. My version is the 11.0.9. But It is not working properly. My OS is Windows 8.1 64-bits.
2. I can normaly open .pdf files on my computer. But when I tried to open a .pdf file on the web [www.stj.jus.br], one dialogue appear as 1.) AcroRd32.exe Error, The instruction at 0x51ad3e3f reference memory at 0x031c31dc. The memory could not be read. Click on OK to terminate the program.
3. Now, when I try to open again, the dialogue does not appear anymore, but the file does not open too. Adobe quickly open and shuts down.
4. Please, how can I solve the problem?
Thank you.

Hi Pat.
1. I've tried that, but the problem persists. What should I do?
Thank you.

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

Similar Messages

Maybe you are looking for