Disk writing failure

Since updating to iTunes 7, I have been getting this message:
What can I do? I have already restored everything once...
I got a black and white clickwheel iPod recently traded in through Applecare...
Thx

i had the exact problem as you. have you tried using a different usb port? these were the steps i took:
1) reset iPod.
2) restore iPod on my laptop iTunes (because it wasn't working on my g5).
3) then i kept trying to sync the iPod with iTunes on my g5 (because that was where my main music library was), but i kept getting the message: "The disk could not be read from or written to." i was using the usb port at the front of the g5.
4) then i tried a different usb port. the first one i tried was on a usb hub. i manually added a few songs to the iPod. IT WORKED! then i switched to another usb port on the back of the g5. IT WORKED there, too!
5) so i sync'ed the iPod to iTunes on the g5. a few times during the sync, i would receive that same message: "The disk could not be read from or written to."
6) so i would safely eject the iPod, then reconnect, and re-sync all over again until the iPod was completely updated. a little bit of a pain, but at least my iPod is functioning again (after being dead for a couple of weeks.)
hope this helps.

Similar Messages

Disk Boot Failure, Insert System Disk and Press Enter

I have been experiencing an intermittent disk boot failure for the last few months on my HP Pavilion Slimline PC. At first, it would occur once every week or two, typically when the computer would boot up after being in hibernation. After turning off the computer and turning it back on, everything worked normally. Within the last month, the failure began occurring with more regularity.
This week, I started receiving the error every time the computer would boot from hibernation. I went into the BIOS and saw that the system was not recognizing the hard drive. I tried changing the boot priority to boot from the HDD first, but to no avail. Today, the system worked as usual until I performed a restart, and it has yet to work again. Additionally, the performance has taken a nose dive over the last week (slow processing, programs not responding, etc.).
System Specs:
HP Pavilion Slimline s3710t PC
250 GB SATA Western Digital HDD (Caviar Blue)
Intel Pentium Dual-Core Processor
Windows Vista Home Premium (32-bit)
3GB DR2-800 MHz SDRAM
I have read through many technical forums, including HP’s, and followed all of the advice. I have again changed the boot priority to HDD first, restored the default settings, etc. The only drive I can find listed is the DVD drive on the unit, which is listed as the second drive. There is no first drive listed in the main tab of the BIOS CMOS Setup Utility.
I attempted to run a system recovery, but it is not even possible. Upon running the diagnostics, it of course mentions that there is no hard drive connected. Upon entering the boot menu, it also only lists the DVD drive.
My next course of action was to remove the side panel and reseat the connections on the hard drive, as well as the connection to the motherboard. This was also unsuccessful, and I have not been able to boot up the computer again today.
The computer itself is 1.5 years old and this is the original hard drive that shipped with it. I have never opened the computer, prior to today. The symptoms started a few months ago, just outside of the warranty period.
Based on the forums I have read, it all signs are pointing to a bad hard drive. This is hard for me to believe, as the computer is relatively new and does not get much use. The use it does get revolves around email and Internet access, as well as use of Microsoft Office.
As you can imagine, I am not happy about the prospect of having to buy a new hard drive, as well as pay for the data recovery on the original drive. I hope that someone at HP can come up with a better solution, as a 1-year life on a hard drive is pretty pathetic.
Thanks,
JR

HI JR,
You situation does not sound good if the PC doesn't recognize your hard drive.
Boot into the bios and run some bios hardware diagnostics.
Try clearing the CMOS.
Try this procedure:
Unplug the PC and open it up. Clean out all the dust. Carefully remove and replace all the cables going to the motherboard one at a time. Do the same for the memory dimms and the video and sound cards if you have any. You might want to buy a can of compressed air to blow the dust out of the CPU heat sink. Plug your PC back in and give it a go.
HP DV9700, t9300, Nvidia 8600, 4GB, Crucial C300 128GB SSD
HP Photosmart Premium C309G, HP Photosmart 6520
HP Touchpad, HP Chromebook 11
Custom i7-4770k,Z-87, 8GB, Vertex 3 SSD, Samsung EVO SSD, Corsair HX650,GTX 760
Custom i7-4790k,Z-97, 16GB, Vertex 3 SSD, Plextor M.2 SSD, Samsung EVO SSD, Corsair HX650, GTX 660TI
Windows 7/8 UEFI/Legacy mode, MBR/GPT

HP Pc 3010 Microtower VN 969EA - Hard Disk Reporting failure

The folloing hard disks reporting failure - Disk nameT3320418AS ATA Device volume C:\ D:\ E:\

Meshmesh -
Is this hard drive a Seagate ST3320418AS ??
320 Gbytes, Barracuda 7200.12 Serial ATA
http://www.seagate.com/staticfiles/support/disc/manuals/desktop/Barracuda%207200.12/100529369c.pdf
IF YES, then assure that the Data on this drive is backed up.
That should be your immediate step, backup/retrieve important files, photos or data,
IF the drive is still accessible.
This Seagate drive was released in 2008-2009 time period (5 to 6 years ago).
Seagate Desktop HDD (Barracuda Hard Drive) Product Page
http://www.seagate.com/support/internal-hard-drives/desktop-hard-drives/desktop-hdd/

XQuery is causing lots of disk writing

Hi,
In our system, we found that XQuery is causing lots of disk writing. I guess it is due to cache.
In dbxml document, it says:
All Berkeley DB XML applications are capable of writing temporary files to disk. This happens when the disk cache fills up and so BDB XML is forced to write overflow pages. For the most part, these temporary files can be safely ignored.
I don't understand what it says above.
My question is: Why Xquery operations will cause lots of disk write? (No other proocesses are writing bdb. )
Thanks.
-Yuan

Hi Yuan,
DB XML uses temporary Berkeley DB databases for a number of things during query evaluation, including re-sorting index entries and storing the parsed documents from a WholedocContainer format container. Berkeley DB will write this information out to disk if the cache becomes full. I would suggest that the behaviour you're seeing indicates that you need to allocate more cache for DB XML to work with.
John

Directory cannot be rebuilt due to Disk hardware failure (-36, 2286 )

Hello everybody,
my macbook was running slower and slower until it became unusable.
I have restarted the macbook with system DVD and run harddisk utilities from the DVD :
- First diagnostic : directory damaged, error on knot, cannot be repaired by this program.
I tried to put the disk in target mode but it was impossible to mount it on the desk.
-Then I tried with DiskWarrior utilities and got the message : Directory cannot be rebuilt due to Disk hardware failure (-36, 2286 )
Does anybody knows what it means ?
If disk has to be changed what brand would be the best suited.
Any advice on this issue will be more than welcome
Best regards from France
Jean Claude

*Many thanks* Templeton Peck for your help.
I am going to replace the disk but all the work of the last four days will be lost, kinf of hard to swallow on a machine bought a little more than a year ago !
Sweet home Chicago ! 41 years ago I heard Menphis Slim sing that tune in "Les trois maillets" a famous St. Germain des prés jazz club in Paris. Souvenirs, souvenirs…
Message was edited by: HotDna

Disk Boot Failure [solved]

I'm installing arch on a rebuilt system, but I cannot get it to boot. I have pared the system down to a a SCSI card, a video card, a single hard drive, an IDE CD, a SCSI tape drive, and a floppy. I have tried my standard installation partitioning scheme, and the automatic version.
No matter what I do, while the system seems to install correctly, when I reboot I get a Disk Boot Failure.
I've zeroed the drive, I've tried an fdisk /mbr, I've run a Maxtor burn-in test which came back fine. I'm convinced it isn't the drive. The standard menu.lst uses root (0,0) and the kernel in /dev/discs/disc0/part3 after an automatic installation. I mounted the /boot partition set up by the auto install, and the grub directory and files are there.
What am I missing?
Last edited by timm (2009-05-04 22:11:42)

I think it's solved.
Everybody who was mentioning the BIOS got me looking in there, but I found nothing out of the ordinary. I decided to try to install Windows 2K to see if that would boot, which it did flawlessly. I reinstalled arch, and go the disk failure. Back to the BIOS.
This is an IDE hard drive; the only thing SCSI is the tape drive.
What I found was that the access on the hard drive was set to Auto, which I had seen before but didn't think to be a problem. I tried changing that to LBA (which is what I thought Auto would do on a drive like this), and suddenly arch comes up just fine.
I have a couple of RocketRaid cards that I'm installing, and will be playing around with the SCSI as well. I'm going to play with things a bit more, but unless I can make it fail with some other tweaking, that BIOS setting appears to have been the problem.
Thanks to everyone for their help!

Problems with 1st Boot (media test failure, disk boot failure)

I have the K7N2G motherboard.
I hooked up everything in my system and on my first boot I get this error:
PXE-E61: Media Test Failure, check cable
PXE-M0F: Exiting NVIDIA Boot Agent
DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER
So, I figure I'll start from scratch and just start with the floppy drive, cpu, and ram hooked up and I get the same error. Here are my specs:
MSI K7N2G
Athlon 2400
Kingston PC3500 RAM
Volcano 7 Fan/Heatsink
Seagate Barracuda V SATA 80 GB
Verbatim CDRW 52/24/52
Any help or suggestions would be greatly appreciated.

This happens if:
- The hard drive is not installed
- An Operating System is not installed
- The BIOS cant detect the hard drive, maybe:
= The wrong jumpers are set on the hard-drive
= The cable is not polarised and pin 1 is on the wrong pin
- The hard-drive has not been set-up in the BIOS
Try something like the above

DISK BOOT FAILURE: PLEASE INSERT SYSTEM DISK....

Hi
I have exhausted two full days on the following problem so I would greatly appreciate some help. The problem I am experiencing is that the disk will not boot on its own. I receive the "DISK BOOT FAILURE: PLEASE INSERT SYSTEM DISK...." error when starting up. I have run chkdsk, i have run Western Digital Diagnostics for Dos (quick test) and no problems come up with the drive. I have also jumpered pins 5 and 6 to force the drive to run at SATA-I speeds. Now here's the curious part: The disk boots up and functions absolutely perfectly IF and ONLY IF, the bios is set to boot from my IDE drive. Now on the IDE drive I have a boot.ini file set up to allow me to boot the SATA drive instead. Using this work around (i.e. boot from IDE, select SATA drive from boot menu) the drive seems to work just fine. However if i change the bios back to boot from the SATA drive (and therefore use its own boot.ini) I receive the error again and the boot will not continue.
Here is my set up:
MSI K8T Neo2-F v2.0 motherboard (with latest BIOS).
Athlon 64 X2 4200+ dual core CPU
1024GB DDR 400 RAM
1 Western Digital 120GB IDE HD running on primary master.
1 Pioneer DVD-108 DVD-RW running on secondary master.
1 Western Digital 250GB (WD2500KS) running on SATA1.
Nividia GeForce 6800 running on AGP.
M-Audio Audiophile 2496 PCI
Sound Blaster Audigy 2 ZS PCI
Originally the system was as above without the new WD2500KS drive. I then bought the new SATA drive and installed windows to it with the intention of clearing windows from the original IDE and making it a storage drive. The above workaround is how I completed installation of Windows XP and installed my other programs, otherwise when rebooting during installation the disk would fail again.
Another issue is that Windows will NOT designate the SATA as drive C. When disconnecting the IDE, the SATA will become "c:" but as soon as the IDE is plugged back in, it immediately claims "c:" again and the SATA becomes "d:". This is ascertained from running the Recovery Console and using 'map' for example. It is important that I get this to "c:" as I have programs which appear to look for files by an absolute path and will not find them on "d:".
I have also tried to 'fixmbr' and this is the only time I have seen any curious message. Using the workaround the disk works fine. But when I tried to 'fixmbr', the system warned that the disk had a non-standard boot record (or something to that effect). But in any case, boot seems fine so long as we're not booting it directly.
Finally, I should confirm that the BIOS is set to run the SATA in IDE mode and not SATA (although as a sanity check I have run it in RAID and the result is the same).
I have no idea at this stage whether the problem lies with the SATA drive or the motherboard. I have sent a copy of this to WD "for further troubleshooting", and am posting a copy here for any advice on the mobo side of things.
Many thanks

Thank you for your reply. You are right, I've just resolved the problem today and discovered that this was the case.
To close the topic and leave advice for anyone else facing similar difficulties I will sum up the progress since the initial post.
Having tried absolutely everything else, I thought "what happens if i make this sata c:?" so I decided to edit the registry and force a drive letter change to ensure that my SATA was "c:". After having done this the SATA for the first time successfully booted to the boot menu! However when loading up into Windows it kept hanging. So next I thought all I need to do is a repair install now, I disconnected the IDE to leave the SATA only and attempted this. Unfortunatley the repair install also kept hanging. The Microsoft support page detailing how to force the drive letter change does warn that doing so can mess everything up unless the problem occurred in some specific circumstances.
So a new install was in order. I hooked up the IDE again and booted from it, backed up all my files to the IDE, and then disconnected it again. Then booted from a Western Digital diagnostics disk and zero filled the SATA - this was more for my own sanity so as not to worry about dodgy MBR's and what not. Then booted from WINXP CD and formatted and reinstalled fresh.
Install was successful.
Hooked up IDE externally to dump back my backed up files. Then deleted the IDE's partition and formatted it. Powered down, connected the IDE internally again - booted from SATA successfully (now on c:)... the IDE was no longer recognised as a "system" disk in Disk Manager, so I gave it a drive letter and hey presto we're business again!! One SATA system disk on drive c: and one IDE storage drive!
SHORT VERSION: If you are adding an SATA drive to an IDE set up, and want the SATA to be your OS disk, unhook all the IDE's first... if the target drive is not in isolation when installing Windows, all kinds of problems can ensue which are very difficult to correct after the install.

MSI 975x disk boot failure

I have been having a problem lately with a 975x having disk boot failure once in a while. The system has 2 drives and a dvd writer. It's about 2.5 years old also. When this happens it doesn't see any drives. I've cleaned the filters, fans etc and sometimes during this it'll start working. Once it finds the drive it boots just fine and works fine. I don't think it's a drive as it can't find any of them.
This happens intermittently, and there is no pattern to what gets it working again. The case is well ventilated. I have 4 gig DDR2, the drives are SATA, core 2 duo 2.13 ghz.
I'm thinking the mother board is starting to go bad on me.
Does anyone have any other ideas?
Also if I change the board what is a good one in the newer models so I won't have to change a lot of other hardware?
I've not kept current on the advances in mother boards the last few years

Well I spoke too soon.
It did it again today. It started with a not responding message and on reboot it did not detect any drives the first time. In the bios it said none in all positions also. After Another reboot it identified the WD drive but not the Seagate drive. After sitting about 2 hours I rebooted with the Seagate drive unplugged and it came up just fine. I then put in 2 more drives and plugged in the Seagate drive and it worked just fine.
Any other ideas?
Do you think my suspecting a flaky MB is wrong?
Also whats a good MB for the hardware I have?

Disk SMART Failure

Basic question I'm sure, but want to get it right the first time. I've done my searching and still not clear on the procedure to replace a failed adm in our Xserve RAID. I have a RAID5 setup (upper controller) with (4) 250GB adm's (approx. 20,000 hours each) and (1) 250GB adm as a hot spare. The drives are in position 1 through 4, with the hot spare in position 7. Drive 2 is throwing a SMART failure and making an annoying high pitched whine, so I'd like to proactively replace it prior to failure. I have an extra 250GB adm ready to install, have backed up the data, so how to proceed? Is it as easy as pulling drive 2 and inserting the new adm? Thanks in advance for any advise / experience / reassurances
BPR
RAID admin 1.5 / Firmware 1.5 /1.50f

Yes - just pull the failed/failing drive. Since you
have a hot spare in the chassis, the XServe RAID will
imediately begin rebuilding the array using this
spare.
Hi,
I've a similar issue with a RAID 5 array: the Xserve RAID notified me by email of a disk SMART failure.
In the RAID Admin, the status for that disk is "Warning" (orange).
I also have a spare disk in the array, its status is "OK" (green).
Will the Xserve RAID automatically "replace" the failed drive to the spare one?
If so, how can I check if it's already rebuilding the array in the background?
Thanks.

Disk write failure

when i go to update the song on my ipod it does 2 or 3 then says disk write failure disk could not be read or written to
does anyone know whats going on

http://docs.info.apple.com/article.html?artnum=301267
When you sync your iPod with iTunes, iTunes may display an error message that reads:
"Attempting to copy to the disk <iPod name> failed. The disk could not be read from or written to."
When you update or restore your iPod, you may see this error:
"Firmware update failure. Disk write error."
These errors can happen with any iPod.
These errors can occur anytime iTunes can't read information from or write information to the iPod. Here are some things that can cause this.
Outdated operating system software
Make sure you have the latest updates for your operating system, which may include improvements for device connections. For example, many USB and FireWire improvements have been included in Windows Service Packs.
Computer needs updates
Make sure you have the latest updates available for your specific computer model (or components for home-built PCs). These are usually available for download on the support website for the maker of the PC (or component). Many USB updates are listed as "Intel chipset" or just "chipset" updates on PC manufacturer's support and download websites.
Software interference
Some software can interfere with iTunes, making it unable to write files to your iPod. For example, antivirus software that scans all files on connected disks can cause one of these errors. Think about what software you have installed, and try disabling any add-ons that might be interfering with iTunes. Check your suspected software's documentation or contact the software maker if you need assistance with disabling the application.
Damaged files
If one of your music files or photos is damaged, iTunes may display one of these errors when transferring that file to the iPod. If you identify a file that is causing the error, try deleting that file and reimporting it from a backup file or from the original source. You may be able to repair files by repairing the disk (see the solutions in the next section).
Damaged disk structure
These errors can also appear if the format of your computer's hard drive or your iPod disk is damaged.
Windows users, search the Help system in Windows for chkdsk to get more information on checking and repairing the disk structure.
To repair an iPod disk—Restore the iPod or iPod shuffle using the latest version of iPod Updater. Warning: Be sure to back up your data before restoring an iPod. The restore process cannot be undone. All of your songs and files will be deleted.
Corrupt iPod photo Cache
If you're getting the error when transferring photos to an iPod photo, try deleting the iPod photo Cache and then starting the photo sync again.
Lost connection
Make sure that the connections from your computer to the iPod are snug and do not wiggle or come loose during transfers. For example, if you use the wrong size dock for your iPod, it can put strain on the connectors and cause a bad connection.
Hardware failure or non-compliant hardware can cause these errors. This could be an issue with iPod hardware or with the cable or dock you're using, but more often it's an issue with the USB or FireWire card or interface in your computer. Some USB and FireWire interfaces just don't work very well. If you isolate the issue to the USB or FireWire interface in your computer, you may want to try a different port, get the computer serviced, or replace the card or interface with a better one.

K8N Neo4 - Disk Boot Failure, Insert System Disk

Hello !
Up an runnung with my new MoBo - for details se below, thats good. But...
No matter how I change my BIOS settings, at startup I got the same message:
Boot from CD : Disk boot failure, insert system disk and press enter
When doing so, the PC is booting OK.
Quit annoying, so glad for any hint !
Greetings / Jan Björk

Thanks TheBigMan for your welcome message !
Glad the join the Forum, it´s great knowledgebase !
I´ve gone through the BIOS settings you are referring to. They are like this: (And have been so all the time)
1:st Boot device [Harddisk]
Hard Disk Priority [SCSI:0 Nvidia Mirror 115.03G]
So there must be something else, thanks anyhow !
I also wonder from where this message, "Boot from CD..etc", is coming, is it really from the BIOS ?
Greetings / Jan Björk

HP Pavillion g6 hard disk test failure

Hi!
My HP laptop stopped working, I cannot get into windows but can reach the diagnostics tests at the startup sequence.
The following was reporeted on a Quick Hard disk test:
Smart Check: PASSED
Short DSN: FAILED
FAILURE ID: 9U0AJM-63570E-MFPX0J-60WH03
PROD ID: B1J44EA#UUW
Hard disk 1
Hard disk test: FAILED
I'm guessing I need to replace the hard drive ?
Regards,
BigRedMachine
This question was solved.
View Solution.

Hi,
Unfortunately it does look like you'll need to replace the HDD - the error code for the short Disk Self Test ( DST ) would indicate that the Hard Drive is failing and needs to be replaced.
The HDD is a warranty item, so if your notebook is still under warranty, contact HP ( with the 24 character error code ) and arrange to have the drive replaced - you can check your warranty status Here.
If you live in the US, contact HP Here.
If you are in another part of the world, start Here.
If you are out of warranty and would like a guide on replacing the Hard Drive yourself, please let me know.
Regards,
DP-K
****Click the White thumb to say thanks****
****Please mark Accept As Solution if it solves your problem****
****I don't work for HP****
Microsoft MVP - Windows Experience

Disk Repair Failure

I have an imac G4 15" Flat Panel 800 MGhz and I have been told that my hard drive went bad so i am about to install a new one. I probably should anyway, the upgrade will be nice. I hope. Anyway, I am trying to learn all I can from this experience so I have another question.
I was getting a grey screen with a folder icon with a flashing question mark on it so I did a disk repair and got this error message "Disk Utility stopped repairing "Untitled 1" because the following error was encountered: The underlying task reported failure on exit.
I then restarted the computer with my OSX Install Disk inserted and held down the shift key and the screen had the following on it:
panic (cpu 0 caller 0X002DFC88): Unable to find driver for this platform: PowerMac4,2".
No debugger configured - dumping debug information
MSR =00001030
Latest stack backtrace for CPU0
Backtrace:
0X00095698 0X00095D98 0X0002683C 0X002DFC88 0X002BF014
0X002BEDDC 0X002BF844 0X002BFEB0 0X000A9814
Proceeding back via exception chain:
Exception state (SU =0X00525A00)
PC =0X00000000; MSR =0X0000D030;
DAR =0X00000000; DISIR =0X00000000;
LR =0X00000000; R1 =0X00000000; XCP =0X00000000 (unknown)
Kernal Version:
Darwin Kernal Version 8.3.0: Mon Oct. 3 20:04:04 PDT 2005;
root: XNU- 792.6.22. obj~2/Release_PPC
Panic: We are hanging here...
After this happened I connected a imac G3 to my imac G4 with a Fire Wire Cable hoping to target my files and recover them. Then this message came up:
Inserted a disk containing no volumes that OSX can read.
So what does this mean?
If my Hard Drive is ruined can I recover my files?
I know there are some geniuses out there so I will await your reply.
Thank you
Ovation
imac g4 flat panel Mac OS X (10.4.7)
imac g4 flat panel Mac OS X (10.4.7)
imac g4 flat panel Mac OS X (10.4.7)

First, check your SMART status of the drive with Disk Utility. If SMART is not verified, you should get another drive before you start loosing data.
When I got similar disk and 'underlying task' errors, I re-formatted the drive and that removed the errors.
I backed up my data to an external firewire drive of the same capacity by booting my PB off my Tiger install CD (the 10.3 should work too) with the firewire drive attached.
Select Disk Utility from one of the menus after you booted off the CD. In Disk Utility, select the Restore tab. Drag your internal PB drive into the source field, and drag your FW drive as the dest field. You will want to erase the destination. Just be careful to get the source and dest disks straight! Click restore and your PB HD will be copied over to your external. You might want to boot from your external to make sure it comes up and looks like it would from the internal drive.
Once this is complete, use Disk Utility to erase your internal drive. Verify your disk to make sure all the problems are gone.
Then run Restore again, this time using your external drive as the source, and the internal as the destination. When restore is complete, your PB will be bootable with all your stuff. Plus, you just made a full backup on your external drive!

Redo log files lost in Disk Corruption/failure

DB version:10gR2
In one of our test databases, I have lost all members of a group due to disk corruption(it was a bad practise to store both members on the same filesystem)
Database is still up. We don't have a backup of the lost redo log group. Altogether we had 3 redo log groups. this is what i am going to do to fix this issue.
Step 1. Add a redo log group
ALTER DATABASE
ADD LOGFILE ('/u04/oradata/ora67tst/log4a.rdo',
   '/u05/oradata/ora67tst/log4b.rdo') SIZE 15m;Step 2. Drop the corrupted redo log group
ALTER DATABASE DROP LOGFILE GROUP 2;Is this the right way to go about fixing this issue?
The documentation says that you need to make sure a redo log group is archived before you DROP it.
When i use the query
SQL>SELECT GROUP#, ARCHIVED, STATUS FROM V$LOG;
    GROUP# ARC STATUS
         1 YES ACTIVE
         2 NO CURRENT
         3 NO INACTIVE
How can i force the archiving of a redo log group 2?
Edited by: Citizen_2 on May 28, 2009 10:10 AM
Edited by: Citizen_2 on May 28, 2009 10:11 AM

Citizen_2 wrote:
How can i force the archiving of a redo log group 2?How could you archive a log group when you have lost all members of that group?
Have you checked out this documentation: [Recovering After the Loss of Online Redo Log Files|file://///castle/1862/Home%20Directories/Vaillancourt/Oracle%2010gR2%20Doc/backup.102/b14191/recoscen008.htm#sthref1872]
More specifically:
If the group is . . .      Current
Then . . .
It is the log that the database is currently writing to.
And you should . . .
Attempt to clear the log; if impossible, then you must restore a backup and perform incomplete recovery up to the most recent available redo log.
>
HTH!

Disk writing failure

Similar Messages

Maybe you are looking for