sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[Felix Zielcke]

Hi David,

could you please have a look at this?
It's a sparc problem.

-------- Weitergeleitete Nachricht --------
> Von: Alexander Vlasov <Alexander.Vlasov@Sun.COM>
> Reply-to: Alexander Vlasov <Alexander.Vlasov@Sun.COM>,
> 538030@bugs.debian.org
> An: submit@bugs.debian.org
> Betreff: Bug#538030: grub-ieee1275 fails to install bootblock
> Datum: Wed, 22 Jul 2009 17:26:05 +0200
> 
> Package: grub-ieee1275
> Version: 1.96+20090709-1
> Severity: normal
> 
> I got a problem trying to setup grub as a bootloader on Ultra45 machine with 
> LSI SAS controller.
> 
> Namely, after installing a package I tried to run grub-install, but it failed 
> with following diagnostic message:
> 
> ---
> grub-mkdevicemap: error: Cannot open SAS PHY ID 
> '/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/phy_identifier'
> ---
> 
> I tried to create device map manually, and this message disappeared, 
> grub-install finished successfully; however boot loader is still SILO.
> 
> Regardless of device.map file, the error message above can be reproduced if 
> grub-setup being invoked with `--recheck' option.
> 
> The machine in question is Ultra45, HW info follows:
> # lspci | grep SCSI
> 0000:0b:01.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1064 PCI-X 
> Fusion-MPT SAS (rev 02)
> 
> appropriate dmesg part:
> [   57.705793] scsi0 : ioc0: LSISAS1064 A3, FwRev=01080300h, Ports=1, MaxQ=511, 
> IRQ=11
> [   57.728772] scsi 0:0:0:0: Direct-Access     ATA      HITACHI HDS7225S A94A 
> PQ: 0 ANSI: 5
> [   57.757453] Driver 'sd' needs updating - please use bus_type methods
> [   57.761410] sd 0:0:0:0: [sda] 488390625 512-byte hardware sectors: (250 
> GB/232 GiB)
> [   57.768028] sd 0:0:0:0: [sda] Write Protect is off
> [   57.771009] sd 0:0:0:0: [sda] Mode Sense: 67 00 00 08
> [   57.772982] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
> doesn't support DPO or FUA
> [   57.782675]  sda: sda1 sda2 sda3
> [   57.805259] sd 0:0:0:0: [sda] Attached SCSI disk
> 
> 
> Tho problems (error message and grub boot sector not actually installed) joined 
> in one report since I believe they're somehow related.
> 
> 
> -- System Information:
> Debian Release: squeeze/sid
>    APT prefers unstable
>    APT policy: (500, 'unstable')
> Architecture: sparc
> 
> Kernel: Linux 2.6.30-1-sparc64-smp (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages grub-ieee1275 depends on:
> ii  grub-common              1.96+20090709-1 GRand Unified Bootloader, version
> ii  libc6                    2.9-20          GNU C Library: Shared libraries
> ii  ucf                      3.0018          Update Configuration File: preserv
> 
> grub-ieee1275 recommends no packages.
> 
> Versions of packages grub-ieee1275 suggests:
> pn  genisoimage                   <none>     (no description available)
> pn  os-prober                     <none>     (no description available)
> 
> -- no debconf information



-- 
Felix Zielcke

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[David Miller]

From: Felix Zielcke <fzielcke@z-51.de>
Date: Wed, 22 Jul 2009 17:45:41 +0200

> could you please have a look at this?
> It's a sparc problem.

I won't even be close to being able to look into this until
late August as I'm currently in New York City and therefore
thousands of miles from my Sparc systems :-)

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[Robert Millan]

On Wed, Jul 22, 2009 at 05:45:41PM +0200, Felix Zielcke wrote:
> Hi David,
> 
> could you please have a look at this?
> It's a sparc problem.
> 
> -------- Weitergeleitete Nachricht --------
> > Von: Alexander Vlasov <Alexander.Vlasov@Sun.COM>
> > Reply-to: Alexander Vlasov <Alexander.Vlasov@Sun.COM>,
> > 538030@bugs.debian.org
> > An: submit@bugs.debian.org
> > Betreff: Bug#538030: grub-ieee1275 fails to install bootblock
> > Datum: Wed, 22 Jul 2009 17:26:05 +0200
> > 
> > Package: grub-ieee1275
> > Version: 1.96+20090709-1
> > Severity: normal
> > 
> > I got a problem trying to setup grub as a bootloader on Ultra45 machine with 
> > LSI SAS controller.
> > 
> > Namely, after installing a package I tried to run grub-install, but it failed 
> > with following diagnostic message:
> > 
> > ---
> > grub-mkdevicemap: error: Cannot open SAS PHY ID 
> > '/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/phy_identifier'
> > ---

I think we should make GRUB tollerant to broken device.map on sparc, like
we did for i386-pc.  But I'm not sure if this is possible.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[David Miller]

From: Robert Millan <rmh@aybabtu.com>
Date: Wed, 22 Jul 2009 19:57:49 +0200

> On Wed, Jul 22, 2009 at 05:45:41PM +0200, Felix Zielcke wrote:
>> > grub-mkdevicemap: error: Cannot open SAS PHY ID 
>> > '/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/phy_identifier'
>> > ---
> 
> I think we should make GRUB tollerant to broken device.map on sparc, like
> we did for i386-pc.  But I'm not sure if this is possible.

I'll look into this when I can next month.

But for the initial bug this user has, can we find out what lives
inside of this directory:

/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/

and if that directory doesn't exit, can they go back one directory node
at a time until something appears?

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[Felix Zielcke]

Am Mittwoch, den 22.07.2009, 11:05 -0700 schrieb David Miller:
> From: Robert Millan <rmh@aybabtu.com>
> Date: Wed, 22 Jul 2009 19:57:49 +0200
> 
> > On Wed, Jul 22, 2009 at 05:45:41PM +0200, Felix Zielcke wrote:
> >> > grub-mkdevicemap: error: Cannot open SAS PHY ID 
> >> > '/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/phy_identifier'
> >> > ---
> > 
> > I think we should make GRUB tollerant to broken device.map on sparc, like
> > we did for i386-pc.  But I'm not sure if this is possible.
> 
> I'll look into this when I can next month.
> 
> But for the initial bug this user has, can we find out what lives
> inside of this directory:
> 
> /sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/
> 
> and if that directory doesn't exit, can they go back one directory node
> at a time until something appears?

Just mail him: Alexander Vlasov <Alexander.Vlasov@Sun.COM>
but then please also CC the bug report: 538030@bugs.debian.org
You could ask then also if he wants to subscribe to grub-devel but if
not then please CC him + the bug report for everything which is
relevant.

-- 
Felix Zielcke

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[David Miller]

From: Felix Zielcke <fzielcke@z-51.de>
Date: Wed, 22 Jul 2009 20:11:44 +0200

> Just mail him: Alexander Vlasov <Alexander.Vlasov@Sun.COM>
> but then please also CC the bug report: 538030@bugs.debian.org
> You could ask then also if he wants to subscribe to grub-devel but if
> not then please CC him + the bug report for everything which is
> relevant.

OK.

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[Alexander Vlasov]

Hi,

David Miller <davem <at> davemloft.net> writes:

> But for the initial bug this user has, can we find out what lives
> inside of this directory:
> 
>
/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0
/0000:0b:01.0/host0/port-0:0/end_device-0:0/sas_device:end_device-0:0/
> 
> and if that directory doesn't exit, can they go back one directory node
> at a time until something appears?

One step back there is a directory structure:

drwxr-xr-x 3 root root    0 2009-07-23 13:52 bsg
drwxr-xr-x 3 root root    0 2009-07-23 13:52 sas_device
drwxr-xr-x 3 root root    0 2009-07-23 13:52 sas_end_device
drwxr-xr-x 3 root root    0 2009-07-23 13:52 target0:0:0
-rw-r--r-- 1 root root 8192 2009-07-23 13:52 uevent

The entire tree (ls -lR) is quite big and is available upon request.
The only trace of `real' device name (sda) is
/sys/devices/root/f0063e50/pci0000:02/0000:02:00.0/0000:03:09.0/0000:0a:00.0
/0000:0b:01.0/host0/port-0:0/end_device-0:0/target0:0:0/0:0:0:0/block/
directory, which contains one subdirectory named sda.

Re: sparc: [Fwd: Bug#538030: grub-ieee1275 fails to install bootblock]

[Felix Zielcke]

Am Mittwoch, den 22.07.2009, 08:49 -0700 schrieb David Miller:
> From: Felix Zielcke <fzielcke@z-51.de>
> Date: Wed, 22 Jul 2009 17:45:41 +0200
> 
> > could you please have a look at this?
> > It's a sparc problem.
> 
> I won't even be close to being able to look into this until
> late August as I'm currently in New York City and therefore
> thousands of miles from my Sparc systems :-)

Just a little reminder.
Are you now back?

-- 
Felix Zielcke
Proud Debian Maintainer