AtXj
Jun 8 2004, 07:33 PM
I have a 10 gb stock hard drive and would like to get the extra 2 gigz onto the F drive but when i ftp it says err 3, and then when i click on it it goes to err 1005. Can someone help me get this working or give me a runthrough on how to get my F drive set up to unlock that remaining 2 gigz.
Happiegolucky1
Jul 24 2004, 10:42 AM
I am getting a very similar error, but only with my g drive. Ava's file manager says err: 1005 for g:, and flashfxp say the same. This problem is sporatic however, on a v1.1 xbox x2.3b lite flashed with x2_4983, evo m8
dieseldk
Jul 24 2004, 10:39 PM
Hey
had same problem after install of a new hd, got it fix by formating the Partition.
boot evox and you can format the driv over ftp.
http://www.xbox-scene.com/articles/hdd-ftp.php
the joker
Jul 26 2004, 04:18 PM
heh
ftp into avalaunch and write this :
SITE FORMAT F:
atlanta800
Aug 7 2004, 08:58 PM
I have same problem with Err: 3 but no 1005, but mine is on Z: the xbox takes FOREVER to boot up, once it is in ava it works fine but takes FOREVER do even change menue options in evolutionx. is there anything i can do? I tried SITE FORMAT Z: in flashfxp and it says drive Z: formatted but i still get the error. also i turned on boot logging and i notice it tries to load "BG" several times and it says its already loaded.. is that normal? i know that avalaunch uses Z: as a cache for loading stuff into so that would explain the slowness right?
atlanta800
Aug 9 2004, 04:07 AM
::BUMP::
atlanta800
Aug 10 2004, 08:50 AM
:::BUMP:::
wow look like no one has solution for me, my friend is gna be pissed...
junkster
Aug 16 2004, 03:27 PM
My F: drive is exhibiting the same problem
F: gets an error 3 and can't be accessed.
When I try to SITE FORMAT F:, Flash FXP tells me, I get the message "553 Could not format drive F:"
Can anybody help me?
triggert
Aug 16 2004, 06:37 PM
I got the same problem with F; after I flashed my bios with x2 4981.67. I was using x2 4977 with no problems. You could always try flashing to that bios to see if it works. I don't have any free space on F: anyway so I'm not too worried about it now.
Trigg
Xe0n
Aug 17 2004, 11:22 AM
same problem here
i got same error @ F and G drives
i have xenium ice modchip @ v1.4 with retail harddisk
tried to solve it with 'format' in flashfxp
but he says this
| QUOTE |
SITE FORMAT F: 553 Could not format drive F: |
marcus21
Aug 28 2004, 09:44 PM
I rebooted AVA and went to file manager and pressed start, ftp'd command SITE FORMAT F: and it worked, i was having the same problem i'm not sure why it didn't work before maybe because of screensaver being on?
Diontae18
Aug 28 2004, 10:14 PM
Try the bios X2 4983
.06 if your xbox has an F:Drive and not a G: Drive.
.67 if your xbox has an F: and A G: Drive.
Personally, I use UnleashX 0.36 to FTP. UnleashX also supports Boost mode for faster transfer. I have never had a problem with the UnleashX dashboard as of yet.
cioprgr
Sep 2 2004, 12:39 AM
Does not work for me too. And when I do the SITE FORMAT F: command, it says, site not implemented. Where enter I do this command in FlashFXP??
DJ SKILLZ
Sep 2 2004, 01:37 PM
I just replaced my dash with avalaunch last night and I'm gettin the same error with my F drive. When Ava first boots up, I get a message box saying "0Mb remaining of F drive" I've never put anything in there. I usually use Flash FXP and I get no access to the F drive or the D drive. Any solutions?
cioprgr
Sep 2 2004, 09:14 PM
I have exactly the same problem. The D drive is your DVD drive, so you can't get anything to it.
roolf
Sep 6 2004, 04:58 PM
I get the same error (Err: 1005 and Err: 3 after I have tried to access the drive). However, my errors are on drives X, Y and Z. I have tried to format all drives several times, but no success. The drives C,E,F and G appears to be working fine.
My xbox is a 1.1 flashed with a executor2 4083.67. My HD is a Seagate Barracuda 7200.7 160GB.
Any suggestions?
SemTecS=-=RiF
Sep 8 2004, 09:52 PM
Oops, started a new topic earlier...
Now reading this, I can tell you I have the exact same problem with latest Ava-version on my F-drive, since I copied files to my F-Drive that didn't have enough space to hold them. Don't know if that really triggered the ERR1005 story on my F-partition but it sucks bigtime. Even formatting the entire drive on my PC, and then re-initialising and formatting it with NetPrep doesn't work anymore!
Sure hope the guys from Avalaunch are working on a fix for this one... Sounds like a major bug to me!
If anyone can come up with a solution?!? Thank M8s...
notserbamma
Sep 15 2004, 03:32 AM
Man you gotta be kidding me. All of these posts about the same problem and there is STILL no solution???
Man I haven't had any problems with my xbox ever until a couple nights ago. I got the Err:3,1005 error on my F drive in Avalaunch after I installed the new version of XBMC (9/9/04 I think). The only thing I can think of that I did differently is change the fan speed in XBMC. Now its like EVERY SINGLE xbe on my F drive is corrupt or something. Most of the xbe's on my E drive are fine (emus) but EVERYTHING on my F drive is corrupt and can't be accessed through anything cept flashfxp. I tried moving Boxplorer to my E drive since I've been able to access a few things on my E drive but when I select it through Ava's file manager, it says "The Selected File Is Not A Valid XBE." Man this REALLY REALLY REALLY sucks that there is no solution to this problem.
From what I've been reading in this thread it looks like not even formatting fixes the problem. Man what are we going to do people? There hasn't been very many "Common" causes of this Err3 problem but everyone seems to be experiencing it the same way.
You know it almost seems like my xbox has caught a virus or something (impossible right?). I was also thinking maybe I ran outta room on the F:\ or something but I had over 23 gigs left...man this is really killing me.
EDIT: I have now lost complete access to the F drive on FLASHfxp also so I can't even back anything up.
Where are the AV people when you need em?
notserbamma
Sep 15 2004, 04:22 AM
What Avalaunch files are in the TDATA and UDATA folders that I can delete?
How about Av files on the XYZ drives?
I'm tryna start fresh without formatting to see what happens
notserbamma
Sep 15 2004, 04:23 PM
Ok well I found the answer to the Err: 3,1005 problem people. It basically means our HDD's are "near" burnt out so its all about trying to back what you can up and buying a new HDD. You might get a few more months out of it if you format it but from what I heard from this guy our HDDs are pretty much screwed.
Oh well...time to step my game up anyway....DREAM-X here I come!!
SemTecS=-=RiF
Sep 23 2004, 09:59 PM
Oh please, get lost ;-)
You must be kidding. Never read anything about this and now suddenly dozens of people report problems with their hard-drives. My guess Avalaunch or XBMC messed up our drives; there should be some solution for this, other then replacing the drive!?! Shouldn't there be?!?
Meanwhile I keep hoping.
BTW. I put the HD in my PC and checked it; no problems detected! Strange, huh?
notserbamma
Sep 30 2004, 08:02 AM
Maybe the AV and XBMC team wants all of us to get lost...since none of them have experienced this problem. Semtecs...usually things that haven't been resolved by now are issues simpler than we would like to admit. Do you really think its an AV or XBMC problem? I doubt it man...the authors know their stuff and would have addressed it by now.
All I know is...I'm pissed...there's been no official solution to this problem...I have no HDD...and I have a whacked thompson drive (disc is dirty or damaged) which means I no longer have an xbox...
Oh well, time to finally buy a PS2...
notserbamma
Oct 20 2004, 01:16 AM
Hard Drive Failure...that is all.
pjc0715
Dec 1 2008, 05:06 PM
QUOTE(marcus21 @ Aug 28 2004, 10:20 PM)

I rebooted AVA and went to file manager and pressed start, ftp'd command SITE FORMAT F: and it worked, i was having the same problem i'm not sure why it didn't work before maybe because of screensaver being on?
Your little tip was exactly what I needed to do. Command wouldn't work, then I read your post, rebooted, reissued command and it worked like a charm.
Thanks
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.