I compiled the latest gentoo-source kernels (r8) using "genkern --config". I
turned on BSD-disklabelsupport i the disklabelsection. However, gentoo still
refuses to read the disklabel from my secund harddrive (hdb), stating it has an
unknown disklabel on it.
The disklabel was created using parted, and it works fine in Knoppix. This is
not a slice, but the entire disk.
Steps to Reproduce:
1.use parted to produse bsd-disklabel
2.compile kernel with BSD-disklanbel support enabled
Noting. The kernel tells me it can not reconise the disklabel on hdb
Read the disklabel and give me the my partisions so I can mount them like
I compiled useing genkern
Can we have some sort of .config please?
Created attachment 20942 [details]
The .config in /usr/src/linux
What command refuses to read the disklabel? Remember that you have UFS support compiled in as a module so you'll need to add "ufs" to your modules.autoload.d or run "modprobe ufs" to access UFS filesystems.
What command refuses to read the disklabel?
Comands? Isnt the disklabel supposed to be recognized at boot? dmesg tells me it does not reconice the disklabel of hdb:
/dev/ide/host0/bus0/target0/lun0: p1 p2 p3 p4 < p5 p6 p7 >
/dev/ide/host0/bus0/target1/lun0: unknown partition table
> Remember that you have UFS support compiled in as a module
The hardisk contains a ext3 filesystem, not a UFS filesystem
Can you see if you get the same effect with vanilla-sources-2.4.20?
I culd not find vanilla-sources-2.4.20, however I configured and installed vanilla-sources-2.4.23. I still have the same problem.
We can't do that much if you continue to get this in a recent vanilla kernel. Can I suggest taking this problem to the LKML. An alternative is to try a 2.6x kernel and see if that gives you the same problem.
I have tryed using the 2.6 kernel, the same problem appears. I have taken youre advice and taken it to the LKML. (http://lkml.org/lkml/2004/4/21/170)
The solution for this is to add support for the BSD filesystem (UFS), even if the harddisk with the BSD-disklabel only contains a ext3-filesystem.
Dont ask my why (perhaps code belonging in BSD-disklabel placed in UFS?), but it appears to be the only working solution.