|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Unable to install - no space left on device
Following the instructions at "https://www.c0ffee.net/blog/openbsd-on-a-laptop/"
I am trying to install 6.6 on an old laptop that had a previous version of OpenBSD installed. Due to my limited knowledge I seem to be unable to even get started as trying to overwrite the disk with "dd if=/dev/urandom of=/dev/rsd0c bs=1m" returns: uid 0 on /: file system full /: write failed, file system is full dd: /dev/rsd0c: no space left on device 1+0 records in 1+0 records out 0 bytes transferred in 0.009 secs (0 bytes/sec). I understand that the file system is full, but isn't the whole purpose of the dd command to overwrite the file system with random data? If someone could point out what I'm doing wrong or what I am misunderstanding I would be grateful. Thanks |
|
||||
From which operating system was this command run?
Your linked guide gives a GNU/Linux dd command to burn the image and then an OpenBSD dd command to wipe the disk, which is a bit confusing. For an official installation guide see https://www.openbsd.org/faq/faq4.html & https://cdn.openbsd.org/pub/OpenBSD/.../INSTALL.amd64
__________________
Are you infected with Wetiko? |
|
|||
Here is what I've now done:
Installed OpenBSD forgoing full disk encryption. Once installed, install curl to download the amd64 disk image and used dd to copy the image to a flash drive. Powered down the laptop, inserted the flash drive and booted from there. Chose "Shell" dd if=/dev/urandom of=/dev/rsd0c bs=1m Result: uid 0 on /: file system full /: write failed, file system is full dd: /dev/rsd0c: no space left on device 1+0 records in 1+0 records out 0 bytes transferred in 0.009 secs (0 bytes/sec). The hard disk is sd0, the USB is sd1 as confirmed in dmesg. I don't understand this but dmesg also tells me: softraid0 at root scsibus3 at softraid0: 256targets root on sd0a swap on sd0b dump on sd0b. I am still confused as to why a command which is supposed to overwrite data refuses to overwrite data because there is data. |
|
||||
Quote:
Quote:
Quote:
# ls /dev/rsd* command will show you the predefined sd0 devices. Only the 16 rsd0 devices are defined, partitions a-p. After your dd(1) command fails, is there a 17th rsd* file in the /dev directory?
|
|
|||
Quote:
The above command writes random data to the entire raw drive and could take a while. From FAQ 14 "This shows that we now have a new SCSI bus and a new disk, sd2. This volume will be automatically detected and assembled when the system boots. Even if you create multiple RAID arrays, the device name will always be softraid0. There won't be a softraid1 or anything else. Because the new device probably has a lot of garbage where you expect a master boot record and disklabel, zeroing the first chunk of it is highly recommended. Be very careful with this command; issuing it on the wrong device could lead to a very bad day. This assumes that the new softraid device was created as sd2. Code:
# dd if=/dev/zero of=/dev/rsd2c bs=1m count=1 Follow jggimi's advice on detecting the right drive. |
|
|||
Quote:
# ls /dev/rsd* returns ls: /dev/rsd*: No such file or directory. If I cd /dev I see rcd0a, rcd0c, etc but no rsd* Before this goes any further I just want to say I realize I'm a pain in the ass but I really do appreciate the help from both of you. |
|
|||
I don't know if this is important but just to satisfy myself I booted into the version of OpenBSD I managed to install without full disk encryption.
Running ls /dev/rsd* from theres shows me 170 rsd* files, everything from rsd0a through rsd9p. |
|
||||
For additional clarity, I have just booted the OpenBSD Release 6.6 installation media for the amd64 architecture, selected the shell, and then issued the ls(1) command I recommended. The output I show below differs from what you reported. What version and architecture of OpenBSD installation media do you have?
Code:
Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. Copyright (c) 1995-2019 OpenBSD. All rights reserved. https://www.OpenBSD.org OpenBSD 6.6 (RAMDISK_CD) #349: Sat Oct 12 11:03:52 MDT 2019 deraadt@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/RAMDISK_CD real mem = 520093696 (496MB) avail mem = 500412416 (477MB) mainbus0 at root bios0 at mainbus0 acpi at bios0 not configured cpu0 at mainbus0: (uniprocessor) cpu0: Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 2493.12 MHz, 06-2a-07 cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,CX8,SEP,PGE,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,POPCNT,AES,XSAVE,AVX,HV,NXE,LONG,LAHF,ITSC,MD_CLEAR,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: using VERW MDS workaround pvbus0 at mainbus0: OpenBSD pci0 at mainbus0 bus 0 pchb0 at pci0 dev 0 function 0 "OpenBSD VMM Host" rev 0x00 virtio0 at pci0 dev 1 function 0 "Qumranet Virtio RNG" rev 0x00 viornd0 at virtio0 virtio0: irq 3 virtio1 at pci0 dev 2 function 0 "OpenBSD VMM Control" rev 0x00 vmmci0 at virtio1 virtio1: irq 5 isa0 at mainbus0 com0 at isa0 port 0x3f8/8 irq 4: ns8250, no fifo com0: console softraid0 at root scsibus0 at softraid0: 256 targets root on rd0a swap on rd0b dump on rd0b erase ^?, werase ^W, kill ^U, intr ^C, status ^T Welcome to the OpenBSD/amd64 6.6 installation program. (I)nstall, (U)pgrade, (A)utoinstall or (S)hell? s # ls /dev/rsd* /dev/rsd0a /dev/rsd0d /dev/rsd0g /dev/rsd0j /dev/rsd0m /dev/rsd0p /dev/rsd0b /dev/rsd0e /dev/rsd0h /dev/rsd0k /dev/rsd0n /dev/rsd0c /dev/rsd0f /dev/rsd0i /dev/rsd0l /dev/rsd0o # |
|
|||
I wish I could post the entire message as you did, but booting from the installation media shows me:
erase ^? werase ^W kill ^U intr ^C status ^I Welcome to the OpenBSD/amd64 6.6 installation program. (I) nstall (U)pgrade (A)utoinstall or (S)hell s #ls /dev/rsd* ls: /dev/rsd*: No such file or directory |
|
||||
I'm sorry. I do not have a rational explanation for why you and I get different results with what appears to be the same media.
There are two amd64 kernels built for installation media: RAMDISK used with the diskette image (floppy66.fs) and RAMDISK_CD used with all other media. *Both* have 16 /dev/rsd* devices pre-defined on boot. Where did you download your image from? Mine came from OpenBSD's CDN pool (https://cdn.openbsd.org/pub/OpenBSD), and was checked against the Project's digital signature with signify(1). |
|
|||
Quote:
In the installer, do you have /dev/wd* devices listed? |
|
|||
I'm sorry but right now I am so confused I really don't remember when I did the install without encryption what it said it was partioning.
In the installer I do have /dev/rwd0a thru rwd0p. If I try: dd if=/dev/urandom of=/dev/rwd0c bs=1m I get: dd: /dev/rwd0c: Device not configured, To answer jggimi's question I got the install media using: curl -OJ https://cdn.openbsd.org/pub/OpenBSD/...4/install64.fs This and dd'ing to the flash drive was done on a MacBook Air running the latest OS. |
|
|||
OK. I did the installation again without encryption to see what it would say.
Available disks are sd0 sd1 Root disk is sd0 I hit enter and see: Disk: sd0 Usable LBA: 64 to 976773104 [976773168 sectors] #: type [ start: size] 1: EFI SYS 64 960 3: OpenBSD 1024 976772081 Use (W)hole disk MBR, whole disk (G)pt, (O)penBSD area or Edit? [OpenBSD] I select the default OpenBSD and auto layout. When done I have /dev/rsd0l,d,f,g,h,k,j,and e. |
|
||||
Quote:
The only thing I can think of is that the file was not correctly downloaded, or, not correctly written to your USB device. You can at least check the SHA hash against the one published by the Project. If it does not match, that would be the root cause of your problem. If it matches, you could try writing it to USB again. Code:
SHA256 (install66.fs) = 0e40d80abb7b46b2309063600997c91c83e576ae07cf3007385095b10948a410 |
|
|||
Just to recap:
Downloaded install66.fs from https://cdn.openbsd.org/pub/OpenBSD/6.6/amd64/ Per jggimi check she hash with sha256 - matches dd if=install66.fs of=/dev/sd1 bs=1m Boot from installation media; choose Shell ls /dev/rsd* returns "No such file or directory sysctl.disknames shows sd0, rd0, sd1 dd if=/dev/urandom if=/dev/rsd0c bs=1m returns write failed file system is full. disklabel sd0 returns "DIOCGDINFO: Inappropriate ioctl for device disklabel sd1 returns "/dev/rsd1: No such file or directory" At this point I am in way over my head. My sincere thanks and appreciation to: Head_on_a_Stick jggimi shep TronDD for taking the time to try helping me out with this. Right now I think I'll leave it for a day and then try again. If it still doesn't work I guess I'll have to forget about encryption and just install the OS. Thanks again to everyone. |
|
|||
Quote:
That seems to have done the trick and /dev/urandom is happily overwriting the data. jggimi - I can't thank you enough. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Unable to install 5.9 release | betweendayandnight | OpenBSD Installation and Upgrading | 7 | 19th February 2016 12:16 PM |
unable to install HP printer | sacerdos_daemonis | OpenBSD General | 25 | 5th January 2015 01:20 PM |
Unable to find device node for /dev/mfid0s1b | bforest | FreeBSD Installation and Upgrading | 4 | 30th September 2011 04:02 PM |
DVD burn error: No space left on device | guitarscn | OpenBSD General | 1 | 22nd December 2009 07:50 PM |
no space left on drive while installing? | knasbas | OpenBSD Installation and Upgrading | 2 | 20th July 2009 09:50 PM |