WRITE SAME failed messages on RAIDs

Hi all,
Since the last kernel upgrade on an headless server
[2013-04-04 09:56] upgraded linux (3.8.4-1 -> 3.8.5-1)
I get loads of these errors:
3w-xxxx: scsi2: Unknown scsi opcode: 0x41
[ 4356.826902] sd 2:0:0:0: [sda] Unhandled error code
[ 4356.826905] sd 2:0:0:0: [sda]
[ 4356.826907] Result: hostbyte=0x04 driverbyte=0x00
[ 4356.826909] sd 2:0:0:0: [sda] CDB:
[ 4356.826911] cdb[0]=0x41: 41 00 00 93 28 ee 00 00 08 00
[ 4356.826919] end_request: I/O error, dev sda, sector 9644270
[ 4356.827002] sda3: WRITE SAME failed. Manually zeroing.
sda3 is an ext4 / partition, on a 3ware hardware controller (RAID1). The awful tw_cli tool says it's everything ok:
Unit UnitType Status %RCmpl %V/I/M Stripe Size(GB) Cache AVrfy
u0 RAID-1 OK - - - 69.2482 ON -
Port Status Unit Size Blocks Serial
p0 OK u0 69.25 GB 145226112 WD-WMANS1886705
p1 OK u0 69.25 GB 145226112 WD-WMANS1886623
I did not find relevant clues by googling.
Do any of you guys know whether this issue is harmful or can be ignored? Since otherwise everything seems fine...
Cheers,
domanov
code tags as opposed to quote tags please -- Inxsible
Last edited by Inxsible (2013-04-09 16:49:22)

alphaniner wrote:
Apparently, WRITE SAME is an optional drive feature that allows writing the same data to consecutive sectors of the drive. A search for "WRITE SAME 3ware" turned up an offsite (ie. not hosted by 3ware) 3ware manual that suggests it's only or primarily used during RAID initialization to speed things up.
WRITE SAME seems to be part of the "SMART Command Transport" feature set, so a good first step would be to make sure SMART is enabled on your drives.
Thanks alphaniner for pointing me there. This is the output of smartctl on one of the two disks in RAID1 (the other gave no error whatsoever):
[root@server ~]# smartctl --all -T permissive --device=3ware,0 /dev/twe0
smartctl 6.1 2013-03-16 r3800 [x86_64-linux-3.8.6-1-ARCH] (local build)
Copyright (C) 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Raptor
Device Model: WDC WD740ADFD-00NLR5
Serial Number: WD-WMANS1886705
Firmware Version: 21.07QR5
User Capacity: 74,355,769,344 bytes [74.3 GB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: ATA/ATAPI-7 published, ANSI INCITS 397-2005
Local Time is: Wed Apr 10 10:59:26 2013 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 2391) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 39) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x103f) SCT Status supported.
SCT Error Recovery Control supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000b 200 196 051 Pre-fail Always - 1
3 Spin_Up_Time 0x0007 169 169 021 Pre-fail Always - 2566
4 Start_Stop_Count 0x0032 100 100 040 Old_age Always - 67
5 Reallocated_Sector_Ct 0x0033 199 199 140 Pre-fail Always - 13
7 Seek_Error_Rate 0x000a 200 200 051 Old_age Always - 0
9 Power_On_Hours 0x0032 045 045 000 Old_age Always - 40164
10 Spin_Retry_Count 0x0012 100 253 051 Old_age Always - 0
11 Calibration_Retry_Count 0x0012 100 253 051 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 62
194 Temperature_Celsius 0x0022 116 106 000 Old_age Always - 27
196 Reallocated_Event_Count 0x0032 187 187 000 Old_age Always - 13
197 Current_Pending_Sector 0x0012 191 188 000 Old_age Always - 113
198 Offline_Uncorrectable 0x0012 200 197 000 Old_age Always - 3
199 UDMA_CRC_Error_Count 0x000a 200 253 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 198 193 051 Old_age Offline - 60
SMART Error Log Version: 1
ATA Error Count: 24 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 24 occurred at disk power-on lifetime: 40148 hours (1672 days + 20 hours)
When the command that caused the error occurred, the device was doing SMART Offline or Self-test.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
40 51 40 df 87 c3 e0 Error: UNC 64 sectors at LBA = 0x00c387df = 12814303
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
25 00 40 c0 87 c3 41 00 2d+04:24:43.728 READ DMA EXT
25 00 40 80 87 c3 41 00 2d+04:24:43.728 READ DMA EXT
25 00 40 40 87 c3 41 00 2d+04:24:43.728 READ DMA EXT
25 00 40 00 87 c3 41 00 2d+04:24:43.728 READ DMA EXT
25 00 40 c0 86 c3 41 00 2d+04:24:43.728 READ DMA EXT
Error 23 occurred at disk power-on lifetime: 40148 hours (1672 days + 20 hours)
All the five errors in the smart log are "only" UNC errors on read: if I understand correctly, googling around, this could be a bad cable connection rather than drive really failing (a couple days ago someone worked on the rack where this server is hosted...).
Anyway, the other drive seems fine and since this 2-disks raid1 unit is just the / partition (it's a plain arch installation, the server is a "number cruncher"; all actual data are in a separate 4-disks raid5 unit) I just backuped /etc for excess of zeal.
For now I think I'll wait for the weekend for running long smart tests/badblocks and such.
Any further hint or comment is still appreciated! Do you think it's time to replace the drive?
Thanks,
domanov

Similar Messages

  • "Write SAME failed" on VMWare 10

    Hello,
    I was trying to install Arch Linux on a VMWare 10 virtual machine but when I mounted the root partition (ext4) it printed: "Write SAME failed".
    How can I solve this problem?
    Thanks
    Dennis

    Have you searched the forums? A quick search gave me these:
    https://bbs.archlinux.org/viewtopic.php?id=164377
    https://bbs.archlinux.org/viewtopic.php?pid=1297289

  • "WRITE SAME failed. Manually zeroing." error during install or boot

    Hello everyone!
    Since the lasts kernels (I'm almost sure it happens since 3.9 because 3.8 worked fine) I can't boot on Archlinux anymore. This error floods my screen and I can't do anything, and because the new Archlinux iso (june 2013) comes with 3.9 kernel it now also happens during installation. Fortunately, I saved the may iso so I still can install archlinux and switch during install to LTS kernel but this is not a good solution. I can't find a solution online, some people have this issue but it seems to be a bit different everytime.
    I use Archlinux on a server, with hardware raid : Dell PERC H200a with LSI SAS2008 according to my BIOS. According to http://kernelnewbies.org/Linux_3.7, the WRITE SAME SCSI command "allows the same block to be efficiently replicated throughout a block range. Only a single logical block is transferred from the host and the storage device writes the same data to all blocks described by the I/O (commit)". Here is the exact configuration :
    - DELL® PowerEdge R210 II
    - 1x Intel® Xeon® E3 1220 V2
    - HDD: 2 x 1 To SATA2 RAID
    - RAID: Hardware, Dell PERC H200, (Raid 1)
    So my first problem is that I can't find online if my server is capable of this command (but I don't think so) and then the other issue is that I want to know if I can disable it. I found kernel patches for this issue :
    https://patchwork.kernel.org/patch/1898441/ and https://patchwork.kernel.org/patch/1982051/ (the first link seems to be a better solution).
    Then, I checked in the kernel source of 3.9 and I think that this patch isn't implemented (there is no device_write_same_capable function for instance). But kernel patching is not a really good solution, if I have to patch my kernel everytime the main kernel is updated...
    After some research, I found that my hardware RAID driver seems (I'm not sure) to be the kernel module "mpt2sas", so I checked both may and june isos of Archlinux and it's the same version (14.1) so it shouldn't be the problem.
    Does somebody can help me on this issue ? I don't really know what to do now.
    Thanks for reading, if I forgot something or if you want more informations, ask me!
    Bye.
    PS : My English isn't very good, sorry.
    EDIT : I found a part of the solution ! It seems to be an issue with the kernel that doesn't detect properly if my disc is capable of doing WRITE SAME command.
    So I have to write "0" in the file "max_write_same_blocks" under /sys. But the problem is that /sys is renewed every boot so I don't know how to make my changes permanent. I made a systemd service file, it almost works, but this solution isn't nice : the parameter is applied lately so errors shows at the beginning and this is not really easy to set up. I prefer a solution like "sysctl" but it seems that it only controls parameter under /proc/sys and not /sys, am I right ?
    Moreover, I tried two other things : Ubuntu 12.04 with kernel 3.9.4 works and Archlinux iso with 3.8.10 has max_write_same_blocks > 0 and it also works... So I don't really understand this issue. Maybe in 3.8 the parameter max_write_same_blocks has no effect (or not the same as in 3.9) ?
    Here is the systemd file that I made to reduce the issue :
    [Unit]
    Description=No WRITE SAME
    After=local-fs.target
    [Service]
    Type=oneshot
    ExecStart=/bin/sh -c 'echo 0 > /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:1:0/0:1:0:0/scsi_disk/0:1:0:0/max_write_same_blocks'
    RemainAfterExit=no
    [Install]
    WantedBy=multi-user.target
    This is not a good solution, see my next post. I don't delete it in case you want to compare.
    Last edited by rfnx (2013-06-02 15:26:50)

    I found a solution to disable the WRITE SAME command. That doesn't answer all my questions but it solves my issue. I was looking for a file like "sysctl.conf" but for /sys parameters : you already can do that in Arch, just create a file that ends with ".conf" in tmpfiles.d and add one line per parameter you want to modify. This file will be loaded early at boot.
    To disable it in an existing Archlinux installation, add in you file the line :
    w /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/host0/target0:1:0/0:1:0:0/scsi_disk/0:1:0:0/max_write_same_blocks - - - - 0
    Read the manpage of tmpfiles.d if you don't understand this line, it depends on your configuration and you can't copy it.
    Then reboot and no more error !
    If you want to disable it during the Arch install, just change directly the value you want in /sys. You have to do it at the beginning before mounting partitions, for instance just after choosing your keymap.
    Bye.
    Last edited by rfnx (2013-06-02 15:34:11)

  • Questions about "WRITE SAME failed. Manually zeroing."

    Hi fellows,
    I've already read this old thread https://bbs.archlinux.org/viewtopic.php?id=164377
    but I have further questions:
    ok, WRITE SAME feature should enhances performance on supported hardware.
    But when I get this error, I must manually ZEROING the parameter to disable it or the parameter is already ZEROED, since it failed?
    and a second question:
    I get this error on an USB device. In the aforementioned thread this error appears with SATA.
    How can I disable permanently on an USB device, since address depends on the USB port which change?
    thank you
    Last edited by nTia89 (2015-01-06 09:59:31)

    I have the same problem with kernel 3.19 (was not happening before) booting Archlinux from USB stick (Ventura ultra).
    Plasma 5 start is now very slow. If I boot from another kernel (linux-rt) all is fine as it was before kernel 3.19 installation.
    It seems to me that also X starting is too slow before  sddm login screen.
    Using nvidia 340xx drivers (updated).
    Some suggestions?
    Last edited by hifi25nl (2015-03-19 13:30:34)

  • Backup failed message

    I connected my La Cie external hard drive to my laptop, as I had done several times before, opened Time Machine and got a "Disc Repir" message that said :
    "The disk is not repairable by this computer ,it is being made available to you with limited functionality. You must back up your data and reformat the disc as soon as possible."
    On the Time Machine window I got a " Backup Failed " message, and info that the next backup would be tried an hour later later.
    When later came I got the same " failed " message and again the info that a backup would be tried in an hour.
    What is the effect of that message, and how should I deal with it ? I don't entirely understand it.

    In Disk Utility the top icon for each disk shows the name that the system reads from the hardware manufacturer. The hardware icon for your Time Machine volume should have "LaCie" included in its name. The indented icons represent the partition(s) on the disk which are also what you see on your desktop in the finder. The indented icon below the LaCie icon should be Time Machine Backups.
    I assumed from your post, perhaps wrongly, that you had been using this drive before and it had data on it that you wished to retain. If you do have data on the drive you wish to save you should try to fix it with DiskWarrior or TechTools Pro. If the drive can't be repaired you need to use something like FileSalvage or Date Rescue to try to recover the files.
    However, if you want to erase everything on the drive and format it for Time Machine click on the indented icon beneath the Hitachi icon. It should have the name of your internal hard drive. See if it says Apple Extended (Journaled) or Apple Extended (Case-sensitive, Journaled) at the bottom of the Disk Utility window.
    Then click on the upper icon for your Time Machine drive which should have "LaCie" included in its name. Then follow the directions for formatting your disk using the "this article" link I posted upthread. However, you should substitute Apple Extended (Case-sensitive, Journaled) for Apple Extended (Journaled) if that is the way your internal hard drive (the Hitachi) is formatted.
    Also, you should use only one partition if you just plan to use your drive for Time Machine backups. That will let you go back the farthest amount in time for your backups. However, if you have a very large external drive and want to use part of it for storage you can use two partitions. If you use partition #1 for Time Machine backups Leopard will allow you to reclaim the space from partition #2 at a later time. That won't affect your Time Machine backups but will erase all the data from partition #2.
    If there is something that you don't understand post back.

  • Mds: (Warning) DiskStore: Failed messaging flag writer

    I reinstalled Mavericks and imported my user from a Time Machine backup from another Mavericks system.
    I noticed the following lines:
    07/12/13 02:40:19,160 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:40:29,149 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:40:39,164 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:40:49,164 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:40:59,159 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:41:08,966 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:41:19,199 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:41:28,484 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:41:37,990 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:41:49,148 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:41:58,964 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:42:09,151 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:42:19,155 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:42:28,963 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:42:38,960 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:42:49,151 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:42:59,151 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:43:09,125 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:43:19,036 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:43:29,152 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:43:39,161 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:43:49,154 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:43:59,154 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:44:09,155 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:44:19,150 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:44:29,154 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:44:39,153 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:44:49,137 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:44:59,138 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:45:08,954 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:45:19,153 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:45:29,150 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:45:39,096 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:45:49,137 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:45:58,955 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:46:09,155 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    07/12/13 02:46:19,137 mds[92]: (Warning) DiskStore: Failed messaging flag writer
    As you can see this repeats every 10 seconds.
    What might be causing this?

    Unfortunately I don't have any idea, but I have exactly the same problem.  I also had a broken Mavericks backup which required OS reinstall and file recovery via a rather manual method.
    Please, anyone out there, any ideas on how to cure the problem?

  • HT1926 reinstalled itunes after unistalling it due to error message during update. after it was completly unistalled still has the same error message: service "apple mobile device" (apple mobile device) failed to start, verify you have sufficient priviled

    I was prompted to update itunes this evening. I did and in the process, it came up with the following error message: Service "apple mobile device" (apple mobile device) failed to start. Verify you have sufficient priviledges to start system services. I unistalled itunes completly and reinstalled but am still getting the same error message. If I click "ignore" the program will finish downloading but will not launch due to "not being installed correctly". Please help, I use this program alot with my first grade classroom and they're expecting their listening center in the morning.

    Hey I finally got an older vesion of itunes to work!!! 10.7  x64 for windows 7
    After uninstalling all apple products even  quicktime
    I had to delete everything from (program files, and program  files x64, program data,)
    And all downloads from apple, and I went in to search deleted  other stuff from apple, and itunes
    But definently not my itunes library and Playlist
    Down loaded 10.7 x64 for windows 7, but checked (do not start  when done)
    Then I emptied my recycling bin and restarted my  PC
    I ran geek tech tool box same as reg cure pro, also PC Tools  registry cleaner, and CC Cleaner
    Then I emptied my recycling bin and restarted my  PC
    And wallah... It finally works, and I Love the older version  anyways.
    Easier to download and transfer  music!!!!!

  • I cannot run itunes, I keep getting this error message" Quick Time failed to initialized (error02096) Quick time is required to run please unistall itunes then install itunes again, I have done this three time and I keep getting the same error message.

    On my PC, I cannot run itunes, I keep getting this error message" Quick Time failed to initialized (error02096) Quick time is required to run please unistall itunes then install itunes again, I have done this three times and I keep getting the same error message. I have had itunes for years, but up until 2 months ago the quick time will not initialize to run it.

    Try using the Windows Installer Cleanup Utility and delete the iTunes installer. Then try installing iTunes again
    http://majorgeeks.com/Windows_Installer_CleanUp_Utility_d4459.html

  • Im trying to install Photoshop Elements premier 12 on my new Mac with the latest update and i keep getting the same failed to initialise message.

    Im trying to install Photoshop Elements premier 12 on my new Mac with the latest update and i keep getting the same failed to initialise message. I was able to register the key code at first but now im not able to either open the program or reinstall it.

    What is "Photoshop Elements Premier 12"? Do you mean Photoshop Elements or Premiere Elements? Were your files copied over from a previous mac that had PSE installed on it?

  • Icannot authorize my tablet. the message is always the same "fail to authorized device"

    I am not able to authorize my tablet. the message is always the same"failed to authorize device" I have an Adobe Id and a password. with the same Id and passaword it was easy to authorize the computer. How can I do?

    The details will depend on which app you are using on the tablet for reading DRM ebooks.
    Bluefire is free and generally pretty reliable, and works on Android and ios.
    Several people have reported problems trying to get the Overdrive app to authorize.

  • Windows Delayed Write Failed Message

    Okay, I've had my iPod classic 80GB working perfectly until a couple days ago, when I plugged it in. iTunes froze up, and wouldn't start back up, until a message came from the bottom right service bar saying "Windows- Delayed Write Failed Message, failed to write to G:/iPod_Control, all data erased, hardware" or something of the sort. Naturally, I assumed the worst, went to My Computer, and formatted the iPod, went back to iTunes, it recognized the iPod, however, it refuses to sync anything, bringing the Windows Delayed Write Fail message in the corner, and then it doesn't recognize the iPod. I've formatted, restored, reset the iPod several times now, and this is really getting frustrating. I even did the hard drive check (My Computer, the one that goes in phases or something), and still nothing. Please help! This is really getting frustrating. Thanks!

    *Disable write-behind caching*
    Right-click on your iPod in *My Computer* and select Properties and then the tab that says Hardware. Highlight the selection that says *Apple iPod USB Device* and select Properties. Under the tab that says Policies make sure that *Optimize for quick removal* is checked.
    Alternatively this registry hack appears to let you disable write-behind caching across the entire file system.
    When restoring an iPod it may also pay to use this method to put the data back on in stages.
    *Break up large transfers*
    In iTunes select the menu item *File... New Smart Playlist*. Change the first drop-down box to Playlist, the next to is and the next to Music. Tick against *Limit to*, type in say 10, then change the drop-down to GB, and set the last drop-down to artist. When you click OK you can enter a name for the playlist, e.g. Transfer. Now sync this playlist to your iPod rather than your entire library. When the sync is complete modify the rule ( *File... Edit playlist* ) to increase the size by your chosen amount, then sync and repeat. You can experiment with different size increments, if it doesn't work just choose something a bit smaller until it works each time. Before long you should have all your music on your iPod. Once that's done you can move on to other media such as podcasts, videos, photos, playlists etc.
    tt2

  • "Delayed Write Failed" message

    Hi.  I am new to this forum, so please forgive me if this has already been discussed.
    I have an X61 Lenovo Thinkpad.  I have an external drive that is connected via USB cable.
    My laptop is only a month old.  I have had no problems with it until now. 
    I cannot use my external drive now because the laptop doesn't recognize it. 
    When I do plug it in, it takes a while for it to boot up.  Minutes, actually.
    I did get a "Delayed Write Failed" message a couple of days ago. 
    The window said, "Dealyed Write Failed.  Windows was unable to save all the data for the file E:\System Volume Information."
    Can someone please help me?  I would like to have my external drive connected to my laptop.
    Thank you!

    Please, someone help me.  I really would like to solve this problem.  I am unable to use my external drive, which I really need to use right now.
    I did call Support, but he just told me to download all the Microsoft updates, all the Windoes updates, all of the ThinkVantage updates, all the Lenovo updates. 
    I am not sure if I should do that.  I bought my computer directly from Lenovo last month, so shouldn't it already be updated?  If not, how do I know what to update?
    If someone has a help line or a support line, I would love to call it for help.
    The problem is my laptop will not recognize my external drive anymore.  If I unplug the external drive, it works fine, but I cannot access my external drive.
    Everything else works; my wireless keyboard and mouse, my security software key, my USB foot pedal.  Everything expect for the external drive.
    I have a feeling that it is because of that "Delayed Write Failed" mesage, saying Windows was unable to save all the data for the file e:\System Volume Information.
    *** My external drive does work on my other laptop, so that's why I think it's something with this X61 Lenovo Thinkpad.
    PLEASE help.  Thank you!

  • Message from RAID utility "Battery failed (code0x#0 = 18)

    Just received message from RAID utility "(code0x#0 = 18)". This is not the first time. I had to bring my Mac Pro in about three months ago for the same issue to have the battery replaced. Wasn't expecting to have to do it again anytime soon. Anyone else on their second go around with this issue?

    Please look there: https://discussions.apple.com/message/22401775#22401775

  • After installing the last version of iTunes, it failed to lunch and gave me 2 Error messages with Error 7 title , rebeat installation several times with the same Error message, what shall I do?

    Once I finish upgrading iTunes on my Windows PC, I had an Error as t shown on the image below which doesn't allow the iTunes App to lunch.
    Please advise what shall I do ?

    Uninstall your existing copy of iTunes. Delete any copies of the iTunesSetup.exe (or iTunes64Setup.exe) installer files from your downloads areas for your web browsers and download a fresh copy of the iTunes installer from the Apple website:
    http://www.apple.com/itunes/download/
    (The current build of the 11.1.4.62 installer was changed a few days ago, which fixed the bulk of the reports of MSVCR80.dll/R6034/APSDaemon.exe/Error-7/AMDS-could-not-start trouble ... but the build number on the installer was not changed. So we're trying to make sure you do the reinstall using a "new good" 11.1.4.62 installer instead of an "old bad".)
    Does the install with the new copy of the installer go through properly? If so, does that clear up the error message?
    If you still have the same error messages cropping up, then try the procedures from the following user tip:
    Troubleshooting issues with iTunes for Windows updates

  • Have been using FaceTime for long time with same person, for the last two weeks when trying to connect, we get connection failed message, something change in settings that we should look at?

    Now getting FaceTime failed message when trying to connect with a person that were connecting successfully with up unto two weeks ago, has something changed?

    Take a look around you here in this forum. Many people are talking about having problems using FaceTime. A few users claim to have contacted Apple and Apple says that they are aware of an issue with FaceTime and that they are working on it.
    Some users claim that upgrading to iOS 7 solved there problem with FaceTime. Take a look around the forum and read some of the other discussions.

Maybe you are looking for