How to set up smartphones and PCs. Informational portal
  • home
  • Reviews
  • Installing the system on a separate ssd drive. Let's move on to disabling hibernation

Installing the system on a separate ssd drive. Let's move on to disabling hibernation

Sunday, 01 May 2011 21:01 + in the quote pad

As a small introduction, I would like to give the characteristics of SSD drives

A flash drive (SSD - Solid State Disk) contains chips instead of moving parts, which means:
a) practically silent
b) there is no risk of mechanical damage while maintaining the integrity of the case
c) has a much faster data access speed
d) more resistant to temperature conditions
e) has less weight
f) the number of rewriting cycles of each memory cell is limited

The last point is most remarkable - the number of rewriting cycles for each memory cell is limited, i.e. in fact, by clumsily setting up the software, it is quite possible to disable an expensive SSD. Therefore, you need to be very careful when installing and configuring an SSD.

The first question that arises is setting the BIOS before installing the operating system, namely setting the AHCI mode for disks.

Having entered the BIOS, I tried to turn on the AHCI mode and was a little discouraged by the lack of the AHCI selection item, thus I had to delve into this topic. What did you do:

1. First of all, as a beginner, he asked a question in the corresponding conference -. In order to get an answer from a specific user - I did it like this, as it is written in the FAQ (unfortunately, at the moment I received an answer - read the FAQ)

2. I read the FAQ carefully

A) Question: What to put in the ACHI BIOS or RAID mode: if 1-SSD (XXXX) is for the system, plus a RAID from two regular SATA HDDs, and one HDD .....
Answer: 1. In BIOS, set the RAID mode, the SSD is defined - as a "single disk" - AHCI - and so it will be there. It's better to start all this on Win7.

B) Enabling AHCI mode in an already installed Windows XP.

An important addition - we are talking about an already installed OS

3. Information from other sources

disturbing -

a) when installing the operating system Windows 2000 or Windows XP, you will definitely need a diskette with drivers (if your computer does not have a floppy drive, this may lead to an unsolvable problem, since other drives are not supported)

b) It is necessary to change the operating mode of the standard IDE / SATA controller of the chipset before installing the operating system. If the system is installed, simply changing the mode in the BIOS will result in a blue screen of death. If you still want to enable AHCI on the installed system, before changing the value of this option, forcibly change the IDE / SATA controller driver to the required one.

c) the disk subsystem of all Windows versions released before Vista will not support AHCI. And for me it is supposed to be a 32GB SSD - Windows XP. Windows XP does NOT work in this mode.

d) The Windows operating system is designed in such a way that at startup it must necessarily "pick up" the correct driver for the hard disk controller. Otherwise, the start is interrupted by the notorious "blue screen", which can be eliminated only by reinstalling the system. Moreover, the installation process will also be interrupted by the same "blue screen" if Windows is not provided with a floppy disk with the required driver in time. You cannot envy the owners of laptops at all - they have nowhere to insert a floppy disk, and Windows does not accept other media in this case.

But the solutions proposed by third-party sites -

The second method is more complicated, but it allows you to do without a floppy disk and without reinstalling Windows. To do this, the BIOS of your computer must be able to disable AHCI (or Native Mode, which in this case are synonyms). With emulation enabled, you install Windows, and then install drivers from the manufacturer of the controller (motherboard chipset). If they are not installed automatically, do it manually. Then you enable AHCI in the BIOS, and the system begins to take advantage of NCQ.

And here we are talking about turning on after installing the OS.

Although not in some BIOS there is an AHCI mode - Main / SATA Configuration / Configure SATA As (Auto, IDE, AHCI) or Integrated Peripherals / either On-Chip IDE Configuration or Onboard Promise IDE

and finally, more detailed information from ViKi

The Advanced Host Controller Interface (AHCI) is a mechanism used to connect Serial ATA storage devices to enable advanced features such as embedded command queuing (NCQ) and hot swapping.

Many SATA controllers can include simple AHCI mode or with RAID support. Intel recommends choosing RAID mode on its motherboards (with AHCI enabled) for more flexibility.

Built-in AHCI support is included in Mac OS X (starting from Mac OS X 10.4.4 for Intel), Microsoft Windows (starting from Vista), Linux (since kernel 2.6.19), NetBSD, OpenBSD (since version 4.1), FreeBSD, Solaris 10 (since release 8/07). Older operating systems require a manufacturer's driver.

AHCI support does not exist in all Southbridge chips, but even if it is implemented in a chip, the motherboard manufacturer may not implement it in the BIOS, and it will be unavailable. Sometimes the problem is solved by updating the BIOS, there are unofficial BIOS versions for many motherboards.

In some cases (Asus P5KC) AHCI support cannot be enabled on the south bridge, but it can be enabled on a stand-alone chip running on an outdated Parallel ATA connector inside the case or via an external eSATA connector. It turns out that internal hard drives cannot use AHCI, but an external enclosure with a drive connected via eSATA can.

Problems using AHCI on Microsoft Windows

Switching the ATA controller, which is part of the south bridge, to AHCI mode means the use of incompatible logic of the controller. From the OS point of view, this action is equivalent to installing an ATA controller board into the system. different from the existing one, and physically switching the boot disk to this board.

In this case, Windows will not find the boot disk during boot and will stop abnormally. with BSOD STOP 0x0000007B, INACCESSIBLE_BOOT_DEVICE. To solve the problem, you must install the driver in Windows AHCI before switching.
Manually, or using utilities like nLite, the AHCI driver can be pre-built into the Windows installation image.
In Windows 7 / Windows Vista, the AHCI driver must be enabled before enabling AHCI mode in BIOS.

4. Results of reading

You can reflash the BIOS with the hope that it will appear,

Set the SSD to RAID mode in BIOS (just try it).

In fact, such a thug because of a petty question is horror.

4.1 put the RAID mode, that's how I got the following

set the RAID mode incorrectly - then you need to slip a floppy disk with drivers

How to correctly connect the ACHI driver for HDD on an already installed Windows XP (Replacing IDE with ACHI)?
1. Back up important information.
2. In the device manager, change the driver for the SATA controller to one that supports ACHI.
3. Reboot and immediately, before loading the OS, set the BIOS to ACHI mode.

5. Hands itch to conduct tests

the main program on which I will stake during testing is CrystalDiskMark 3.10.0

test results of the WD 250GB hard drive


speed relatively new Samsung HD103


flash drive speed level

here comes the 32GB SSD Silicon Power

The main impression from the speed - in everyday use, speed, the response of the system is very, very felt.

There is a certain limit of the speed of the disk, having passed which the speed of the ssd is no longer felt.

The argument is that - the Office will open in 1.5 seconds instead of 1.9 seconds. and in practice this change is very difficult to grasp.

together with the installation CrystalDiskMark installed program SsdReady to monitor disk activity

SsdReady monitors the selected drives and collects useful and convenient statistics: who, where and how much writes on your drives. The program was made in order to estimate the number of records and, accordingly, the approximate lifetime of an SSD, even before using an SSD (based on data from SSD manufacturers).

P.S. After installation, do not forget to enable the option: Collect process names.

P.P.S. License code: 13DE4355012B9B3FA0C

installed without problems, set the settings - enable the option: Collect process names + load to tray at system startup

BUT the results are unclear - did not show the recording volumes after the tests.

addition of 05/26/2011

with the program CrystalDiskMark there are some difficulties that have not been resolved at the moment

1. the program stubbornly does not want to work in the tray - it remains in the task area.

2. During the last launch, it asks for a registration password.

All this actually shows that the program is intended for one-time - weekly monitoring, and not daily use + these are the results obtained

I can't find a photo, I'll add it later

there was an unexpected problem - friezes, yeah

Categories:
Tags:
Liked: 1 user

Top related articles