OK you guys! Spouting off how superior Linux is. Prove it by physically putting a hard drive that the BIOS does NOT recognize. Then try to read ANYTHING from the drive and use that data for recovery attempts.
I believe the BIOS need only recognize a *boot* disk. And, can even work if the drive is only *partially* recognized E.g., some ancient BIOS's won't recognize "big" disks, fully. But, you can get the BIOS to recognize the "first part" of the drive and install a kernel there which will then be bootable. Once booted, the entire drive can be seen because the BIOS isn't relied upon for disk accesses.
That seems like trivial task given the common interpretation of BIOS, pleas clarify exactly what you mean by "recognised" and or "the BIOS".
Modern hard drives (since ATA) either work or don't, if they work it's fairly easy to pull a full or partial drive image off the drive. if not the hardware fault needs to be repaired first.
Earlier this year I pulled the drive from our rented photocopier and dumped the contents. I soon figured out it was an ordinary dos format but with odd and even addresses swapped "AF-T23" instead of "FAT-32"
So I used dd to swap them and mounted the resulting image, and had a look around.
I also ran photorec against it and recovered several scanned images. I wanted to test the "secure wipe" feature, but our copier didn't come with that option.
On Fri, 26 Jun 2015 23:10:06 -0700, Robert Baer Gave us:
Dumbfuck. You ATTACH the drive to an already running system in an enclosure using eSATA or a simple USB interface. Then, THE OS examines the drive and formats it.
The MOBO and its BIOS doesn't have a damned thing to do with it, unless you are stupid enough to try to attach the drive there and see it at start-up.
You are like the idiot who boots DOS from his floppy drive and cannot figure out why a 30 year old OS cannot see a disc it was NEVER meant to be able to see. Remember the 2.88MB floppy? Those REQUIRED MOBO BIOS support BECAUSE the controller was ON the MOBO. Do you even know what "IDE" means?
Is the drive too new or too old? If its the latter: I've had problems with an PIO only old quantum bigfoot once.... You could try to recompile the kernel with support for all those really old legacy chipsets and see if they still work.... chances are they won't... worth a try tho'...
On Sat, 27 Jun 2015 17:50:25 +0200, Johann Klammer Gave us:
The way he squawks, all he wants is recovery, not a system drive. If that is the case, then there are several combo connector scheme-to-USB interface adapters out there to facilitate powering and accessing a drive.
No knowing the exact situation. I would have to say that Linux cannot perform miracle. If the BIOS does not recognize it, then Linux and/or any other OS cannot boot from it. On secondary drives, Linux does not require the BIOS to run them.
On Sat, 27 Jun 2015 14:22:44 -0700 (PDT), snipped-for-privacy@gmail.com Gave us:
More like not much knowing any situation.
Hopefully, we will be able to fend off the hackers from China... You know, the one's who claim they are not hacking us.
You are not very bright. Modern BIOSes make available all kinds of bootable media. It all depends on how you connect it.
Did you even read the original post? He never mentioned booting from the drive.
Then learn to read. He did not say a damned thing about booting from it.
This is not a Linux challenge.. It is more like a mental test for Windows idiots who think they have Linux experience, but lack skills in basic English comprehension.
Let me guess.... you write those "instructions" that come with Chinese made products. You know, the ones that are nearly unable to be disseminated over here, where the products actually get sold.
It is YOU that ate so stupid. I USED already running system, and put the HD in an enclosure (as if _that_ makes any difference; i have run HDs "bare",just "hanging" by its cables (not literally, the cables were not the support). I can read and format practically any hard drive (yes, that includes SATA, with or without use of USB). I even "brought up" a more modern computer that had NO floppy support, and NO IDE support that could not even boot from a genuine M$ operating system disk because it was so modern. (I could do that even on a Pentium II). That computer has been running fine, being used by a translation and music publisher in Addis Ababa. So do not tell me i do not know what i am doing.
I do know about "too old" - using only CHS and no translation; ugly and slightly messy even with 10-year-plus old hardware (kept my Pentium II); that is not the problem. This hard drive was bought the same time as four others and the others are still working well with zero problems; so "too new" is not the problem. Thanx.
SORRY! Have them all and a few you do not even know about. Yes, i will settle for some kind of recovery - as with that, i could restore it back to a system drive. And before you barf off all over the place,i have ALREADY done that with another hard drive, same vintage.
Very likely, but...one should be able to determine a) the interface lines existing, then b) operational, then c) can the internal "firmware" be accessed, etc. I think that it is this fine "granularity" that is needed, and so the question could be extended "does Linux have tools like that"?
ElectronDepot website is not affiliated with any of the manufacturers or service providers discussed here.
All logos and trade names are the property of their respective owners.