|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Hello.
I run -current on my laptop (x220) and it works great. use to update it with the latest snapshot every week i download all the necessary files from an ftp mirror to my /mnt/home/afdruiprek/upgrade folder and cp bsd.rd to / and reboot bsd.rd and update, all has worked well untill now. when it was time to install today it verifyed all files and installed bsd bsd.rd and bsd.mp but when it was time for base63.tgz it says "id0 on /mnt: file system is full", which is true. df -h shows (I use full disk encryption therefore sd1) Filesystem size used avail capacity Mounted on /dev/sd1a 1005M 1003m -48.4M 105% /mnt when i installed the system from the start i choose auto partitioning. When i boot the system normal i cant do anything, some things was probably owerwritten. init : can´t exec /bin/sh for /etc/rc: Exec format error When i try to change shell nothing hapens. How can i make /mnt bigger (without damage everything else)? or what files under /mnt is it safe to remove to make room for the update. du dosent work. Best regards... ~ |
|
|||
The reason why i didn't post the whole df is because i could not copy it from the laptop
and /mnt/home is because df was run from bsd.rd boot, normal boot docent work anymore But here comes a hand written df -h Code:
Filesystem size used avail capacity Mounted on /dev/rd0a 3.5M 3.2M 229k 94% / /dev/sd1a 1005M 1003m -48.4M 105% /mnt /dev/sd1k 95.0G 9.7G 80.5G 11% /mnt/home /dev/sd1d 3.9G 10.0k 3.7G 0% /mnt/tmp /dev/sd1f 2.0G 966M 946M 51% /mnt/usr /dev/sd1g 1005M 185M 769M 19% /mnt/usr/X11R6 /dev/sd1h 9.8G 1.3G 8.1G 14% /mnt/usr/local /dev/sd1j 5.9G 2.0k 5.6G 0% /mnt/usr/obj /dev/sd1i 2.0G 2.0k 1.9G 0% /mnt/usr/src /dev/sd1e 18.1G 17.5M 17.2G 0% /mnt/var Last edited by ocicat; 2nd June 2018 at 03:35 AM. Reason: Please use [code] & [/code] tags when posting command output. |
|
||||
Thank you for sharing this. Now I understand the "/mnt" references in your first post. You were using the RAMDISK kernel after running the upgrade script.
You need to determine what file has filled the root filesystem. The most common reason is a standard file in the /dev directory instead of a character or block special file (device node). /dev should be very small. Code:
$ du -sh /dev 34.0K /dev # cd /mnt/dev # export TERM=vt220 # ls -l | less # rm file.I.accidentally.created.with.a.typo In most cases, the offending file will be obvious. Should the /dev directory be correct and small, then the other directories on the root filesystem may be investigated. Last edited by jggimi; 1st June 2018 at 10:16 PM. Reason: formatting, clarity |
|
|||
Quote:
I was making a bootable usb with dd earlier this week and guess what ? an 918M file in /mnt/dev called sd2 Everything works fine now. Last edited by afdruiprek; 2nd June 2018 at 10:43 AM. |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Full Disk Encryption | jjstorm | OpenBSD Installation and Upgrading | 3 | 30th May 2016 08:19 PM |
Full disk encryption in NetBSD 7.0 RC2 | bashrules | NetBSD Installation and Upgrading | 1 | 18th August 2015 02:11 AM |
Reliability concerns on full disk encryption | virtuvoos | OpenBSD Security | 4 | 31st October 2013 11:06 PM |
FreeNAS 8.3.1 introduces full disk ZFS encryption | J65nko | News | 0 | 22nd March 2013 02:54 AM |
Full disk encryption with Loop-AES | deviant085 | OpenBSD Security | 9 | 23rd November 2009 12:51 AM |