Ubuntu 18.04 Error Attempt to Read or Write Outside of Disk Hd0

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

Later on installing Linux at the offset kicking you may encounter the error mentioned in the subject area.

To understand the reason, literally a couple of words well-nigh the boot process. It all starts with the fact that the BIOS initializes the devices, including difficult drives; afterward that, the BIOS transmits control to the GRUB booter, indicating the place on the disk where information technology should read the configuration file and other files necessary for it.

BIOS is a rather onetime invention and it has a number of limitations. For example, no BIOS is able to work with disks over 2 terabytes. Therefore, if yous installed the system on such a deejay, then it is quite possible that the BIOS volition not cope with loading the operating system.

But this is non all – some BIOSes has especially poor design – they cannot point GRUB to files that are likewise far from the showtime of the deejay – not necessarily beyond 2 Terabytes, perhaps much closer.

How is the recording on the disc performed

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

Therefore, when you install the operating system, the /kick folder can exist anywhere — even at the end 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 (non EFI)
• large disk size
• poor BIOS pattern
• folder /boot is written too far from the start of the disk

can get the error:

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

From that facts the conclusions follow:

• when installing on the same disk, the error may or may not occur (depending on the location of the /kick folder on the disk)
• Reinstalling GRUB, which is advised on some websites, may or may not help - once more, depending on where the /boot folder is overwritten
• if your computer supports EFI, and then y'all volition never encounter this error
• the trouble disk may well boot on another computer (in that location are nuances - on some other computer there may be EFI or also poorly designed BIOS)

And the most important conclusion – if the /boot folder is written to a separate partition and the partition is located at the beginning of the deejay, then this will nearly certainly solve the problem.

How to put the /boot binder on a carve up section.

I will show the example of Debian and derivatives (Kali Linux, for instance). With other distributions, the deportment are similar – only you need to look in advance for information on how to put the /boot binder in a separate section during the installation process.

I would particularly note that if your reckoner supports EFI (and this is the majority of computers manufactured in the last 8-10 years), then yous volition not encounter this problem and yous do non need to worry.

Then, at the start of the installation is performed as usual.

And so, when yous get to the deejay layout – select 'Transmission':

Select the disk to partition:

Cull Yes:

Select Gratuitous Infinite:

Create a new partition:

Nosotros do not very big size – ane Gigabyte is enough for more than. In fact, less than 100 megabytes will be used. In any case it is better to classify more than 200 megabytes:

Primary:

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

Go to Mountain Point:

Select /kick - static files of the boot loader:

Fix Bootable flag to on. Select Done setting upwardly the sectionalisation:

Now go to the FREE Infinite and create another department:

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

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

We get:

By the way, for the main sectionalization you lot tin can utilise not all the free space - you lot can salve space on the deejay for other needs. You tin can also allocate x Gigabytes for SWAP partition – swap expanse (used when in that location is non plenty RAM). To exercise this, when you ready the properties of the disk, select 'Use every bit', and there select the 'swap surface area'.

Adjacent, the installation of the operating system over again continues every bit usual.

Determination

The problem can arise both with an internal difficult bulldoze, and with an external USB drive. The problem may arise suddenly – fifty-fifty on a disk that previously worked fine – it's all about "luck" - where exactly the /kick folder will exist written. The method shown in this article will allow you not to rely on luck, but to completely prevent this problem.

Past the way, if y'all've got into transmission disk partitioning anyway, information technology is recommended to create another division and select information technology to mountain the /home folder. The result will be that the system will be on one partition, and the /abode folder, in which user files are located, on another. Therefore, the adjacent time you lot reinstall the operating system, the files in the /home folder will non exist deleted (unless yous exercise this manually). And you can re-connect this sectionalization to mount every bit /abode. That is, it turns out that y'all have a new organization, and all user files are in the same identify as earlier the reinstallation.

constablewintelpom.blogspot.com

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

Share this post