I got this message :
# fsck_ext2fs -d /dev/ad3
** /dev/ad3
BAD SUPER BLOCK: MAGIC NUMBER WRONG
ioctl (GCINFO): Inappropriate ioctl for device
/dev/ad3: can't read disk label
is this due to geom or to FreeBSD 5.1? It worked on a 4.6.2.
Though /dev/ad3 could be mounted when it was clean.
___
I've a IDE hard drive sliced in 4 part
ad0s1 : NTFS
ad0s2 : linux swap
ad0s3 : linux ext2fs
ad0s4[a-f] : ffs (FreeBSD 5.1)
mount_ntfs /dev/ad0s1 /mnt/XP : It works.
mount_ext2fs /dev/ad0s3 /mnt/linux : /dev/ad0s3 not found (not the exact
message)
Does someone have this bug with devfs and mou
I'm writing a remote block device on FreeBSD 4.6.2
As far as the network part is rather difficult, I don't want to include it
in the kernel module. So I started coding my module with this overall
structure in mind :
- a program reads the block device.
- the module receives read and write uio re
3 matches
Mail list logo