Install Ubuntu and Get Read Write Outside of Disk 'hd0'

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

After installing Linux at the showtime boot you may run across the fault mentioned in the field of study.

To understand the reason, literally a couple of words nigh the kick process. It all starts with the fact that the BIOS initializes the devices, including hard drives; afterwards that, the BIOS transmits command to the Chow booter, indicating the identify 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 2 terabytes. Therefore, if you installed the system on such a disk, then it is quite possible that the BIOS will not cope with loading the operating system.

Just this is not all – some BIOSes has especially poor blueprint – they cannot point GRUB to files that are too far from the kickoff of the disk – not necessarily across ii Terabytes, perhaps 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 10% of the disk space is occupied, this does not mean that the offset ten% are occupied – the information can be scattered randomly. Smart disks specifically tape information in different areas – so that the disc degrades evenly.

Therefore, when you lot install the operating organisation, the /kick binder can be anywhere — even at the end of the disk.

mistake: try to read or write outside of deejay «hd0″

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

• BIOS is used (not EFI)
• big disk size
• poor BIOS pattern
• folder /kick is written as well far from the start of the disk

can get the error:

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

From that facts the conclusions follow:

• when installing on the same deejay, the error may or may not occur (depending on the location of the /boot folder on the disk)
• Reinstalling Chow, which is advised on some websites, may or may not help - over again, depending on where the /boot folder is overwritten
• if your computer supports EFI, then you will never encounter this mistake
• the problem disk may well kicking on some other computer (there are nuances - on some other figurer there may be EFI or too poorly designed BIOS)

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

How to put the /boot folder on a split up department.

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

I would especially note that if your reckoner supports EFI (and this is the majority of computers manufactured in the terminal viii-ten years), then you will not encounter this problem and you do not need to worry.

And then, at the beginning of the installation is performed as usual.

Then, when you go to the disk layout – select 'Transmission':

Select the disk to division:

Choose Yes:

Select FREE Space:

Create a new partitioning:

We exercise not very large size – 1 Gigabyte is enough for more than. In fact, less than 100 megabytes volition exist used. In any example information technology is better to allocate more than than 200 megabytes:

Primary:

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

Go to Mount Betoken:

Select /boot - static files of the boot loader:

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

Now go to the Gratuitous Space and create another section:

Further, as with the first sectionalisation – prepare the size. Select a logical segmentation.

The mount point should be / - this character ways the root filesystem:

We get:

By the way, for the main partition you can use non all the free space - you can relieve space on the disk for other needs. You can too 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 deejay, select 'Utilize as', and there select the 'swap area'.

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

Conclusion

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

By the way, if yous've got into manual deejay division anyway, it is recommended to create another partition and select it to mount the /home folder. The event will be that the system volition be on one partition, and the /habitation binder, in which user files are located, on some other. Therefore, the next time you reinstall the operating arrangement, the files in the /home folder will not be deleted (unless you lot practice this manually). And you can re-connect this sectionalization to mount equally /dwelling house. That is, it turns out that you have a new arrangement, and all user files are in the same identify as before the reinstallation.

phillipsnionothe.blogspot.com

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

Share this post