[Wilfried.Weissmann@gmx.at: Bug#277534: hal: harddisk partition scan does not check harddisk size]

[Kay Sievers]

On Wed, Oct 20, 2004 at 09:51:58PM +0200, Sjoerd Simons wrote:
> 
>   Got the mail below from a debian user. The volume_id code in debian's
>   0.2.98-3 is the same as the one in upstream's 0.4.0.. 
> 
> ----- Forwarded message from Wilfried Weissmann <Wilfried.Weissmann at gmx.at> -----
> Package: hal
> Version: 0.2.98-3
> Severity: important
> 
> I have debian installed on a raid-0 volume of one of those lowcost pseudo
> hardware raid controllers (Highpoint-Tech HPT370A). I do not use the
> binary kernel module from HPT to run the controller with linux, but
> instead I use the devicemapper/EVMS to setup the raid volumes.
> The problem is that the partition table (of the raid volume) that is
> stored on the first disk at the usual place (sector 2 I think) is
> picked by the hald-daemon. The partition table contains illegal offsets
> for the single non-raid disk of course. hald does not stop at this point
> but starts to scan the harddisk and makes the kernel puke ide erros:
> 
> Oct 19 20:18:58 tbird kernel: hdg: 0 bytes in FIFO
> Oct 19 20:18:58 tbird kernel: hdg: timeout waiting for DMA
> Oct 19 20:18:58 tbird kernel: hdg: dma_intr: status=0x51 { DriveReady
> SeekComplete Error }
> Oct 19 20:18:58 tbird kernel: hdg: dma_intr: error=0x10 {
> SectorIdNotFound }, LBAsect=160071496, se
> ctor=160071496

Hi Wilfried,
thanks for the report.  Is it possible to get a
  hald --daemon=no --verbose=yes

debug output? It would be nice to know, what exactly is going on here.

Kay
_______________________________________________
hal mailing list
hal at freedesktop.org
http://freedesktop.org/mailman/listinfo/hal