@george1421 Once again sir, you are a legend. Fixed
Posts made by RogerBrownTDL
-
Space Issue
Iām having a space issue with my Fog server. I think when iām deleting images, they are only deleting from the gui and not the box itself? Is there a way to āpurgeā any remnants?
Output from putty:
root@tie-fogdeploy-01:~# df
Filesystem 1K-blocks Used Available Use% Mounted on
udev 5941224 0 5941224 0% /dev
tmpfs 1197468 1104 1196364 1% /run
/dev/mapper/ubuntuāvg-ubuntuālv 513396624 326710568 164713068 67% /
tmpfs 5987336 0 5987336 0% /dev/shm
tmpfs 5120 0 5120 0% /run/lock
tmpfs 5987336 0 5987336 0% /sys/fs/cgroup
/dev/loop1 64896 64896 0 100% /snap/core20/1879
/dev/loop0 64896 64896 0 100% /snap/core20/1852
/dev/loop3 94080 94080 0 100% /snap/lxd/24061
/dev/loop2 94080 94080 0 100% /snap/lxd/23991
/dev/loop4 54528 54528 0 100% /snap/snapd/18933
/dev/loop5 54528 54528 0 100% /snap/snapd/19122
/dev/sda2 1992552 213032 1658280 12% /boot
tmpfs 1197464 0 1197464 0% /run/user/0Dashboard shows
Image list:
Total size of the images is 105.29GB?
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth Thanks friend Legendary!
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth root@tie-fogdeploy-01:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 5.7G 0 5.7G 0% /dev
tmpfs 1.2G 1.1M 1.2G 1% /run
/dev/mapper/ubuntuāvg-ubuntuālv 490G 86G 384G 19% /
tmpfs 5.8G 0 5.8G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup
/dev/loop0 92M 92M 0 100% /snap/lxd/23991
/dev/loop4 50M 50M 0 100% /snap/snapd/17950
/dev/loop2 92M 92M 0 100% /snap/lxd/24061
/dev/loop3 64M 64M 0 100% /snap/core20/1778
/dev/loop1 64M 64M 0 100% /snap/core20/1822
/dev/loop5 50M 50M 0 100% /snap/snapd/18357
/dev/sda2 2.0G 207M 1.6G 12% /boot
tmpfs 1.2G 0 1.2G 0% /run/user/0
root@tie-fogdeploy-01:~#
iām guessing /dev/mapper/ubuntuāvg-ubuntuālv 490G 86G 384G 19% / means its worked? -
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth Thanks my friend, snapshot taken in hyper-v and command runā¦ Stupid Q now. How do I check if itās worked
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth further info print iāve got if this makes more sense:
root@tie-fogdeploy-01:~# sudo parted /dev/sda unit MiB print
Model: Msft Virtual Disk (scsi)
Disk /dev/sda: 512000MiB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:Number Start End Size File system Name Flags
1 1.00MiB 2.00MiB 1.00MiB bios_grub
2 2.00MiB 2050MiB 2048MiB ext4
3 2050MiB 511999MiB 509949MiBIf the system isnt running, surely I wouldnt be able to do anything, so it needs to be online?
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth So obviously as a Linux noob, I know very littleā¦ Iām purely (I know, insert puke emoji here) a Windows Sysadmin. If I understand it correctly the way iāve got it setup is like having a single big C:\ and all iām wanting to do is get the entire fog server to see it all rather than just a partition of itā¦ If I follow that command
ālvextend --extents +100%FREE ubuntu-vg/ubuntu-lv --resizefsā
Will it do that so that the full 500gb would be visible and the images stored remain intact? -
RE: Ubuntu Help - Boot Problem #N00b
@lukebarone response: root@tie-fogdeploy-01:~# lvextend -L +398g ubuntu-vg/ubuntu-lv --resizefs
Insufficient free space: 101888 extents needed, but only 101887 available
root@tie-fogdeploy-01:~# -
RE: Ubuntu Help - Boot Problem #N00b
In which case based on the output here:
root@tie-fogdeploy-01:~# pvs
PV VG Fmt Attr PSize PFree
/dev/sda3 ubuntu-vg lvm2 a-- <498.00g <398.00g
root@tie-fogdeploy-01:~# lvs
LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert
ubuntu-lv ubuntu-vg -wi-ao---- 100.00g
root@tie-fogdeploy-01:~# vgs
VG #PV #LV #SN Attr VSize VFree
ubuntu-vg 1 1 0 wzān- <498.00g <398.00g
root@tie-fogdeploy-01:~# lvextend -L +398g ubuntu-lv --resizefs
Please specify a logical volume path.
Run `lvextend --helpā for more information.
root@tie-fogdeploy-01:~#Would it be lvextend -L +398g ubuntu-vg --resizefs ?
-
RE: Ubuntu Help - Boot Problem #N00b
@lukebarone said in Ubuntu Help - Boot Problem #N00b:
lvextend -L +398g ubuntu-lv --resizefs
to confirm, this will mean I can actually use the box to itās full 500gb drive allocation?
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth said in Ubuntu Help - Boot Problem #N00b:
lvs
Output is as follows:root@tie-fogdeploy-01:~# pvs PV VG Fmt Attr PSize PFree /dev/sda3 ubuntu-vg lvm2 a-- <498.00g <398.00g root@tie-fogdeploy-01:~# lvs LV VG Attr LSize Pool Origin Data% Meta% Move Log Cpy%Sync Convert ubuntu-lv ubuntu-vg -wi-ao---- 100.00g root@tie-fogdeploy-01:~# vgs VG #PV #LV #SN Attr VSize VFree ubuntu-vg 1 1 0 wz--n- <498.00g <398.00g root@tie-fogdeploy-01:~#
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth said in Ubuntu Help - Boot Problem #N00b:
df -h
Okay, removed the offending one using rm -rf /images/dev/c8d9d2d4c8ac df -h shows:
root@tie-fogdeploy-01:~# df -h Filesystem Size Used Avail Use% Mounted on udev 5.7G 0 5.7G 0% /dev tmpfs 1.2G 112M 1.1G 10% /run /dev/mapper/ubuntu--vg-ubuntu--lv 98G 86G 7.8G 92% / tmpfs 5.8G 0 5.8G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup /dev/loop0 92M 92M 0 100% /snap/lxd/23991 /dev/loop1 64M 64M 0 100% /snap/core20/1822 /dev/loop2 92M 92M 0 100% /snap/lxd/24061 /dev/loop3 50M 50M 0 100% /snap/snapd/17950 /dev/loop5 50M 50M 0 100% /snap/snapd/18357 /dev/loop4 64M 64M 0 100% /snap/core20/1778 /dev/sda2 2.0G 207M 1.6G 12% /boot root@tie-fogdeploy-01:~#
Rebooted VM. df -h shows
root@tie-fogdeploy-01:~# df -h Filesystem Size Used Avail Use% Mounted on udev 5.7G 0 5.7G 0% /dev tmpfs 1.2G 1.1M 1.2G 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv 98G 86G 7.8G 92% / tmpfs 5.8G 0 5.8G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup /dev/loop1 64M 64M 0 100% /snap/core20/1778 /dev/loop0 64M 64M 0 100% /snap/core20/1822 /dev/loop2 50M 50M 0 100% /snap/snapd/18357 /dev/loop5 92M 92M 0 100% /snap/lxd/24061 /dev/loop3 50M 50M 0 100% /snap/snapd/17950 /dev/loop4 92M 92M 0 100% /snap/lxd/23991 /dev/sda2 2.0G 207M 1.6G 12% /boot tmpfs 1.2G 0 1.2G 0% /run/user/0 root@tie-fogdeploy-01:~#
Itās a 500gb VHDX though, surely this shouldnt be full?
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth said in Ubuntu Help - Boot Problem #N00b:
ls -al /images/dev
root@tie-fogdeploy-01:~# ls -al /images/dev total 16 drwxrwxrwx 4 fogproject root 4096 Mar 3 15:43 . drwxrwxrwx 7 fogproject root 4096 Mar 1 19:31 .. drwxrwxrwx 2 root root 4096 Mar 3 15:45 c8d9d2d4c8ac -rwxrwxrwx 1 fogproject root 0 Sep 7 20:42 .mntcheck drwxrwxrwx 2 fogproject root 4096 Sep 7 20:42 postinitscripts root@tie-fogdeploy-01:~#
-
RE: Ubuntu Help - Boot Problem #N00b
@Sebastian-Roth said in Ubuntu Help - Boot Problem #N00b:
root@tie-fogdeploy-01:~# df -h Filesystem Size Used Avail Use% Mounted on udev 5.7G 0 5.7G 0% /dev tmpfs 1.2G 118M 1.1G 11% /run /dev/mapper/ubuntu--vg-ubuntu--lv 98G 98G 0 100% / tmpfs 5.8G 0 5.8G 0% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs 5.8G 0 5.8G 0% /sys/fs/cgroup /dev/loop0 92M 92M 0 100% /snap/lxd/23991 /dev/loop1 64M 64M 0 100% /snap/core20/1822 /dev/loop2 92M 92M 0 100% /snap/lxd/24061 /dev/loop3 50M 50M 0 100% /snap/snapd/17950 /dev/loop5 50M 50M 0 100% /snap/snapd/18357 /dev/loop4 64M 64M 0 100% /snap/core20/1778 /dev/sda2 2.0G 207M 1.6G 12% /boot
root@tie-fogdeploy-01:~# du -h --max-depth=1 / 21M /tftpboot 207M /boot 118M /run 72K /home 4.0K /mnt 0 /dev 1.4G /snap 1.7G /var 48K /root 1.5G /opt 4.0K /tftpboot.prev du: cannot access '/proc/42729/task/42729/fd/3': No such file or directory du: cannot access '/proc/42729/task/42729/fdinfo/3': No such file or directory du: cannot access '/proc/42729/fd/4': No such file or directory du: cannot access '/proc/42729/fdinfo/4': No such file or directory 0 /proc 0 /sys 2.7G /usr 89G /images 7.0M /etc 4.0K /media 12K /srv 16K /lost+found 28K /tmp 100G /
root@tie-fogdeploy-01:~# mount sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) proc on /proc type proc (rw,nosuid,nodev,noexec,relatime) udev on /dev type devtmpfs (rw,nosuid,noexec,relatime,size=5941220k,nr_inodes=1485305,mode=755) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) tmpfs on /run type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1197472k,mode=755) /dev/mapper/ubuntu--vg-ubuntu--lv on / type ext4 (rw,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755) cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) pstore on /sys/fs/pstore type pstore (rw,nosuid,nodev,noexec,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/hugetlb type cgroup (rw,nosuid,nodev,noexec,relatime,hugetlb) cgroup on /sys/fs/cgroup/memory type cgroup (rw,nosuid,nodev,noexec,relatime,memory) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/rdma type cgroup (rw,nosuid,nodev,noexec,relatime,rdma) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=28,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=16183) hugetlbfs on /dev/hugepages type hugetlbfs (rw,relatime,pagesize=2M) mqueue on /dev/mqueue type mqueue (rw,nosuid,nodev,noexec,relatime) sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,nosuid,nodev,noexec,relatime) tracefs on /sys/kernel/tracing type tracefs (rw,nosuid,nodev,noexec,relatime) nfsd on /proc/fs/nfsd type nfsd (rw,relatime) fusectl on /sys/fs/fuse/connections type fusectl (rw,nosuid,nodev,noexec,relatime) configfs on /sys/kernel/config type configfs (rw,nosuid,nodev,noexec,relatime) binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,nosuid,nodev,noexec,relatime) /var/lib/snapd/snaps/lxd_23991.snap on /snap/lxd/23991 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core20_1822.snap on /snap/core20/1822 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/lxd_24061.snap on /snap/lxd/24061 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/snapd_17950.snap on /snap/snapd/17950 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/snapd_18357.snap on /snap/snapd/18357 type squashfs (ro,nodev,relatime,x-gdu.hide) /var/lib/snapd/snaps/core20_1778.snap on /snap/core20/1778 type squashfs (ro,nodev,relatime,x-gdu.hide) /dev/sda2 on /boot type ext4 (rw,relatime) tmpfs on /run/snapd/ns type tmpfs (rw,nosuid,nodev,noexec,relatime,size=1197472k,mode=755) tracefs on /sys/kernel/debug/tracing type tracefs (rw,nosuid,nodev,noexec,relatime)
root@tie-fogdeploy-01:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:0 0 91.8M 1 loop /snap/lxd/23991 loop1 7:1 0 63.3M 1 loop /snap/core20/1822 loop2 7:2 0 91.9M 1 loop /snap/lxd/24061 loop3 7:3 0 49.8M 1 loop /snap/snapd/17950 loop4 7:4 0 63.3M 1 loop /snap/core20/1778 loop5 7:5 0 49.9M 1 loop /snap/snapd/18357 sda 8:0 0 500G 0 disk āāsda1 8:1 0 1M 0 part āāsda2 8:2 0 2G 0 part /boot āāsda3 8:3 0 498G 0 part āāubuntu--vg-ubuntu--lv 253:0 0 100G 0 lvm / sr0 11:0 1 1024M 0 rom root@tie-fogdeploy-01:~#
-
Ubuntu Help - Boot Problem #N00b
Hi All,
Iām a complete noob when it comes to Linux and it was working fine for a while but now wont ābootā fully. Errors show āOS Error ERRNO 28 No space left on deviceā
Itās a VM running on Hyper-V. VHDX is a 500gb max disk with current file size of 97gb?
FDISK shows:
root@tie-fogdeploy-01:~# fdisk -l
Disk /dev/sda: 500 GiB, 536870912000 bytes, 1048576000 sectors Disk model: Virtual Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 62FE1AF7-BC7B-4B14-90C3-A9037D6F882C Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 4198399 4194304 2G Linux filesystem /dev/sda3 4198400 1048573951 1044375552 498G Linux filesystem Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 100 GiB, 107374182400 bytes, 209715200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes root@tie-fogdeploy-01:~# Disk /dev/sda: 500 GiB, 536870912000 bytes, 1048576000 sectors Device Start End Sectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 4096 4198399 4194304 2G Linux filesystem /dev/sda3 4198400 1048573951 1044375552 498G Linux filesystem Disk /dev/mapper/ubuntu--vg-ubuntu--lv: 100 GiB, 107374182400 bytes, 209715200 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes
What do I do to get this back up? Iām guessing itās something simple as expanding the OS to see the 500gb but I dont know how to do this and dont want to break this server
Cheers in advance
Roger -
RE: UEFI PXE Boot - Pain
@george1421 i can just create a new image for a 256gb drive though right? I guess I can then apply that to either a 256gb or 500gb drive and it wont matter?
-
RE: UEFI PXE Boot - Pain
@george1421 I LOVE YOU!!! Itās working
@brakcounty thanks for your help alsoI have a new problem where it wont apply the image because it says the disk is too big but Iām sure itās because I captured the image from a 500gb SSD and iām trying to apply it to a 256gb SSD but Iām happy as hell because the actual PXE is working!!!
-
RE: UEFI PXE Boot - Pain
@brakcounty Chill man, itās all goodā¦ Not everyones setup is gonna be the same. Unfortunately iāve inherited this network from someone who was far more technical than me but why he set the Watchguard as the DHCP server rather thanā¦ oh IDKā¦ an actual DHCP server is beyond me. Meh, it is what it is (I hate that saying but itās true I guess)
Will try PXE tomorrow and see what happensā¦ It is strange though that dnsmasq was already there and configured but when we first set this up it just fell on its face and wouldnāt PXE any machine hence the need to add the options 66 and 67 to at least get it to PXE so I could put an image out. Fucking manufacturers removing the option for legacy boot is fine and I guess the nature of the IT beast is that nothing stands still for long but it is a proper pain in the arse unpicking stuff to make it work based on them.