I created a hdd.img using Yocto and copied the same to pendrive using dd command.
On PC it is mounted as single partition "boot".
When I checked on command line using sudo fdisk -l, it is showing four partitions.
I booted my hardware from pendrive, now I want to remove rootfs.img from boot partition mounted at /media/realroot and copy same rootfs.img again to the same partition.
It is giving No disk space error. I am trying to copy the same rootfs.img which I deleted.
Why it is using only 700MB for boot partiton of 16GB pendrive, or how to increase boot partition size in Yocto to make use of full 16GB?
I'm not sure I understood the real problem but if you are looking for a way to increase the free space on the rootfs, take a look at IMAGE_ROOTFS_EXTRA_SPACE as well as IMAGE_OVERHEAD_FACTOR.
Related
I've an Apache Kafka 2.7 and it is in the production environment, there are discs that we use as data storage, and they are %90 filled, how can i increase the disc capacity, they are in virtual environment would you also share the answer for if physical discs were connected?
Assuming you've configured log.dirs to use specific volume mounts, then no.
The contents of the directories for that value must be topic-partition folders, not a parent folder of all volumes where it would be more possible to dynamically add directories.
Drives may be hot swappable on the physical server (or VM), yes, but you'll still need to edit the Kafka property file to include the new mount path, and restart the broker.
Also, if you add new disks, Kafka will not rebalance existing data, meaning you'll still have discs that are 90% full. In any environment, you'd need to create/acquire a new, larger disc, shutdown the machine, replicate the disc, then attach the new one, and restart.
I set up standalone ironic with mitaka version. I created a whole disk image (ubuntu14.04) by virt-install and used Coreos pxe image (Here) as deploy kernel and ramdisk. (ubuntu 14.04) The disk image size is 10G, and it could be deployed successfully on my node. When I logged in the node and checked the disk info, it only used 10G disk size for /dev/sda. The physical disk size of node is 500G.
How do I make my image to use whole disk size of node after deploying? Thanks.
You have a swap partition after the root partition and that will block the online growing of the root FS.
You need to either move the swap to the front of the disk or remove it entirely.
I have a 300 GB external drive connected to a Raspberry Pi. I changed the file boot/cmdline.txt in order to use the SD card only to boot up the system. Then the partition /root is located in /dev/sda2 (external drive). How can I increase the size of the root partition? I want to merge all the unallocated space with /sda/dev2.
I tried by using GParted, but it is necessary to unmount before merging:
sudo umount /dev/sda2
umount: /: device is busy.
Gparted Image:
I used fdisk on Ubuntu to achieve something similar. Rasbian is very similar to Ubuntu and should work the same.
You have to actually remove the original partition and the extended partition before creating a new, larger partition. It doesn't loose any data as long as you don't write changes back to the disk. Still, I would take a backup. :)
I wrote a wiki on it here: http://headstation.com/archives/resize-ubuntu-filesystem/
I am installing ubuntu 14.04 on an acer machine and I realize that the OS can't initialize if the booting files are lost.
I would really appreciate if somebody could bring information about how these files work.
Thank you very much.
There are several stages of booting in GRUB, each of them uses differect file(s)
Stage 1: boot.img is stored in the master boot record (MBR), or optionally in any of the volume boot records (VBRs), and addresses the next stage. At installation time it is configured to load the first sector of core.img.
Stage 2: core.img is by default written to the sectors between the MBR and the first partition, when these sectors are free and available. Once executed, core.img will load its configuration file and any other modules needed, particularly file system drivers; at installation time, it is generated from diskboot.img and configured to load the stage 3 by its file path.
_
This is a little piece of info, for full information check Wikipedia
While creating virtual Machine i forgot to "Tick" - Allocate all disk space now.
I have already setted up machine, and cloned several from the one, and made changes. :(
So i was looking for any option so that i could change my machine (thin disk province) to change to pre-allocated where it will be equal to dedicated size.
using: VMWARE workstation 7.1.4
created disk without allocating disk size now need fixed allocated disk size.
any help would be highly appreciated.
To sum up: how to change growable disk to pre-allocated in vmware workstation.
vmware-vdiskmanager -r sourceDisk.vmdk -t 2 targetDisk.vmdk
as an administrator while using cmd from windows..
lets say, windows, 7 and we have to open cmd as administrator and cd to the particular location where vmware is installed and run this command,
I'm not sure that you can change the disk type to pre-allocated. You can, however, expand a growable-type disk by selecting Utilities->Expand in the Hardware tab of the VM settings. You can only expnad the disk if the VM has no snapshots and the VM is not a linked clone or the parent of a linked clone. In order to make the newly added space available to your VM, you have to use a disk management tool to increase the size of the existing partition to match the new expanded size of the virtual disk.