I have a server with the root filesystem / mounted on /dev/sda, i.e., the entire disk, which has no partitions. This situation makes me uncomfortable, and I would like to partition the disk and put the root filesystem on /dev/sda1. I'm not sure if this is possible though, without losing my entire server, since this is the root filesystem. If I run fdisk /dev/sda, it lets me create the partition /dev/sda1 over the entire disk, but I'm afraid that this will wipe the disk, so I haven't proceeded with that. Is there a way to move / from /dev/sda to /dev/sda1 without losing everything? Here's fdisk -l, edited to remove loop devices:

Disk /dev/sda: 117.19 GiB, 125829120000 bytes, 245760000 sectors
Disk model: QEMU HARDDISK   

Disk /dev/sdb: 1000 MiB, 1048576000 bytes, 2048000 sectors
Disk model: QEMU HARDDISK   

Device     Boot Start     End Sectors  Size Id Type
/dev/sdb1        2048 2047999 2045952  999M 82 Linux swap / Solaris

Disk /dev/sdc: 160 GiB, 171798691840 bytes, 335544320 sectors
Disk model: Volume          

Device     Boot Start       End   Sectors  Size Id Type
/dev/sdc1        2048 335544319 335542272  160G 83 Linux

I would like to mount a disk on /var/log, the thing is, there are some process/services writing into it, such as openvpn, or system logs. Is there a way to mount a filesystem without having to restart the machine, or stopping the service? Many thanks

I have installed Ubuntu on my old laptop to give him a second life. I installed Ubuntu on the 24gb SSD. But the old Windows10 partition is on the 1tb HDD. Now every time I boot the system it asks which one I want to boot from. I dont want this, and want to just delete everything from this disk (the Windows one ofcourse) and start with a clean disk. How do I do this?

My computer was running a dual boot with Arch and Manjaro on their own partitions. I decided I wanted to exchange Manjaro for Debian, so I flashed the USB and deleted the Manjaro partition. Apparently that's the one Grub wants to boot from though, so I get shifted into grub rescue> mode. I want to at least boot into Arch, and ideally get a grub menu where I can boot from the USB containing the Debian installer. The problem is when I run insmod normal, I get the error in the title.

I use VirtualBox on Windows 10 to run a VM using Ubuntu 16.04.1 LTS. I got the VM from my University with a disk size of 20GB which was way to optimistic ... so I want to resize it to 50GB so I already did 0. (on the host) Make a BackUp ;) 1. (on the host) VBoxManage clonehd "source.vmdk" "clone.vdi" --format vdi 2. (on the host) VBoxManage modifyhd "clone.vdi" --resize 51200 3. (on the host) Downloaded GParted.iso 4. (in the VM) Booted into GParted 5. (in the VM) Expanded The Swap from 2GB to 4GB according to the RAM of the VM I also changed Now I see the following image As you can see obviously the new diskspace got added at the end of the disk. But now I'm facing the problem that I cannot expand the primary partition because the swap partition is "in the way". I neither am able to move the swap-partition. **How can I expand the primary partition and/or move the swap partition to the end of the disk?** The Idea I had was: 1. Delete /dev/sda5 2. Delete /dev/sda2 3. Create new Partition /dev/sda2 with file format linux-swap and the end of the disk 4. Expand /dev/sda1 to use the rest of the disk **Is this the way to go? Will Ubuntu automatically "know" where the swap partition will be after this action?**

After running in to some problems with my initial attempt to install, I've premade the partitions I want to use, and I want to install Debian using those partitions. One of the problems I had was that the partitioner included in the installer can't create the layout I want: | drive | partition | encryption | filesystem | mountpoint | | ----- | --------- | ---------- | ---------- | ---------- | | 1 | 1 | none | ESP | /boot/efi | | 1 | 2 | LUKS1 | ext4 | /boot | | 1 | 3 | LUKS2 | ext4 | / | | 2 | 2 | LUKS2 | btrfs | /home | **Now I've created those partitions, with some customized options, and I want to tell a Debian installer to use the existing partitions.** After failing to find that option in the Calamares-based GUI installer on my rescue system, searching online has given me the impression that neither the self-booting graphical or text-based installers have that option either. I'm hoping someone here can point me to an option that will use the existing partitions, or failing that to an option that can recreate both LUKS1 and LUKS2 encrypted volumes and put specified unallocated spaces between partitions

I want to move an empty disc space from one partition to another. Is this possible? In the below image, I have free space under /local (/dev/sda3). I want to allocate this space to / which is on /dev/sda2. How can I do this?

I want to change from Windows to Pop OS, I don't want to make a partition and getting a dual boot, just want to say goodbye to Windows, the issue is that I'm not pretty sure if doing this having two Hard-disks (128GB+1TB), so, is it possible that I loose one Hard-disk on the process ? I'm worried to loose the 1TB Hard-disk (currently I'm working on my local C drive (the one of 128GB, so don't know if I can loose the 1TB of storage).

I have a ~500gb hard drive that I intend to split 50/50 for Windows 10 and Linux Mint 17. The Windows partition is 232GB and the Linux partition is, at the moment, uncreated. When I run Mint off my pen drive and go to install it, it shows the hard drive as 500gb of 'free space'. I can't install because it will wipe my Windows install. How can I get the partition to show in Mint?

i have a ~200GB luks encrypted partition on a dual boot setup and i've just shrunk my windows partition by a bit so i can use the unallocated space on my root partition which is xfs. how would i go about extending the luks partition and subsequently the voidvm/root one? $ lsblk -f NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS nvme0n1 ├─nvme0n1p1 vfat FAT32 SYSTEM 089A-0EBD /boot/efi ├─nvme0n1p2 ├─nvme0n1p3 ntfs Windows 18E6E384E6E3610C ├─nvme0n1p4 ntfs 066C04116C03FA67 └─nvme0n1p5 crypto_LUKS 1 2ab65cad-808c-4168-8e51-0e081bd9d58b └─voidvm LVM2_member LVM2 001 c4mDao-UZLC-znl1-efSm-SmPB-DrRU-ChSQ82 ├─voidvm-root xfs root 2559b74d-53a8-437f-82e5-62b514f6987d 2.1G 91% / └─voidvm-home xfs home 60588d15-9846-43c9-996b-a4d09cea8b07 17.1G 90% /home Physical vol sudo pvs PV VG Fmt Attr PSize PFree /dev/mapper/voidvm voidvm lvm2 a-- <195.31g 0 LVM lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert home voidvm -wi-ao---- <171.31g root voidvm -wi-ao---- 24.00g

I was reading "Full_Disk_Encryption_Howto_2019" - Link . I noticed that the partition type codes used by the author are uncommon:

sgdisk --typecode=1:8301 --typecode=2:ef02 --typecode=3:ef00 --typecode=5:8301 $DEV

In a standard linux installation, I can see these two type codes: 8300 and 8200. These are the names per partition type code:

$ sgdisk -L
0700 Microsoft basic data  0c01 Microsoft reserved    2700 Windows RE          
3000 ONIE boot             3001 ONIE config           3900 Plan 9              
4100 PowerPC PReP boot     4200 Windows LDM data      4201 Windows LDM metadata
4202 Windows Storage Spac  7501 IBM GPFS              7f00 ChromeOS kernel     
7f01 ChromeOS root         7f02 ChromeOS reserved     8200 Linux swap          
8300 Linux filesystem      8301 Linux reserved        8302 Linux /home         
8303 Linux x86 root (/)    8304 Linux x86-64 root (/  8305 Linux ARM64 root (/)
8306 Linux /srv            8307 Linux ARM32 root (/)  8400 Intel Rapid Start   
8e00 Linux LVM             a000 Android bootloader    a001 Android bootloader 2
a002 Android boot          a003 Android recovery      a004 Android misc        
a005 Android metadata      a006 Android system        a007 Android cache       
a008 Android data          a009 Android persistent    a00a Android factory     
a00b Android fastboot/ter  a00c Android OEM           a500 FreeBSD disklabel   
a501 FreeBSD boot          a502 FreeBSD swap          a503 FreeBSD UFS         
a504 FreeBSD ZFS           a505 FreeBSD Vinum/RAID    a580 Midnight BSD data   
a581 Midnight BSD boot     a582 Midnight BSD swap     a583 Midnight BSD UFS    
a584 Midnight BSD ZFS      a585 Midnight BSD Vinum    a600 OpenBSD disklabel   
a800 Apple UFS             a901 NetBSD swap           a902 NetBSD FFS          
a903 NetBSD LFS            a904 NetBSD concatenated   a905 NetBSD encrypted    
a906 NetBSD RAID           ab00 Recovery HD           af00 Apple HFS/HFS+      
af01 Apple RAID            af02 Apple RAID offline    af03 Apple label         
af04 AppleTV recovery      af05 Apple Core Storage    af06 Apple SoftRAID Statu
af07 Apple SoftRAID Scrat  af08 Apple SoftRAID Volum  af09 Apple SoftRAID Cache
b300 QNX6 Power-Safe       bc00 Acronis Secure Zone   be00 Solaris boot        
bf00 Solaris root          bf01 Solaris /usr & Mac Z  bf02 Solaris swap        
bf03 Solaris backup        bf04 Solaris /var          bf05 Solaris /home       
bf06 Solaris alternate se  bf07 Solaris Reserved 1    bf08 Solaris Reserved 2  
bf09 Solaris Reserved 3    bf0a Solaris Reserved 4    bf0b Solaris Reserved 5  
c001 HP-UX data            c002 HP-UX service         e100 ONIE boot           
e101 ONIE config           ea00 Freedesktop $BOOT     eb00 Haiku BFS           
ed00 Sony system partitio  ed01 Lenovo system partit  ef00 EFI System          
ef01 MBR partition scheme  ef02 BIOS boot partition   f800 Ceph OSD            
f801 Ceph dm-crypt OSD     f802 Ceph journal          f803 Ceph dm-crypt journa
f804 Ceph disk in creatio  f805 Ceph dm-crypt disk i  fb00 VMWare VMFS         
fb01 VMWare reserved       fc00 VMWare kcore crash p  fd00 Linux RAID

Thus we can easily interpret the type codes that the author has used: - 8301 is "Linux reserved". - ef02 is "BIOS boot partition". - ef00 is "EFI System". I don't understand as follows: 1. What is the usage of a partition type 8301? 2. Why should someone use partition type 8301 instead of 8300 (i.e. "Linux filesystem") ? 3. When do we use the other specific Linux-partition ? For example, when do we use 8302 over the standard 8300 ?

The Debian GUI Installer provides multiple automated partitioning options. I've had no issues with "use entire disk and set up encrypted LVM" so far. But toady I had to install Debian on a disk that is preoccupied by multiple operating systems. In the beginning of the disk there is a Windows installation, and in the end of the disk there is an Ubuntu installation. There is one continuous space in the middle of the disk. When I chose the "use the largest continuous free space" option it correctly selected the entire space but there was no automated process to encrypt the volume. So I have an unencrypted Debian installation in the middle of my disk. Is it possible to encrypt only the entire Debian portion of the disk after an unencrypted installation in the same way as the guided "use entire disk and set up encrypted LVM"? I chose to put "All files in one partition". If there are no native methods, can third party software such as Veracrypt help? If there is no solution but to reinstall, how should I partition next time to achieve what I want?

I'm endeavoring to put Kali linux onto a USB stick - I know it's already written up , but I'd like to use only a portion of the total space (the aforementioned link will use the entire drive space). Let's have my 16GB usb stick mounted as sdb ... the goal is: 16 GB total, split like this... ---------------------------- | 11 | 01 | 04 | (GB) ---------------------------- sdb1 sdb2 sdb3 (partition ID) FAT32 FAT32 FAT32 (format) storage fatdog kalipart (label) - sdb1 is FAT32 and the main storage area (so that [windows can see it] along with any other OSes) - sdb2 is bootable and has Fatdog64 (6.3.0) and Precise Puppy (5.7.1) installed (multi-booting from one syslinux menu) - sdb3 is the target partition for Kali to use The objective is to multi-boot Fatdog64, Puppy, and Kali linux. Currently, sdb2 is bootable (syslinux) and successfully passes to Fatdog and Puppy, both on sdb2. Next I'd like to add chainloading to Kali on sdb3. It seems to me that the best way to do that is to load GRUB4DOS from syslinux (both on sdb2), map sdb3 and chainload to sdb3 from GRUB4DOS. So I ask: How do I install Kali onto an existing partition on this USB stick? Other options: - Install live Kali onto the USB stick/partition from the Kali distro itself - but this doesn't seem to be an option the same way it is with Fatdog/Puppy/Ubuntu - Boot direclty to sdb3, chainloading to sdb2 if necessary (not preferred, but an option) >Update: > >1. I have tried copying the files from a mounted iso to sdb3 using Fatdog64 and noticed several errors, mostly in copying the firmware files. Here's two examples: > Copying /mnt/+mnt+sda1+isos+kali-linux-1+0+6-i286+kali-linux-1+0+6-i286+iso/firmware/amd64/microcode_1.20120910-2_i386.deb as /mnt/sda3/firmware/amd64-microcode_1.20120910-2_i286.deb > ERROR: Operation not permitted > Copying /mnt/+mnt+sda1+isos+kali-linux-1+0+6-i286+kali-linux-1+0+6-i286+iso/debian as /mnt/sda3/debian > ERROR: Operation not permitted > These errors look like permissions errors, but I can't tell if they affect booting or not (I can troubleshoot other errors later, I'd prefer to keep this question to just multi-boot). > >2. I'm chainloading GRUB4DOS from the SYSLINUX installed by default via Fatdog64 ... > > label grub4dos > menu label grub4dos > boot /boot/grub/grldr > text help > Load grub4dos via grldr (in /boot/grub) > endtext > > ... and then once in GRUB4DOS, I have successfully chainloaded GRUB2 (on the kali partition) ... > > title Load GRUB2 inside of kali > find --set-root /g2ldr.mbr > chainloader /g2ldr.mbr > > ... but all this gives me is a grub> prompt, and I haven't figured out any proper combinations of GRUB4DOS commands to load GRUB2 with a GRUB2 config file - and to add to the confusion, I thought the live CD iso of Kali ran on syslinux. (@jasonwryan @user63921)

I bought a brand new 4TB Western Digital Blue HDD, which is connected to my NAS running Debian via usb with an external HDD enclosure. I used the following commands to setup the drive: (parted) mklabel gpt (parted) mkpart primary 0% 100% sudo mkfs.exfat -n 4tbBackup /dev/sdc It seemed to work okay on the Linux machine, but when I plugged it into my Windows PC, it showed up under Disk Management as an unallocated 2048GB partition and another unallocated partition with the rest of the disk on it. I tried switching to gdisk, and it immediately gave me this error: GPT fdisk (gdisk) version 1.0.6 Warning: Partition table header claims that the size of partition table entries is 0 bytes, but this program supports only 128-byte entries. Adjusting accordingly, but partition table may be garbage. Caution: invalid main GPT header, but valid backup; regenerating main header from backup! Warning: Invalid CRC on main header data; loaded backup partition table. Warning! Main and backup partition tables differ! Use the 'c' and 'e' options on the recovery & transformation menu to examine the two tables. Warning! Main partition table CRC mismatch! Loaded backup partition table instead of main partition table! Warning! One or more CRCs don't match. You should repair the disk! Main header: ERROR Backup header: OK Main partition table: ERROR Backup partition table: OK Partition table scan: MBR: MBR only BSD: not present APM: not present GPT: damaged Found valid MBR and corrupt GPT. Which do you want to use? (Using the GPT MAY permit recovery of GPT data.) How can I totally reset the drive so that I can clear all of this header corruption out and reformat it safely to exFAT?

While trying to install Kali Linux as a secondary OS with Windows 11(primary OS), the partition created for Kali is not visible during the Graphical Install. The hard drive I'm trying to install kali on is of size 1 TB. Even after making a partition of 150 GB, the disk partition menu in the graphical install of kali is not showing the partitions rather showing the disk with one partition of size 932 GB Upon initial research, I tried fixing the partition table using gdisk (since my system has GPT disks), but that didn't help. Primary OS: Windows 11 Disk Type: GPT Image Used: kali-linux-2021.4a-installer-amd64 **EDITED:** Disk Management: Partition Not Visible:

In my RHEL 7.8 server, I have allocated 100GB for /root. I need more space because I need to install more software that will be available systemwide for all users. I am new to Linux and not very familiar with the system. My questions are: 1. If I want to increase my /rhel-root, what should I do? 2. If I can't increase the space, how can I change the download and software Installation location? 3. For case 2, is there anything else I need to do so my users have access to the installed software? Thanks a lot for your time!

I found a similar question here, but there's one different point on my server: --- Volume group --- VG Name vg System ID Format lvm2 Metadata Areas 1 Metadata Sequence No 4 VG Access read/write VG Status resizable MAX LV 0 Cur LV 3 Open LV 3 Max PV 0 Cur PV 1 Act PV 1 VG Size 465.50 GiB PE Size 32.00 MiB Total PE 14896 Alloc PE / Size 14896 / 465.50 GiB Free PE / Size 0 / 0 VG UUID xxxxx pvdisplay --- Physical volume --- PV Name /dev/sda3 VG Name vg PV Size 465.51 GiB / not usable 15.00 MiB Allocatable yes (but full) PE Size 32.00 MiB Total PE 14896 Free PE 0 Allocated PE 14896 PV UUID xxxxx I would like to install virtualizor on the server and using volume group storage configuration, but with this preinstalled OS configuration (volume group root) it is not possible and my skills are not enough to know how to do to shrink the volume group and create a new one.

I have a 6TB disk in Debian Linux 12, let's say the disk is /dev/sdd. It's just for data; no parts of the OS are on it. Now I’m trying to use it as a normal disk with the full space in a single partition. If I try to create the partition, fdisk tells me that the max size with a DOS partition is 2TB. If I create that, I get a new device /dev/sdd1, but the size is limited to 2TB, not what I want. To have a single 6TB partition, I need to use a GPT partition table instead of DOS. If I do that, I can create a single partition with fdisk. But then I don’t get a device node for the partition (/dev/sdd1), which I need later for things like formatting. Any ideas? **EDIT** I create the partition that way. fdisk /dev/sdd Tells me then: *The size of this disk is 6 TiB (6597069766656 bytes). DOS partition table format cannot be used on drives for volumes larger than 2199023255040 bytes for 512-byte sectors. Use GUID partition table format (GPT).* Commands are then: g n w That creates a GPT partition table and a new partition with full size and writes it down.

I am trying to install CentOS-7(GNOME) on my Dell Laptop which has 30GB SSD and 1TB HDD, RAM of 8GB, i7 Intel processor. I am doing manual partition. I have selected SSD as bootable drive and my /boot is on SSD with 2GB as size. In which drive should I put the leftover(28 GB) SSD for better OS performance? I tried adding it to / but this is only allowing me if I deselect HDD. But then I am not able to add other partitions like /home, swap, /usr, /opt, /var on HDD and they would all default to SSD which has only 30GB in total which I am trying to avoid. I am planning to use this laptop for my development activities eg Java(with Intellij), Docker, Kubernetes, MongoDB, Apache Flink which at times would be resource consuming and I want to utilize SSD as much as feasible. Does the CentOS installation always default to the disk with higher space? Should I simply install to SSD(deselect HDD) and then after installation mount other partitions on HDD? So far, I am trying to follow instructions here : I'll appreciate if someone could help.

New(ish) to Linux, not new to hardware. Got a new NAS which is to be hosted via linux. Before that I'm faffing about with the hardware, and things I will never get to do otherwise. Live distros are so lovely. I've tried around 4 so far. Anyway, I'm also playing around with the storage drives. There's a bunch of file systems and partition types to explore - swap partitions are a puzzling idea to me, but whatever. I can play around with those easy enough. However I could not find a way to actually delete the partition **TABLE**, just change it. I tried both fdisk and gparted. How do you delete the partition table?