Re: Summary: GRUB installed but boot failed on Fujitsu M10-4

[Eric Snowberg]

> On Jun 5, 2019, at 9:42 AM, Sonnie Hook <address@hidden> wrote:
> 
> This is an Fujitsu M10-4 machine.

It could be we are not enumerating the disk correctly. What kind of HBA is in 
this system? 

> DVD drive is installed on rear USB. Flash disk is installed on front USB.
> 
> cdrom is an alias of 
> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden,1/address@hidden/disk
> 
> When booting from cdrom, the first lines are pasted below. I'm not sure if 
> this is a problem:
> [    1.265722] pci_sun4v: pci_iotsb_conf failed error: 6
> [    1.265754] pci_sun4v: Error creating ATU IOTSB
> [    1.265760] pci_sun4v: ATU init failed, err=6
> [    1.285642] pci_sun4v: pci_iotsb_conf failed error: 6
> [    1.285672] pci_sun4v: Error creating ATU IOTSB
> [    1.285676] pci_sun4v: ATU init failed, err=6
> [    1.306054] pci_sun4v: pci_iotsb_conf failed error: 6
> [    1.306085] pci_sun4v: Error creating ATU IOTSB
> [    1.306090] pci_sun4v: ATU init failed, err=6
> [    1.326480] pci_sun4v: pci_iotsb_conf failed error: 6
> [    1.326512] pci_sun4v: Error creating ATU IOTSB
> [    1.326517] pci_sun4v: ATU init failed, err=6
> 
> The whole installation procedure is fine. After installing GRUB on /dev/sda1, 
> I entered a shell and installed GRUB on /dev/sdb1 manually. Below are some 
> outputs of commands that might help.
> 
> # archdetect
> sparc64/sun4v_gpt                                                             
>   
> 
> # partmap /dev/sda
> gpt
> 
> # parted /dev/sda print 
> Model: LSI Logical Volume (scsi) 
> Disk /dev/sda: 599GB 
> Sector size (logical/physical): 512B/4096B
> Partition Table: gpt 
> Disk Flags: 
> 
> Number  Start   End     Size    File system     Name  Flags
>  1      1049kB  10.5MB  9437kB                     bios_grub
>  2      10.5MB  533GB   533GB   ext4
>  3      533GB   599GB   66.4GB  linux-swap(v1)
> 
> # parted /dev/sdb print
> Model: Generic Flash Disk (scsi)
> Disk /dev/sdb: 8179MB
> Sector size (logical/physical): 512B/512B
> Partition Table: gpt
> Disk Flags: 
> 
> Number  Start   End     Size    File system  Name  Flags
>  1      1049kB  30.4MB  29.4MB  ntfs               bios_grub
>  
> # mount -o bind /dev /target/dev
> # mount -o bind /proc /target/proc
> # mount -o bind /sys /target/sys
> # chroot /target
> 
> # grub-ofpathname /dev/sda1
> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden,0:a
> # grub-ofpathname /dev/sdb1
> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden,1/address@hidden,0:a
> 
> # grub-install --force-extra-removable "/dev/sdb"
> Installing for sparc64-ieee1275 platform.
> Installation finished. No error reported.
> 
> -------
> 
> {0} ok cd /packages/disk-label
> {0} ok .properties
> gpt
> supported-labels      gpt
> sun
> mbr
> name  disk-label
> 
> {0} ok boot 
> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden,0:a
> Boot device: 
> /address@hidden/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden,0:a
>   File and args: 
> 
> Can't open boot device

To find out, at this point in OBP, issue a probe-scsi-all

{0} probe-scsi-all

Please post the results.  It should return something like this:

/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden/address@hidden
  Unit 0   Removable Disk     ATA     TUSB9261

/address@hidden/address@hidden/LSI,address@hidden
Target 0
  Unit 0   Disk   LSI      MR9361-8i        4.23    Capacity 2994 GB

Select the HBA containing the disk.  In my system it would be: 

{0} “ /address@hidden/address@hidden/LSI,address@hidden select-dev

(make sure to add a space after the first “ above)

Now issue the .properties command to display the HBA information.
{0} .properties

Please post the results.

Now lets see how your HBA enumerates disks, take the Target and the Unit 
returned from probe-scsi-all and use it with the decode-unit command.  
"<target>, <unit>” decode-unit.  In my system these are both 0.

{0} “ 0,0” decode-unit encode-unit type

(make sure to add a space after the first “ above)

This will return the true canonical name for the disk. Please post the results 
for this as well.