Error Attempt to Read or Write Outside of Disk

Solving the trouble with 'error: endeavor to read or write outside of disk "hd0″'

Afterwards installing Linux at the first boot you may encounter the error mentioned in the discipline.

To empathize the reason, literally a couple of words about the kicking process. It all starts with the fact that the BIOS initializes the devices, including difficult drives; subsequently that, the BIOS transmits control to the GRUB booter, indicating the place on the disk where it should read the configuration file and other files necessary for it.

BIOS is a rather sometime invention and information technology has a number of limitations. For example, no BIOS is able to work with disks over 2 terabytes. Therefore, if you installed the organization on such a disk, then it is quite possible that the BIOS will non cope with loading the operating organisation.

But this is not all – some BIOSes has especially poor design – they cannot point GRUB to files that are too far from the get-go of the disk – not necessarily beyond ii Terabytes, peradventure much closer.

How is the recording on the disc performed

This seems counterintuitive, but the data is not recorded to the deejay sequentially – that is, if ten% of the deejay space is occupied, this does not hateful that the first 10% are occupied – the information tin can be scattered randomly. Smart disks specifically record data in different areas – so that the disc degrades evenly.

Therefore, when you install the operating system, the /kicking folder can be anywhere — even at the stop of the disk.

error: attempt to read or write outside of disk «hd0″

So, as a result of the confluence of a number of circumstances:

• BIOS is used (not EFI)
• large disk size
• poor BIOS design
• folder /kick is written too far from the beginning of the disk

can get the mistake:

error: attempt to read or write outside of deejay «hd0″

From that facts the conclusions follow:

• when installing on the aforementioned disk, the error may or may not occur (depending on the location of the /boot folder on the disk)
• Reinstalling Grub, which is advised on some websites, may or may not help - once more, depending on where the /kick folder is overwritten
• if your estimator supports EFI, then yous volition never run into this error
• the problem deejay may well boot on another computer (in that location are nuances - on another estimator in that location may be EFI or as well poorly designed BIOS)

And the most important conclusion – if the /boot binder is written to a separate partition and the partition is located at the offset of the disk, then this will almost certainly solve the problem.

How to put the /boot folder on a divide section.

I volition testify the example of Debian and derivatives (Kali Linux, for instance). With other distributions, the actions are similar – but you need to look in advance for information on how to put the /kicking binder in a separate section during the installation procedure.

I would particularly notation that if your computer supports EFI (and this is the majority of computers manufactured in the last 8-10 years), so you will not encounter this problem and you lot practice not need to worry.

So, at the beginning of the installation is performed as usual.

Then, when you become to the disk layout – select 'Manual':

Select the disk to sectionalisation:

Choose Yep:

Select FREE SPACE:

Create a new segmentation:

We do not very big size – 1 Gigabyte is enough for more than. In fact, less than 100 megabytes will be used. In any instance it is better to allocate more than 200 megabytes:

Primary:

Be sure to select 'Beginning' - otherwise everything what we do at present is meaningless:

Become to Mount Point:

Select /boot - static files of the boot loader:

Set Bootable flag to on. Select Done setting up the sectionalisation:

Now go to the FREE Infinite and create another section:

Further, as with the first partitioning – fix the size. Select a logical partition.

The mountain point should be / - this grapheme means the root filesystem:

Nosotros go:

Past the way, for the main sectionalisation y'all tin can use not all the free space - you can save space on the disk for other needs. You can likewise allocate 10 Gigabytes for Swap partition – bandy area (used when there is not plenty RAM). To do this, when you set up the properties of the disk, select 'Use as', and there select the 'swap area'.

Next, the installation of the operating arrangement again continues equally usual.

Conclusion

The problem can ascend both with an internal hard drive, and with an external USB drive. The trouble may ascend suddenly – even on a deejay that previously worked fine – it's all most "luck" - where exactly the /kick binder will be written. The method shown in this article will let you not to rely on luck, but to completely prevent this trouble.

By the way, if yous've got into manual disk division anyway, information technology is recommended to create some other division and select it to mountain the /abode folder. The outcome volition be that the system will be on one partition, and the /dwelling house folder, in which user files are located, on another. Therefore, the adjacent fourth dimension yous reinstall the operating arrangement, the files in the /home binder will not be deleted (unless yous do this manually). And you tin can re-connect this sectionalisation to mount as /home. That is, it turns out that you have a new system, and all user files are in the same identify as before the reinstallation.

gonzalesexpron.blogspot.com

Source: https://miloserdov.org/?p=2420

Share this post