Disk Erase Failed Error Bad File Descriptor
Contents |
You can not post a blank message. Please type your message and try again. This discussion is locked Douglas :-) Level 1 (0 points) Q: Hard Drive issues Hi everyone,I've disk erase failed with the error file system formatter failed been having hard drive problems with my iMag G5, bought last
Disk Erase Failed With The Error Posix Reports The Operation Couldn't Be Completed
summer. Basically what happens, is over a couple of weeks, the computer starts to simply "freeze up" occasionally
Disk Erase Failed With The Error Invalid Request
while you are using the computer. Then, what happened this morning, it won't turn on at all. Trying to boot into single user mode sort of works, I get to
Disk Erase Failed With The Error Unable To Write To The Last Block
a command prompt, but when trying to boot the system, I get "disk0s3 I/O" errors.The "fix" I have at the moment is to reinstall OS X. I've done that twice now.Running Disk Utility's repair disk feature was failing this morning, it wouldn't complete. Last week, it rand without issue, reporting a clean bill of health. Using the Apple Hardware Test, disk erase failed with the error couldn't open device I could find no errors.Is this likley to be a software issue, or, as I suspect, a slowly dying harddrive?If so, what is the best way to get it fixed? I live in the Netherlands, and the closest "Apple Authorized Service Provider" to me wants to charge me for a "Service Agreement" - which would clearly be a charge for warranty service under an existing warranty.Any help would be great,Douglas iMac G5 (no iSight), Mac OS X (10.4.3), System freezes, no booting, and disk I/O errors. Posted on Jan 2, 2006 3:30 PM I have this question too by Mac Medic (be@MacOSG.com),Solvedanswer Mac Medic (be@MacOSG.com) Level 6 (17,290 points) A: Thanks Bmer,I tried doing as you say, though I recieved a "Zerodisk failed" error with the message "Could not opendisk". I also tried doing a normal erase, it said"Disk erase failed" with the message "Bad filedescriptor". I can't even see the hard drive as aninstall target for the installer now!Sound like that disk has major problems. You could try DiskWarrior on it, but I would contact A
NSXVirtual SAN vCenterFusionWorkstationvExpertVMware {code} CloudCredSubmit a Link Home > VMTN > VMware vSphere™ > VMware ESXi 5 > Discussions Please enter a title. You can not post a blank message. Please type your message and try again. 4 Replies Latest reply: Aug 2, 2016 4:54 AM by nE0sIghT Bad file disk erase failed with the error invalid request exfat descriptor during update toxadi Aug 7, 2012 8:12 AM Hello all,I am trying disk erase failed with the error couldn't unmount disk to patch an ESXi 5.0.0.0-474610 but when I run esxcli software vib install -d /vmfs/volumes/... I get [InstallationError] disk erase failed with the error wiping volume data Failed to clear bootbank content /altbootbank: [Errno 9] Bad file descriptor: '/altbootbank/state.167901' Please refer to the log file for more details. When I go to /altbootbank I see several state.XXXXXX folders and https://discussions.apple.com/thread/296114?start=0&tstart=0 their contents, but the specific state.167901 is having problems. I cannot cd into it, I cannot delete it even with rm -Rf.~ # cd /altbootbank/ /vmfs/volumes/295d3aaa-e07d5aaa-6aaa-2a6e97710aaa # ls -l some other files... drwxr-xr-x 1 root root 8 Jan 1 1970 state.167901 drwxr-xr-x 1 root root 8 Jan 1 1970 state.173542 drwxr-xr-x 1 root root 8 Jan 1 1970 state.1905743 drwxr-xr-x 1 root root 8 https://communities.vmware.com/thread/413441?start=0&tstart=0 Jan 1 1970 state.2006991 drwxr-xr-x 1 root root 8 Jan 1 1970 state.2044903 drwxr-xr-x 1 root root 8 Jan 1 1970 state.2075069 drwxr-xr-x 1 root root 8 Jan 1 1970 state.3439559 drwxr-xr-x 1 root root 8 Jan 1 1970 state.3814560 drwxr-xr-x 1 root root 8 Jan 1 1970 state.3869077 drwxr-xr-x 1 root root 8 Jan 1 1970 state.3999265 drwxr-xr-x 1 root root 8 Jan 1 1970 state.4036776 drwxr-xr-x 1 root root 8 Jan 1 1970 state.4059918 drwxr-xr-x 1 root root 8 Jan 1 1970 state.4137343 drwxr-xr-x 1 root root 8 Jan 1 1970 state.4998361 -rwx------ 1 root root 23225 Aug 1 17:43 state.tgz some other files... /vmfs/volumes/295d38eb-e07d5e9d-6f8e-2a6e97710fdd # cd state.167901/ sh: getcwd: No such file or directory (unknown) # and # rmdir state.167901 rmdir: 'state.167901': Bad file descriptor # rm -Rf state.167901 rm: cannot remove 'state.167901': Bad file descriptor dosfsck finds no errors in that partition, so I am pretty stuck.Ideas anyone? :-) 2115Views Tags: none (add) This content has been marked as final. Show 4 replies 1. Re: Bad file descriptor during update sysxperts Oct 30, 2012 12:18 AM (in response to toxadi) I had similar problem and unf
click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X http://forums.macnn.com/90/mac-os-x/405828/problems-with-restore/ > Problems With Restore user: pass: Remember Me? Show Threads http://linux.sys-con.com/node/1053821 Show Posts Advanced Search Sans Serif Small Sans Serif Medium (Default) Serif Small Serif Medium Go to Page... Problems With Restore ghporter Administrator Join Date:Apr 2001 Location:San Antonio TX USA Status: Offline Dec 19, 2009, 12:07 PM In preparation for a hard drive swap, I tried to back up my existing drive onto the new drive using Disk Utility. I disk erase said it could not verify the source due to a "bad file descriptor." Repairing permissions gave me a notice that permissions were repaired but that the SUID of something in my System/Library/CoreServices/Remote Management/ARDAagent package had been changed and would not be repaired. I'm assuming that's the file with the bad descriptor. The drive verifies fine. It sounds like I'm going to have to either delete this remote management thing then try to back up again, or install fresh on the new drive. This disk erase failed leads to questions. Is Remote Management part of the OS, or is it something I've added later? Is it OK to delete anything in the ARDAagent or the package itself? If that's a bad idea, and I should go ahead with a fresh install, what's the best strategy for getting my apps installed and my data migrated? Glenn -----OTR/L, MOT, Tx View Public Profile Find More Posts by ghporter Art Vandelay Professional Poster Join Date:Sep 2002 Location:New York, NY Status: Offline Dec 19, 2009, 02:00 PM Ignore the permissions error. It's normal and has nothing to do with your other problem. What is giving the bad file descriptor error? Vandelay Industries View Public Profile Find More Posts by Art Vandelay Hal Itosis Grizzled Veteran Join Date:Mar 2004 Status: Offline Dec 19, 2009, 02:49 PM It's becoming difficult to trust what Disk Utility says... isn't it? -HI- View Public Profile Find More Posts by Hal Itosis ghporter Administrator Join Date:Apr 2001 Location:San Antonio TX USA Status: Offline Dec 19, 2009, 07:49 PM Originally Posted by Art Vandelay Ignore the permissions error. It's normal and has nothing to do with your other problem. What is giving the bad file descriptor error? When I run Restore, I get through the source and destination selection, the verification that I want to erase the destination, and my password. The routine stops wi
HAT RUBY SAP SEARCH SILVERLIGHT SYMBIAN VIDEO VIRTUALIZATION WEB 2.0 WEBLOGIC WEBSPHERE WIRELESS XML Home Subscribe Advertise Authors Topics Videos Events Webcasts Internet of Things | Cloud | Big Data | DevOps | Containers | Microservices | WebRTC | Java | Linux | Open Stack | Mobile | Security | SDDC Linux Containers Authors: Elizabeth White, Pat Romanski, Liz McMillan, APM Blog, Miska Kaipiainen Related Topics: Linux Containers Linux Containers: Article Bad File Descriptor Error in Linux Stellar Phoenix Linux Data Recovery is a comprehensive data recovery tool By Allen Sood Article Rating: Select ratingGive it 1/5Give it 2/5Give it 3/5Give it 4/5Give it 5/5 July 30, 2009 04:30 AM EDT Reads: 69,384 Related Print Email Feedback Add This Blog This In a Linux system, files, blocks, directories, sockets and other items are referred by corresponding file descriptors. If your system is reporting errors that the file descriptor is bad, one of possible causes is that file system is corrupt and thus, you require restoring from backup. But if backup is not valid enough to restore complete information, you need to use advanced Linux Data Recovery applications. As an instance, you might encounter the below error message with your Linux based system: “Bad file descriptor” You might receive this error while trying to access a file or while trying to boot the system. Cause Possible reasons for the ‘Bad file descriptor’ error to occur are: Linux systems use a special file, called /dev/null (also called the null device). This file removes all the data that is written to it after reporting that the write process has successfully succeeded. You might receive the above error message if /dev/null has been deleted or overwritten. You can infer this cause when file system is reported as read-only at the time of booting through error messages, such as“/dev/null: Read-only filesystem” and “dup2: bad file descriptor” If you get this error message while trying to access a file, the most prominent causes are file system corruption or damaged disk block(s). In such situations, you also get write errors. Solution You need to use these methods to troubleshoot the above behavior: For solving deleted or overwritten /dev/null file issues, you need to replace it with the suitabl