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

Similar Messages

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.

[SOLVED] Pacman "config file could not be read" error during Arch ins

I've been attempting to get Arch setup for a while now, and after having some trouble with partitions, my wireless connecting, and setting up repos and mirrors, which the Wiki helped me solve, I've hit a bigger bump. While updating the system using pacman as the Beginners Guide says to do, I get errors when I try to continue the update process as follows :
btw: I'm typing this on a laptop next to my computer
[root@McArch~]# pacman -Syu
error: config file /etc/pacman.d/core could not be read
error: config file /etc/pacman.d/extra could not be read
error: config file /etc/pacman.d/community could not be read
:: Synchronizing package databases . . .
error: failed to updated core (unexpected error)
error: failed to updated extra (unexpected error)
error: failed to updated community (unexpected error)
error: failed to synchronize any databases
Any tips as to whats going on? I've tried to created said files, and even insert mirrors into the file, like in the /etc/pacman.d/mirrorlist file but this doesn't seem to help
Last edited by Windfinder (2008-09-29 20:43:29)

Glad you got it working.
I'm not sure what happened in your install but I just finished using an old 2007.08 iso and pacman first starts out with /etc/pacman.d/core, etc/pacman.d/extra, /etc/pacman.d/community ... etc., but I never had your problem when I did the #pacman -Syu after initial install reboot. The pacman update removes the above mentioned repos and replaces them with a single /etc/pacman.d/mirrorlist. You must have messed up an initial config file somehow as I couldn't get the same errors you got. It looks like you had your /etc/pacman.conf file messed up somehow and when you pointed it to the mirrorlist it could finally work properly. I'll just include my /etc/pacman.conf file and /etc/pacman.d/mirrorlist so you can compare. NB* these are from my x86_64 so for 32 bit machines i686 would replace x86_64 in the files.
# /etc/pacman.conf
# See the pacman.conf(5) manpage for option and repository directives
# GENERAL OPTIONS
[options]
# The following paths are commented out with their default values listed.
# If you wish to use different paths, uncomment and update the paths.
#RootDir = /
#DBPath = /var/lib/pacman/
#CacheDir = /var/cache/pacman/pkg/
#LogFile = /var/log/pacman.log
HoldPkg = pacman glibc
# If upgrades are available for these packages they will be asked for first
SyncFirst = pacman
#XferCommand = /usr/bin/wget --passive-ftp -c -O %o %u
#XferCommand = /usr/bin/curl %u > %o
# Pacman won't upgrade packages listed in IgnorePkg and members of IgnoreGroup
#IgnorePkg =
#IgnoreGroup =
#NoUpgrade =
#NoExtract =
# Misc options (all disabled by default)
#NoPassiveFtp
#UseSyslog
#ShowSize
#UseDelta
#TotalDownload
# REPOSITORIES
# - can be defined here or included from another file
# - pacman will search repositories in the order defined here
# - local/custom mirrors can be added here or in separate files
# - repositories listed first will take precedence when packages
# have identical names, regardless of version number
# - URLs will have $repo replaced by the name of the current repo
# Repository entries are of the format:
# [repo-name]
# Server = ServerName
# Include = IncludePath
# The header [repo-name] is crucial - it must be present and
# uncommented to enable the repo.
# Testing is disabled by default. To enable, uncomment the following
# two lines. You can add preferred servers immediately after the header,
# and they will be used before the default mirrors.
#[testing]
#Include = /etc/pacman.d/mirrorlist
[core]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[extra]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
[community]
# Add your preferred servers here, they will be used first
Include = /etc/pacman.d/mirrorlist
# An example of a custom package repository. See the pacman manpage for
# tips on creating your own repositories.
#[custom]
#Server = file:///home/custompkgs
/etc/pacman.d/mirrorlist
# Arch Linux repository mirrorlist
# North America
# - United States
Server = http://mirror.neotuli.net/arch/$repo/os/x86_64
Server = http://holmes.umflint.edu/archlinux/$repo/os/x86_64
Server = http://archlinux.unixheads.org/$repo/os/x86_64
Server = ftp://ftp.archlinux.org/$repo/os/x86_64
Server = ftp://locke.suu.edu/linux/dist/archlinux/$repo/os/x86_64
Server = ftp://ftp.gtlib.gatech.edu/pub/linux/distributions/archlinux/$repo/os/x86_64
Server = ftp://mirror.cs.vt.edu/pub/ArchLinux/$repo/os/x86_64
Server = http://mirrors.easynews.com/linux/archlinux/$repo/os/x86_64
Server = ftp://ftp.ibiblio.org/pub/linux/distributions/archlinux/$repo/os/x86_64
Server = http://mirror.rit.edu/archlinux/$repo/os/x86_64
Server = http://mirror.umoss.org/archlinux/$repo/os/x86_64
# - Canada
Server = ftp://mirror.csclub.uwaterloo.ca/archlinux/$repo/os/@carch
Well it was an interesting way to kill 30+ minutes.

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

"ABC could not be saved, because the source file could not be read" error when downloading

Almost every time I download a file, the download gets to the end and then I get this error "<filename> could not be saved, because the source file could not be read", and then the download fails.
I checked my addons and they are not the problem. This doesn't happen when I try another Firefox profile. I tried several solutions offered in "http://kb.mozillazine.org/Unable_to_save_or_download_files" but they didn't help. It's not my antivirus.
I hate to start another profile because I have my current one just the way I like it.
Please help!

You can check the file attributes of all the files in the Firefox Profile Folder to make sure that you have write permission.
*http://kb.mozillazine.org/Profile_folder_-_Firefox
Create a new profile as a test to check if your current profile is causing the problems.
See Basic Troubleshooting: Make a new profile:
*https://support.mozilla.com/kb/Basic+Troubleshooting#w_8-make-a-new-profile
If that new profile works then you can transfer some files from the old profile to that new profile (be careful not to copy corrupted files)
See:
*http://kb.mozillazine.org/Transferring_data_to_a_new_profile_-_Firefox

Memory could not be read Error Fixed

At least 6 months ago, I noticed that every time I opened my
default page in Dreamweaver and closed it, Dreamweaver would crash.
I would get the famous Application Error, "The instruction at
"0x5ad71531" referenced memory at "0x00000014". The memory could
not be "read". Click OK to terminate the program."
What I figured out is that right about that time, I had
switched my default browser for viewing to Firefox Mozilla.
Today, while I was testing some things out, I noticed that
the Check Browser Support list, only had Internet Explorer and
Netscape.
After I added Firefox Mozilla to the list of browser to check
compatibility for, the problem disappeared.
Go figure.

> At least 6 months ago, I noticed that every time I
opened my default page in
> Dreamweaver and closed it, Dreamweaver would crash. I
would get the famous
> Application Error, "The instruction at "0x5ad71531"
referenced memory at
> "0x00000014". The memory could not be "read". Click OK
to terminate the
> program."
>
> What I figured out is that right about that time, I had
switched my default
> browser for viewing to Firefox Mozilla.
>
> Today, while I was testing some things out, I noticed
that the Check Browser
> Support list, only had Internet Explorer and Netscape.
>
> After I added Firefox Mozilla to the list of browser to
check compatibility
> for, the problem disappeared.
Great detective work!
I can't seem to reproduce this problem. What version of DW do
you use?
Was Internet Explorer or Netscape defined as either Primary
or Secondary
browsers? Any other details to help me reproduce this so we
can fix it
if it's still in the code?
Thanks,
Randy

The instruction at 0x100072b8 referenced memory at same could not be read-error message always appears at startup and cannot be eliminated.

firefox.exe - Application Error
The instruction at 0x100072b8 referenced memory at 0x100072b8. The memory could not be read.
Click on OK to terminate the program
Click on CANCEL to debug the program
Either of the above options terminates Mozilla - neither option fixes the problem - however Mozilla works as long as the error message remains on the desktop.

We cannot know. You are not offering any system information nor actually telling what program you use and what you do when the crash occurs.
Mylenium

Reports 3.0 "Memory could not be read" error

If the object referenced by a trigger is deleted without also deleting the trigger itself the following error message appears when attempting to access or delete the trigger:
R30DES32.EXE - Application Error
The instruction at "0x649e401e" referenced memory at "0x00000402". The memory
could not be "read".
Click on OK to terminate the application
Click on CANCEL to debug the application
<<OK>> <<Cancel>>
Clicking either button terminates the session.
How can I get rid of a trigger in this situation when to highlight it and press the delete key only results in needing to restart Reports?
TIA,
Dan Wilterding
[email protected] (aging e-dress, soon to go away)
[email protected] (newer, faster, shinier e-dress with better mpg)

GX is disabled since installing. I don't know what or who installed manycam but i will disable it and come with updates. Thank you, kind sir.
Later edit: OK Uninstalled manycam just changed the error code, but the error is still there. I attached the picture.
Attachments:
DSC_2877.JPG ‏2879 KB

Skype 7.0 memory could not be read error on shutdo...

Hello, yestarday I upgraded to Skype 7.0.0.100 and when I shutdown the computer, restart or log off I get this error message: The instruction at 0x60afedfe referenced memory at 0x069b26a0. The memory could not be read.
I mention that I unchecked the option to "play a sound when I sign out" and I disabled uPnP (as mentioned in other threads).
This issue is the result of a conflict with the Asus Xonar DG SI 7.1 audio card, but unchecking the option to "play a sound when I sign out" fixed the problem in the previous version 6.
The error doesn't generate any kind of information in the event viewer.
My OS: Win 8.1 Pro
Any suggestions?
Attachments:
DSC_2877.JPG ‏2784 KB

GX is disabled since installing. I don't know what or who installed manycam but i will disable it and come with updates. Thank you, kind sir.
Later edit: OK Uninstalled manycam just changed the error code, but the error is still there. I attached the picture.
Attachments:
DSC_2877.JPG ‏2879 KB

ITunes 7: "memory could not be read" error

I am running the latest version of iTunes 7 and sometimes get the following error message:
"Instruction at Ox5ad71331 referenced memory at 0x00000014. Memory could not be read"
This happens after iTunes crashes. The appearance of the crash is that the font will become very dark/bold and dark lines will appear around the cells of the library, then the program will crash.
Is this related to iTunes 7 or Multi-Plugin, which I use to make my media buttons on my laptop work with iTunes? I have no skinning options chosen.
Thanks.

I uninstalled the Multi-plugin and haven't had the problem since, in fact, no crashes at all.

Referenced memory could not be read - error

Hey, In an application on stop command, I exit from labivew on exit I get an error the referenced memory could not be read click ok to terminate program can any one suggest why this error is seen
how this can be resolved?
enclosed a screen shot of error
Regards
anil
Attachments:
error log.PNG ‏6 KB

Hi AndreasC,
This error message occurs when LabVIEW memory space goes corrupt and is often due a DLL or CIN code.
There can be two reasons for this:
1. Try removing all DLL calls in your code and see if it works. Most of the time, the corruption is traced to a call to a DLL function that has incorrectly passed inputs to the Call Library Function node, often by passing an uninitialized string or array, or by writing past the bounds of the string or array in the DLL function. Some DLL functions assume that a string buffer is presized to 256 bytes, 1 KB, or some other size. If a smaller sized string buffer is passed, the DLL can write past the buffer and corrupt the dataspace that follows.
2. This error can also be caused when running a LabVIEW built executable. If the VI calls a WinAPI DLL function and uses the full path to the DLL in the Call Library Function Node, the LabVIEW Application Builder will create a copy of the DLL in the data directory of the executable. Some DLLs such as WinAPI DLLs should only reside in one location, such as C:\WINDOWS\system32, otherwise errors/crashes can occur when called. To prevent this, remove the DLL path in the Call Library Function Node when calling WinAPI DLLs.
Some users have faced similar problems and the above solutions have worked for them.
Here are the links to those discussions:
http://forums.ni.com/ni/board/message?board.id=170&message.id=67230&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&thread.id=229434&view=by_date_ascending&page=1
Regards,
Ujjval

Memory could not be read error.

I keep getting the following error while using Form Designer 7:
The instruction at "0x022221b2" referenced memory at "0x0000001c". The memory could not be "read".
It happens, randomly, when doing a number of things:
inserting a static text area
moving a form field
resizing a static form field....
In other words, no one thing seems to be causing it. If anyone has any ideas on this one it would be most helpful. Right now it is a pain in the butt since I keep losing information everytime it crashes.

Can't help with why but.... If Designer crashes you can recover the last PDF that you previewed by going to C:\Documents and Settings\<username>\Local Settings\Temp and finding the most recent pdf with a name such as _12bs10afg3a40f3t7j.pdf. That should be the last version you Previewed. Rich Ruiz Novanis

Backup discs could not be read error occurred (-50). HELP!

I'm using itunes 9.0.2; running Windows XP on Oracle Virtual Box in Ubuntu 10.04. the latest itunes will not work and 9.0.2 is the closest i can get.
One out of 4 backup discs contains only the itunes purchases and it works but a message pops up: +'could not restore some of the files from the play-list'+, +'they may be on other backup discs'+ even though all the songs on disc play. I put the next disc in and the following message pops up: +'the disc cannot be read. an unknown error occurred (-50)'.+
Any ideas why this is happening? I loaded the discs in the latest itunes on another PC and it is fine. would it be that I may be using an older itunes then when i backed up the other discs and so not compatible? is that possible??
Any help on how to get all my music back on would be great!!

Let's get you to SP 6 for CR XI r2:
https://smpdl.sap-ag.de/~sapidp/012002523100015859952009E/crxir2win_sp6.exe
Then I'd like you to see if you can duplicate the issue with one of our sample from here:
https://wiki.sdn.sap.com/wiki/display/BOBJ/CrystalReportsfor.NETSDK+Samples
vbnet_win_export.zip will probably be the best sample to use.
Ludek
Follow us on Twitter http://twitter.com/SAPCRNetSup

"Segment Version could not be read" Error in IDX2

Hi All,
I did one File-IDOC Scenario. But now there is a change in IDOC Structure. A extra segmetn is added. Now i reimported the definition in Design and made changes accordingly.
But while trying to import the idoc in IDX2 i m getting a error that segment version could not be found.
What might be the reason for this. Do i need to do any changes in the Channel Definition or Is it a Error in R/3 side?

Check if new segment is released in R/3 system ..
Go to transaction WE30 on R/3. Give your IDoc type..double click to new created segment>segment editor> there see if Released check box is check..
As you are saying new seg is reimported in IDoc then the segment must be released ..

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

Similar Messages

Maybe you are looking for