![]() |
|
OpenBSD General Other questions regarding OpenBSD which do not fit in any of the categories below. |
![]() |
|
Thread Tools | Display Modes |
|
|||
![]()
hi all bsd members,
what methods should get deployed when having problem under such situation? eg, can't boot, motherboard broke, detach the OpenBSD hard disk and attach it to another Windows OS pc, (assume we only got windows pc available) just want to copy/backup the file partitions "/home" or other relevant file partitions. could we use live cd to copy & transfer. ( is there any OpenBSD live cd that available for download? ) what should we do under such situation? please share, thank you. |
|
|||
![]()
Last edited by ocicat; 1st January 2013 at 01:18 PM. Reason: Clarify. |
|
|||
![]()
Other options: Provided the OpenBSD disk is hardware compatible with the Windows PC (Not an AMD64 OpenBSD disk in an i386 Windows PC) you should be able boot the OpenBSD disk directly.
Then you could use tar(1) to archive/compress the files on the OpenBSD disk and then write them to a CD or USB drive. Or you can edit /etc/inetd.conf to allow ftp transfers and Code:
/etc/rc.d/inetd restart |
|
|||
![]()
@ocicat,
thanks for the replied, i downloaded jggimi live OpenBSD iso, but find no luck to test and boot it inside VirtualBox, maybe i need try a little bit more =) btw, is there any specific concerns when mounting those file partitions? in linux, windows or must use OpenBSD only to mount it to prevent possible issues arise? @shep, thanks for the tips, =) |
|
|||
![]()
You don't need to test and boot inside Virtual Box. Just like any other live cd you can run it from the CD itself.
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
![]() Quote:
actually, i tried to create some possible situations and test & solve it using 1 laptop ;~) easier. and don't have to burn unnecessary dvd as virtualbox allow us to select the iso file and boot it. |
|
|||
![]()
oh yeah, the evil manufacturer love to disable our on/off VT-x setting in bios, damn!
workaround as follow, from Siddi via jggimi pm, https://www.virtualbox.org/ticket/639 Code:
C:\Program Files\Oracle\VirtualBox>VBoxManage.exe list vms "OpenBSD" {afadb990-f7d2-47b9-8f0e-180756fb62b8} C:\Program Files\Oracle\VirtualBox>VBoxSDL.exe -norawr0 -vm afadb990-f7d2-47b9-8f0e-180756fb62b8 |
|
||||
![]()
One last point on VirtualBox; it has (in the past) returned faulty register values causing bugs to appear in OpenBSD guests ... I don't recall seeing any reparations published for the particular flaw cited in the misc@ thread below. ershiba and other Virtualbox users should keep it in mind if operational errors occur in VB guests:
http://marc.info/?l=openbsd-misc&m=120492689515501&w=2 Last edited by jggimi; 2nd January 2013 at 08:06 PM. Reason: clarity |
|
|||
![]() Quote:
The Linux 3.7.1 'dmesg' reveals all: sdb1: <openbsd: sdb10 sdb11 sdb12bad subpartition - ignored Here I have the "/" partition on sdb10, swap on sdb11 and another data partition on sdb12. (the bad "subpartition message" is for partition sdb11, the OpenBSD swap partition) So I can mount sdb10 and sdb12 using the following /etc/fstab entries: /dev/sdb10 /b10 ufs ufstype=44bsd,noauto,ro 0 0 /dev/sdb12 /b12 ufs ufstype=44bsd,noauto,ro 0 0 and then mount /b10 mount /b12 |
|
|||
![]() Quote:
thanks a lot to you, comet--berkeley i successfully mount ro openbsd /home using slax linux ( kinda blasphemy ![]() ![]() |
|
|||
![]()
ok, another question related to this topic,
using VirtualBox as an example, i change the storage controller from IDE (wd0) to SCSI (sd0) and no doubt, i can't boot into OpenBSD, because the /etc/fstab try to mount device (wd0) which no longer exists, i suppose my "make it works" strategy is rewrite /etc/fstab, change wd to sd are there concerns issues when writing to OpenBSD file partitions? what is your best way to save a day when having such issue? ps: i suppose attaching an IDE hard disk into bios SATA/SCSI mode or IDE via USB cable would cause such issue. |
|
|||
![]()
The best way is to do an plain OpenBSD install to an USB stick and use that stick to boot the machine.
Then you can read the OpenBSD partition whether it is then called sd[0-9] or wd[0-9]. Simple isn't it? ![]()
__________________
You don't need to be a genius to debug a pf.conf firewall ruleset, you just need the guts to run tcpdump |
|
|||
![]() Quote:
Quote:
i was understand that DUID is more useful when dealing with lots of hard disks, to prevent misidentifying afaik, |
|
|||
![]()
ic, thanks jggimi,
glad you mentioned this, gonna try it with changing storage controller ![]() |
![]() |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Motherboard advice wanted... | Vetus | General Hardware | 6 | 4th April 2011 08:59 PM |
PHP read file contents - Maximum file size | cksraj | Programming | 1 | 21st September 2009 11:38 AM |
Mini-ITX motherboard suggestions | twisted_steel | General Hardware | 28 | 18th August 2008 09:32 PM |
Remote Access to File Server | Oko | OpenBSD Security | 7 | 23rd June 2008 05:17 PM |
Swfdec read-only file access vulnerability | corey_james | FreeBSD Ports and Packages | 0 | 14th May 2008 11:31 PM |