http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml
You need to create a boot device to run hdderase. It can not be executed in Windows. Needless to say it will wipe all data from your drive.
Printable View
http://cmrr.ucsd.edu/people/Hughes/SecureErase.shtml
You need to create a boot device to run hdderase. It can not be executed in Windows. Needless to say it will wipe all data from your drive.
Ice009
I had the same issue with an HDD once, never found what caused the problem.
HDDerase runs from DOS and needs IDE mode, you could try that. Link to pcper article and download
edit:
You could try updating the MB BIOS, as a last option you could try selecting RAID mode.
(raid mode compares to AHCI performance wise, should be identical)
Alright, Thanks. I've downloaded both versions 3.3 from your link and also the latest version from Audienceofone's link.Quote:
Originally Posted by Anvil
I am kind of stuck on how to make a bootable USB drive. A bit confused about the instructions. If it's not any trouble can someone explain how to make a my Corsair Voyager flash drive boot with it?
Ice009
Google translation of a German webpage
It uses the HP USB Boot Utility which is the same one as I've been using, however I'm using the Win98 boot files, just not sure where you could download them.
The above link should make it work.
ice - i have installed w7x64 4-6 times with ahci turned on in the bios - always just had one drive connected to the mobo - the drive has always been found and instal as far is getting the os onto the drive has been no problem.
OK that seems simple enough to make the flash drive bootable. Do I then just copy the HDDerase.exe file to it after making it bootable?Quote:
Originally Posted by Anvil
Ice,
That's correct, just copy any files you need to the USB.
I keep firmwares, hdderase, mb bioses and so on the USB stick, very neat.
the intel ahci diver is built into windows, but the amd one is not thats why i thought u had AMD. sorry for the confusion
Actually the default AHCI driver is Microsoft's own, and was the only TRIM enabled driver until now. Now Intel has their TRIM driver out (Rapid Storage Technology its called).Quote:
Originally Posted by zanzabar
Microsofts pciide driver also supports ATA TRIM. But since you get better performance and more options with AHCI, it's not really an issue.
This is an amazing amount of responses to the OP.
Have you tried using a board NOT! made by DFI? I have tried close to one dozen SSD's (that's 12 F'ing disks!) on a DFI board and they never....ever....worked right.
Maybe the board was bad? I thought so too. I replaced it. And replaced it. And replaced it. Nothing helped...... Until
I got a board made by some one else. Even DFI tech support told me I was right in buying a board from someone else. I had to deal with RMA from more than one company before I realized that it wasn't RAM (which I RMA'd) or the CPU (which I replaced!!!) or the PSU (which I tested against 5 other units) or, so I though, the mobo, which I replaced more than once with a DFI board.
My personal conclusion is that DFI boards will get the highest overclocks you know, but the stability is worse than awful with SSD's.
Hey guys, just want to say that I was able to get the drive installed in RAID mode as a single drive. This still gives me Trim right?Quote:
Originally Posted by Anvil
I had all drives unplugged except the DVD drive and the SSD to do it.
Question. Should I try moving the DVD drive to one of the two yellow Jmicron ports and have the SSD by itself on one of the 6 green SATA ports?
Also, I forgot to mention that I have my HAF 932 e-SATA front panel SATA connector plugged into one of the green ports. Would that make a difference you think?
Ice,
In order to get TRIM on your SSD in RAID mode you have to install RST 9.6.
Based on the number of ports I would expect the ICH ports to be Green and the yellow ones to be some sort of extra bonus controllers.
Keep the SSD on the ICH, the DVD should work on both the green and yellow ports, it shouldnt make any difference whether keeping it on the ICH or not.
(I've got my DVD installed on one of the "bonus" controllers, it's working just fine)
The same goes for the eSATA front panel connector, it shouldn't matter where you connect it.
Putting everything on a single controller should not be an issue.
One “problem” with using different on-board controllers is the added time to initialise the controller during boot up, albeit it only a few seconds it can be annoying. ;)
I haven't used multiple add in controllers very often but when i have it seemed that intialization - for the most part - went on in parrallel. The cards seem to initialize themselves and usually only stop if there is operator intervention. For this reason - again generally speaking - adding/using multiple controllers should not add a lot of additional boot time.Quote:
Originally Posted by audienceofone
My experience is that if you use multiple controllers on a mobo, or if you add controllers via a dedicated card then you will have to wait whilst each one initialises serially during the boot process. :shrug:
You can see what I'm talking about on one of the videos I posted on the Napalm thread. ICH9 first and then the U3S6. It’s only a few seconds for each controller but if you reboot frequently it can be annoying.
A while back I had 2 areca 1231's installed in the same machine for a short time - both cards initialized at the same time.
I now have a 9211 and 1231 but not in the same machine - I should give this a try and see what happens.
The extra onboard might take some time initializing *if* there are devices connected.
For me that's not an issue, compared to raid controllers initializing the onboard stuff are just peanuts.
As for initializing in parrallel, the PERC and the 9260 initializes in their own time.
The 9260 doesn't start "booting" until the PERC is done, can't really speak for other controllers.
Just a quick tip if you get odd bios errors like the OP:
Put the #1 Intel/Amd controller in AHCI/RAID mode and the #2 mb controller in IDE mode. Then just connect the drive to the #2 controller, install windows and add drivers for the Intel/Amd when you're in windows. Turn off, switch the drive to #1 controller, boot and off you go.
I'm actually thinking it might be the Motherboard because someone pointed out to me on a previous BIOS update for the DFI T3EH8 was for compatibility with SSD drives.Quote:
Originally Posted by saint-francis
"Major Reasons of Change:
1. Fixed system lagged issue.
2. Fixed some SSD device can’t install OS issue."
That was listed for an old Beta BIOS, but I'd say you might be right that it's probably a compatibility issue with the DFI Motherboard. What kind of problems have you had with SSD drives and on what DFI board?
Anyone know how would I go about telling DFI about the issue to see if it can be fixed via a BIOS update?
Thanks for the info. I just installed the Rapid Storage Technology 9.6 driver. How do I go about checking to see if Trim is working properly?Quote:
Originally Posted by Anvil
So just to clarify running a single drive in RAID mode should be very similar to AHCI mode? What are the actual differences if any between RAID mode and AHCI with a single drive?
Hey guys,
Can anyone quickly tell me how to check to see if Trim is working? Thanks.
google fsutil disabledeletenotify to see if os is sending the command
instal and then run crystal disk info to see if drive accepts the command
Quote:
Originally Posted by Ice009
I had the same issues you had (I.e. couldn't do anything with a SSD unless it was in RAID mode) as well as things like not being able to install an OS and the system crashing from time to time (well actually it was fairly often). Trying to make a backup with Acronis amounted to failure about 85% of the time. I had this problem on P35 and X48 boards. They apparently had the same kinds of problems with the X58 board and there were a bunch of BIOS fixes which seemed to help people but never completely ironed all of the bugs out. I even got a custom BIOS from DFI Taiwan to address the issue and it didn't do a damn thing for me. Replacing the board was really good though. Fixed all of my problems instantly. Now I have a pile of SSD's and DFI boards. The SSD's work in any board not made by DFI and the DFI boards work with any disk that isn't a SSD.
You can call DFI and tell them but I don't think they are going to do anything about it. If they haven't fixed it by now they probably never will or don't know how to. Or maybe the "bug" causing all of these problems is something that they depend on for other performance factors which they deem more important than SSD support.
Edit:
Just realized that you are using the X58 board. This is a known issue. There's no secret about it. The running train of thought on the DFI support forum last time I checked was "there are problems but they go away as soon as you have booted". Whatever that means. Obviously this is not the case.