Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
i have tried all of those things in the last post, none of them have helped, i cannot boot the machine to do any of the post boot tests seeing as no OS detects the drive if i hotplug it, i can get to the bios setup screen if the drive is unplugged, then if i plug it in while in the setup it detects it, however i have to reboot the machine to get it to load an OS thus we hit the post problem again
my question really is, how can i repair a stuffed up drive that causes these issues outside of the machine, the machine cannot be used as a repair tool, i have already tried all above options before posting this thread
after consulting with some professionals with some real experience in this area, they have concluded that the firmware on the drive is kaput, thus the drive needs replacing or re-flashing, seeing as i cannot re-flash it myself then i'll need to replace it, thanks for your attempt to help (however idiotic and ignorant) but i'll be spending my hard earned money and buying a new drive due to the lack of intelligence displayed in this thread
thanks for your attempt to help (however idiotic and ignorant) but i'll be spending my hard earned money and buying a new drive due to the lack of intelligence displayed in this thread
Can you please explain to me how ANYTHING we suggested in this thread caused to your issue? Obviously you had the issue with the drive BEFORE any of us said anything. As none of us get paid to help with these threads, I do find your statement not only incorrect but also offensive.
Everyone here is presumed to be doing the best they can, including the original poster. Would he do that bit more by telling us what was likely to have caused the fault, if it is indeed the HDD firmware, as no change in an operative system should have any effect on the HDD at that level?
i was not using the drive in any way other than how it was intended, i dont know why this happened, only that it did and i explained what happened, i have already explained multiple times that i cannot boot anything while the drive is plugged in or enabled, and there is no way to access the drive from anywhere if i power on the machine whilst the drive is plugged in.
this was a cheap drive in the first place though less than 6 months old i should have expected that it would be fine. i also apologize for the insults in my previous post, my frustrations at the lack of peoples understanding of what i had thought i made perfectly obvious overwhelmed me and i should have remained restrained, however no option that anyone has presented thus far has, or could be successful, i can say that with confidence, as my BIOS is unable to be accessed at all whilst the drive is connected and no bootable medium works
In the future if you need help then provide information requested. I know that I requested information and you stated you would post but never did. Burn me once and your excused, burn twice then beware!
If you have more eyes on the thing with brains attached then you may get to a solution. Maybe you should read the next two links because as far as I'm concerned you are going too need to learn how to use them;
Do you have the ability to install the HDD in another system and is there any difference if you do?
My suggestion was actually to remove the HDD, change the BIOS settings, then re-install the HDD. I thought that the BIOS at Fail-Safe settings and the HDD probably set as PATA might at least get the HDD recognized.
Before you throw anything away, you might try something like this, not a tool meant for your problem, but it resets the HDD firmware and might jog your firmware into working. You would need a Windows machine.
onebuck: i was going to post the information, but if you had read the next post, it would tell you that there was no change in the output what so ever, the output it's self would have confused the matter further as i had to connect an external HDD to transfer the log, this of-course shows up in the log and makes the issue more difficult to resolve
thorkelljarl: i will be asking a friend of mine to take the drive for a few days to see if he can use it in his system, i have also already tried removing the drive and changing all the BIOS settings to defaults. as for the windows tool, that requires a machine to be able to boot and recognize the drive, at this point my machine is not capable of that. I also always thoroughly comb google before posting any threads on an issue i have, there was nothing that seemed remotely close there
i know this, but the machine has nowhere to store anything, so i have nowhere to redirect anything to without confusion being added, i analysed the dmesg output myself and there was nothing out of the ordinary there anyway
the drive started working once i plugged it into a different mobo, i was then able to perform a S.M.A.R.T test on it to find that it had a few bad sectors, i know this shouldn't hang the BIOS but it did, i was in a stressful situation where every solution that was offered was impractical for the state of affairs, i have now run some repair utilities on the drive and am using it to hold virtual machine images, however i do stress that people also listen to the OP when they say that the solution offered was not even remotely helpful, if people had listened from the start then no-one would have gotten hot under the collar and gotten "burned". it was not my intention to insult anyone, only to show that the offered solutions were either impossible, impractical or unnecessary. a better line of attack in hindsight would have been to run diagnostic tools for the motherboard rather than the hard drive. i did make it clear that i would not be able to run any tests on the drive it's self