Attempt to Read or.write Outside.of This Disk Grub Rescue

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

After installing Linux at the first boot you may meet the error mentioned in the subject.

To empathize the reason, literally a couple of words about the boot process. Information technology all starts with the fact that the BIOS initializes the devices, including difficult drives; later on 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 information technology.

BIOS is a rather old 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 organisation on such a deejay, then it is quite possible that the BIOS volition not cope with loading the operating organization.

But this is not all – some BIOSes has especially poor pattern – they cannot signal GRUB to files that are too far from the beginning of the disk – non 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 10% of the disk infinite is occupied, this does not mean that the first 10% are occupied – the information can be scattered randomly. Smart disks specifically record information in different areas – so that the disc degrades evenly.

Therefore, when you lot install the operating arrangement, the /boot 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 deejay size
• poor BIOS pattern
• folder /kicking is written too far from the commencement of the disk

can get the error:

error: attempt to read or write outside of disk «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 /kicking folder on the disk)
• Reinstalling Grub, which is brash on some websites, may or may not assist - again, depending on where the /boot folder is overwritten
• if your computer supports EFI, so you will never encounter this mistake
• the problem disk may well boot on some other computer (there are nuances - on another estimator at that place may exist EFI or too poorly designed BIOS)

And the most important determination – if the /boot folder is written to a separate division and the partition is located at the showtime of the deejay, then this will almost certainly solve the trouble.

How to put the /kick folder on a separate section.

I will bear witness the example of Debian and derivatives (Kali Linux, for example). With other distributions, the actions are similar – but you need to await in accelerate for information on how to put the /boot folder in a divide section during the installation process.

I would especially annotation that if your reckoner supports EFI (and this is the bulk of computers manufactured in the last eight-10 years), and then yous will not encounter this trouble and you do not need to worry.

So, at the starting time of the installation is performed as usual.

Then, when you get to the deejay layout – select 'Manual':

Select the disk to sectionalization:

Cull Yes:

Select FREE Space:

Create a new partition:

We practice not very big size – ane Gigabyte is plenty for more than. In fact, less than 100 megabytes volition be used. In whatsoever case information technology is better to classify more 200 megabytes:

Primary:

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

Go to Mount Betoken:

Select /boot - static files of the boot loader:

Prepare Bootable flag to on. Select Washed setting upwardly the partition:

Now go to the Gratis SPACE and create another section:

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

The mount signal should be / - this character means the root filesystem:

We get:

Past the mode, for the main segmentation you can use not all the free infinite - you lot can save infinite on the deejay for other needs. You can also allocate 10 Gigabytes for Swap partition – swap area (used when there is not enough RAM). To do this, when you set the properties of the disk, select 'Use as', and there select the 'bandy area'.

Next, the installation of the operating organization over again continues as usual.

Conclusion

The problem tin ascend both with an internal hard bulldoze, and with an external USB drive. The problem may arise suddenly – even on a disk that previously worked fine – it'southward all near "luck" - where exactly the /boot folder will be written. The method shown in this commodity will allow y'all non to rely on luck, but to completely prevent this problem.

By the way, if you lot've got into manual deejay sectionalization anyhow, it is recommended to create some other partition and select it to mount the /home folder. The result will exist that the organisation will be on 1 partition, and the /home folder, in which user files are located, on another. Therefore, the next fourth dimension y'all reinstall the operating system, the files in the /home folder will not be deleted (unless y'all do this manually). And you can re-connect this partition to mount equally /dwelling. That is, it turns out that you have a new arrangement, and all user files are in the same place as before the reinstallation.

johnsonlasurged.blogspot.com

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

Share this post