Search the Community
Showing results for tags 'persistent'.
-
Hi all. I posted this question in the X-S Discord a day or two ago and haven't made any headway in resolving the issue, so I'll post here and see if anyone may be able to help. A few days ago, I acquired a "non-working" 1.2/1.3 that had never been opened but externally was very clean. When I received it, I immediately opened it up to pull the clock capacitor and clean it up. Aside from the clock cap, the polymer caps were all leaking, as well as the caps near the CPU/GPU. I cleaned and recapped the entire board before ever attempting to power it up. After the initial cleaning and repair, I finally attempted to boot to be greeted with error 21. Since I went in blind, without any idea of what was actually wrong with the system, I just assumed the dash may have possibly been wrecked from a previous softmod/user error or something, so I opted to start by installing a fresh copy of the MS Dash files via FATXplorer. I got it back together, booted, and got error 16, which was expected. I then installed an x2.3b lite to get around the clock check, but rather than booting to the dash as it should, it just hangs at the Xbox logo splash screen. At this point I tossed in Doom 3 to see if it would load a disc, and it did begin to load the game, however it immediately froze as it was began to write the initial cache data to the HDD. I decided the HDD might just be crapping out after all, so I substituted a known good working drive from another system and this is where things get weird... The system will read the x2config.ini from the second HDD (evidenced by the fact that it can and does read, load, and apply the LED and fan settings from the INI file), but was exhibiting the same problem. It just hangs at the Xbox logo splash screen instead of loading XBMC. If I lock any of the drives and try to boot from the retail bios, I go right back to error 21 again... Just to check my sanity, I tested and confirmed all the individual drives and parts work fine in another system. Also, while performing the testing in the working system, I reformatted and "factory reset" the OEM HDD using OGXbox Installer 1.5.4 just to eliminate myself and any possibility of my wrong-doing from the equation. In the working system, MS Dash loads as it should. If I move the HDD back to the problematic system, error 21. After trying various combinations of 4 HDDs, 2 DVD drives, 3 different IDE cables, 2 power supplies, both with and without a modchip, I still cannot get beyond error 21 or the system freezing... I think it's weird that I can boot into Xblast from the chip, format, lock, unlock, and read the S.M.A.R.T data from the drives without issue. It's weird that it will read the x2config.ini from the drives, but based on the observed behavior, it seems like any other HDD I/O causes it to crap itself, and ultimately all roads have led to error 21. At any rate, I am out of ideas on what else to try and any suggestions or help are, of course, greatly appreciated.
- 5 replies
-
- weird
- persistent
-
(and 1 more)
Tagged with:
Board Life Status
Board startup date: April 23, 2017 12:45:48