Gustavo Polillo wrote:
Hi sorry by my english.. In Brazil does not a real openbsd list.. so I am here..
I did:
openbsd:~# sysctl hw.disknames
hw.disknames=wd0,cd0,wd1
openbsd:~# disklabel wd1
disklabel: warning, DOS partition table with no valid OpenBSD partition
# /dev/rwd1c:
type: ESDI
disk: ESDI/IDE disk
label: ST3320620A
flags:
bytes/sector: 512
sectors/track: 63
tracks/cylinder: 255
sectors/cylinder: 16065
cylinders: 38913
total sectors: 625142448
rpm: 3600
interleave: 1
trackskew: 0
cylinderskew: 0
headswitch: 0 # microseconds
track-to-track seek: 0 # microseconds
drivedata: 0
16 partitions:
# size offset fstype [fsize bsize cpg]
c: 625142448 0 unused 0 0
i: 625137282 63 ext2fs
THUS:
openbsd:~# mount -t ext2fs /dev/wd1i /hd2
mount_ext2fs: /dev/wd1i on /hd2: specified device does not match mounted device
My Openbsd is 4.2 version..
is there any tips?
Thanks.. Gustavo Polillo.
On OpenBSD ext2fs utilities are based on version 1.27 while current e2fs
is @ version 1.40.4
with many features added.
Although you can mount a recent ext2fs when it is marked clean, problems
arise when
the fs has not been unmounted properly. All sorts of error messages.
Solution:
mark the system clean with the OS and ext2 utilities the FS was
formatted with.
On other OSes, in /etc/fstab, make sure the two last fields are 0 0
(zero zero).
Example:
I have
# cat /etc/fstab
...
/dev/wd0i /media/lenny ext2fs rw,nodev,nosuid 0 0
/dev/wd0k /data ext2fs rw,nodev,nosuid 0 0
/dev/wd0l /sandbox ext2fs rw,nodev,nosuid 0 0
...
/dev/wd0i is a ext3 (journalling) on Debian. If this slice generates
errors when mounting,
I reboot on Debian and do a fsck there.
/dev/wd0k and /deb/wd0l are ext2fs shared slices, created and formatted
with
OpenBSD on which I only use /sbin/fsck_ext2fs
(On the other OSes, the fstab lines also ends with 0 0 )
If, the other OS has not unmounted the FS, I must boot OpenBSD to run
the Fsck
and mark the system clean.
