Error: Attempting to Read or Write Outside of Partition

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

After installing Linux at the commencement boot you may encounter the mistake mentioned in the subject field.

To sympathise the reason, literally a couple of words about the boot procedure. It all starts with the fact that the BIOS initializes the devices, including hard drives; later 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 old invention and it has a number of limitations. For example, no BIOS is able to piece of work with disks over ii terabytes. Therefore, if yous installed the organisation on such a disk, then it is quite possible that the BIOS volition not cope with loading the operating system.

Merely this is non all – some BIOSes has especially poor blueprint – they cannot point Grub to files that are too far from the beginning of the disk – not necessarily across 2 Terabytes, maybe 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 offset 10% are occupied – the information can be scattered randomly. Smart disks specifically record information in different areas – and so that the disc degrades evenly.

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

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

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

• BIOS is used (not EFI)
• big disk size
• poor BIOS blueprint
• folder /boot is written also far from the kickoff of the disk

can get the mistake:

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

From that facts the conclusions follow:

• when installing on the aforementioned deejay, the fault may or may non occur (depending on the location of the /boot folder on the disk)
• Reinstalling Grub, which is advised on some websites, may or may not assistance - again, depending on where the /boot folder is overwritten
• if your figurer supports EFI, so y'all will never encounter this fault
• the problem deejay may well boot on another computer (there are nuances - on another figurer 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 showtime of the disk, and so this will almost certainly solve the problem.

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

I will prove the example of Debian and derivatives (Kali Linux, for case). With other distributions, the actions are similar – only y'all need to look in advance for data on how to put the /kick folder in a split up section during the installation process.

I would especially note that if your computer supports EFI (and this is the majority of computers manufactured in the last 8-10 years), so you will non encounter this trouble and you do not demand to worry.

So, at the showtime of the installation is performed every bit usual.

And then, when you go to the disk layout – select 'Manual':

Select the disk to sectionalisation:

Cull Yes:

Select FREE SPACE:

Create a new division:

Nosotros practise non very big size – one Gigabyte is enough for more than. In fact, less than 100 megabytes volition exist used. In whatsoever case it is better to allocate more 200 megabytes:

Primary:

Be sure to select 'Kickoff' - otherwise everything what we practice now is meaningless:

Get to Mount Point:

Select /boot - static files of the kicking loader:

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

Now go to the FREE SPACE and create another section:

Further, every bit with the beginning segmentation – set the size. Select a logical partition.

The mount point should exist / - this character means the root filesystem:

We get:

By the fashion, for the main sectionalization you can employ not all the free infinite - you tin can save space on the disk for other needs. You lot can also allocate ten Gigabytes for SWAP partition – bandy surface area (used when there is not enough RAM). To do this, when y'all gear up the properties of the disk, select 'Employ as', and at that place select the 'swap surface area'.

Next, the installation of the operating system again continues as usual.

Decision

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

By the fashion, if you lot've got into manual disk partitioning anyway, information technology is recommended to create another segmentation and select information technology to mount the /home folder. The consequence will exist that the system will be on one partition, and the /home folder, in which user files are located, on another. Therefore, the next time yous reinstall the operating system, the files in the /habitation folder volition not be deleted (unless yous do this manually). And you lot can re-connect this partitioning to mount as /home. That is, it turns out that you have a new arrangement, and all user files are in the same place as before the reinstallation.

Error: Attempting to Read or Write Outside of Partition

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

Share this post