|
OpenBSD Installation and Upgrading Installing and upgrading OpenBSD. |
|
Thread Tools | Display Modes |
|
|||
Quote:
If this hard drive was connected to the other system via USB, all USB devices are connected through the SCSI subsystem -- hence the references to /dev/sd0 found in /etc/fstab. This can be fixed by editing /etc/fstab. Use the device node seen in the laptop's dmesg(8) output. As a personal request, please limit the number of exclamation points (!) used in your messages. Exclamation points are meant to indicate emphasis. Using exclamation points for every sentence is frequently interpreted as shouting. |
|
||||
Thanx for the quick reply.How can i edit the /etc/fstab?I have not vi available as far as i can see.
I keep that in mind about '!' but rest assured; there's no shouting in my typing. edit: the hard disk is identified as 'wd0' |
|
|||
Quote:
Assuming you installed the complete system onto the hard drive being transferred, vi(1) is available as it is installed in /usr/bin. In order to access vi(1), you will need to manually mount the partition containing /usr. |
|
||||
If you boot in single-user mode, no mounts will be made, though the root partition will be available read only (it will be the "a" partition on booted device, most likely wd0). To boot in single user mode, use "-s" at the boot> prompt.
Mount points vary. Once you reach the shell, issue the following commands (assuming wd0 is the device, and /etc is in the root partition): # export TERM=vt220 # mount /dev/wd0a / # cat /etc/fstab (Look for your /usr partition, this example will assume you see it as /dev/sd0f. Change accordingly.) # mount /dev/wd0f /usr ---- From here, you can use vi(1) or mg(1) or sed(1) to edit the file. |
|
|||
As stated by jggimi, if you installed OpenBSD to the drive when it was in an enclosure it would be on the USB bus and hence be detected as a simulated SCSI drive.
Once installed back in the new system it would be on the native controller for that system, device names and numbering obvious may differ.. this should have been apparent to you. At the boot> prompt you could pass '-a' along with '-s' as a flag to manually specific the root partition so that you're using the GENERIC kernel and not the RAMDISK kernel, the same thing applies.. you need to fix your fstab file to contain the right disk so that the partitions are mounted at boot time. Fortunately with I believe in 5.0 the installer will ask if you want to use DUID's instead of device names in the fstab. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
FreeBSD Health Check: FreeBSD - "The unknown giant" | J65nko | News | 0 | 4th February 2010 11:28 PM |
Fixed "xinit" after _7 _8, "how" here in case anyones' "X" breaks... using "nvidia" | jb_daefo | Guides | 0 | 5th October 2009 09:31 PM |
"No package available in the PKG_PATH" error | Nk2Network | OpenBSD Packages and Ports | 19 | 12th January 2009 09:22 PM |
Installation master "disk" using USB memory stick, dd? | peterg22 | FreeBSD Installation and Upgrading | 7 | 14th October 2008 05:18 PM |
CF, as wd0, 4.3 dmesg "DMA error" | s2scott | OpenBSD Installation and Upgrading | 11 | 10th May 2008 08:21 AM |