1. Forum
  2. Usenet
  3. LINUX.DEBIAN.PORTS.SPARC

  • mkfs.ext2 - state D partitioning stops at 33% /boot

    From Mike Tremaine@21:1/5 to All on Tue Jun 23 22:40:01 2020
    On Jun 22, 2020, at 8:17 AM, Gregor Riepl <onitake@gmail.com> wrote:

    @all:
    Are there any users that had success with Promise based ATA controllers
    on UltraSPARC?

    As a matter of fact, I do. I had a software RAID running on 2 SATA disks
    on a Promise SATA300 TX4 controller and even built a custom mounting
    bracket for my old Ultra 10 to hold more than one disk.
    But, this was with Debian 4 (or thereabouts) and the sparc32 userland,
    and the boot disk was connected to the internal PATA controller.

    Not sure if this still bears much relevance.

    @Mike:
    I wonder if your problems could be an endianness issue in the Promise
    drivers. In the end, I assume these were mostly used on x86. I'd expect
    it to work with the onboard ATA controller of the Ultra 5 - at least it
    worked for me when I tried an installation on my Ultra 10 and I believe
    the hardware used in both machines is similar to identical. That it
    works with OpenBSD for you could be due to their development process
    which takes into account the specifics of many different architectures.

    If there is any relevance to my older success story, the issue may have creeped in much later than kernel 2.6.18. It could also be a 32/64-bit
    issue, as the the Debian sparc kernel was 64-bit and the userland 32-bit
    back then (as far as I remember).


    This has been solved. It was “hardware” related, sort of. I had turned of the EIDE board via setenv pcib-probe-list figuring that I was not using it and did not need it. (I also turned off the mach64 video card). Well curiously I think that
    prevents the system from being able to use DMA (I assume the IRQ never get allocated or something like that). Which causes these cards to be forced into PIO4 and not really work correctly with modern kernels.

    Here we see it correctly set up

    [ 14.063745] scsi host0: pata_pdc202xx_old
    [ 14.075370] scsi host1: pata_cmd64x
    [ 14.076299] scsi host2: pata_pdc202xx_old
    [ 14.076897] ata1: PATA max UDMA/100 cmd 0x1fe02000400 ctl 0x1fe02000408 bmdma 0x1fe02000440 irq 15
    [ 14.076914] ata2: PATA max UDMA/100 cmd 0x1fe02000410 ctl 0x1fe02000418 bmdma 0x1fe02000448 irq 15
    [ 14.087272] scsi host3: pata_cmd64x
    [ 14.088010] ata3: PATA max MWDMA2 cmd 0x1fe02c00000 ctl 0x1fe02c00008 bmdma 0x1fe02c00020 irq 13
    [ 14.088026] ata4: PATA max MWDMA2 cmd 0x1fe02c00010 ctl 0x1fe02c00018 bmdma 0x1fe02c00028 irq 13
    [ 14.090801] pata_cmd64x: active 10 recovery 10 setup 3.
    [ 14.090821] pata_cmd64x: active 10 recovery 10 setup 3.
    [ 14.240097] ata1.00: ATA-9: OWC Mercury Electra 3G SSD, R0522A0, max UDMA/133
    [ 14.240118] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 0/32)
    [ 14.264918] scsi 0:0:0:0: Direct-Access ATA OWC Mercury Elec 2A0 PQ: 0 ANSI: 5


    The install is almost done, so after I’ve played around some bits I’ll post up a more complete success with details. [Feeling dumb for banging my head against that wall for so long but oh well.]

    Thanks again for the input.

    -Mike


    <html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><
    div class="">On Jun 22, 2020, at 8:17 AM, Gregor Riepl &lt;<a href="mailto:onitake@gmail.com" class="">onitake@gmail.com</a>&gt; wrote:</div><br class="Apple-interchange-newline"><div class=""><div class=""><blockquote type="cite" class="">@all:<br class=
    "">Are there any users that had success with Promise based ATA controllers<br class="">on UltraSPARC?<br class=""></blockquote><br class="">As a matter of fact, I do. I had a software RAID running on 2 SATA disks<br class="">on a Promise SATA300 TX4
    controller and even built a custom mounting<br class="">bracket for my old Ultra 10 to hold more than one disk.<br class="">But, this was with Debian 4 (or thereabouts) and the sparc32 userland,<br class="">and the boot disk was connected to the internal
    PATA controller.<br class=""><br class="">Not sure if this still bears much relevance.<br class=""><br class=""><blockquote type="cite" class="">@Mike:<br class="">I wonder if your problems could be an endianness issue in the Promise<br class="">drivers.
    In the end, I assume these were mostly used on x86. I'd expect<br class="">it to work with the onboard ATA controller of the Ultra 5 - at least it<br class="">worked for me when I tried an installation on my Ultra 10 and I believe<br class="">the
    hardware used in both machines is similar to identical. That it<br class="">works with OpenBSD for you could be due to their development process<br class="">which takes into account the specifics of many different architectures.<br class=""></blockquote><
    br class="">If there is any relevance to my older success story, the issue may have<br class="">creeped in much later than kernel 2.6.18. It could also be a 32/64-bit<br class="">issue, as the the Debian sparc kernel was 64-bit and the userland 32-bit<br
    class="">back then (as far as I remember).<br class=""></div></div></blockquote></div><br class=""><div class=""><br class=""></div><div class="">This has been solved. It was “hardware” related, sort of. I had turned of the EIDE board via &nbsp;
    setenv pcib-probe-list &nbsp;figuring that I was not using it and did not need it. (I also turned off the mach64 video card). Well curiously I think that prevents the system from being able to use DMA (I assume the IRQ never get allocated or something
    like that). Which causes these cards to be forced into PIO4 and not really work correctly with modern kernels.&nbsp;</div><div class=""><br class=""></div><div class="">Here we see it correctly set up</div><div class=""><br class=""></div><div class=""><
    div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.063745] scsi host0: pata_pdc202xx_old</span></div><div style="
    margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.075370] scsi host1: pata_cmd64x</span></div><div style="margin: 0px;
    font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.076299] scsi host2: pata_pdc202xx_old</span></div><div style="margin: 0px; font-
    stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.076897] ata1: PATA max UDMA/100 cmd 0x1fe02000400 ctl 0x1fe02000408 bmdma 0x1fe02000440
    irq 15</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.076914] ata2: PATA max UDMA/100 cmd
    0x1fe02000410 ctl 0x1fe02000418 bmdma 0x1fe02000448 irq 15</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[
    &nbsp; 14.087272] scsi host3: pata_cmd64x</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.088010]
    ata3: PATA max MWDMA2 cmd 0x1fe02c00000 ctl 0x1fe02c00008 bmdma 0x1fe02c00020 irq 13</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-
    common-ligatures" class="">[ &nbsp; 14.088026] ata4: PATA max MWDMA2 cmd 0x1fe02c00010 ctl 0x1fe02c00018 bmdma 0x1fe02c00028 irq 13</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family: Menlo;"
    class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.090801] pata_cmd64x: active 10 recovery 10 setup 3.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-family:
    Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.090821] pata_cmd64x: active 10 recovery 10 setup 3.</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px; line-height: normal; font-
    family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.240097] ata1.00: ATA-9: OWC Mercury Electra 3G SSD, R0522A0, max UDMA/133</span></div><div style="margin: 0px; font-stretch: normal; font-size: 14px;
    line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.240118] ata1.00: 234441648 sectors, multi 1: LBA48 NCQ (depth 0/32)</span></div><div style="margin: 0px; font-stretch:
    normal; font-size: 14px; line-height: normal; font-family: Menlo;" class=""><span style="font-variant-ligatures: no-common-ligatures" class="">[ &nbsp; 14.264918] scsi 0:0:0:0: Direct-Access &nbsp; &nbsp; ATA&nbsp; &nbsp; &nbsp; OWC Mercury Elec 2A0&nbsp;
    PQ: 0 ANSI: 5</span></div></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div
    class=""><span style="font-variant-ligatures: no-common-ligatures" class="">The install is almost done, so after I’ve played around some bits I’ll post up a more complete success with details. [Feeling dumb for banging my head against that wall for
    so long but oh well.]</span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class="">Thanks again for the input.</
    span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class=""><br class=""></span></div><div class=""><span style="font-variant-ligatures: no-common-ligatures" class="">-Mike</span></div><div class=""><span style="font-
    variant-ligatures: no-common-ligatures" class=""><br class=""></span></div></body></html>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Florent Nicart@21:1/5 to All on Tue Jun 30 09:10:02 2020
    Hi Mike,

    I ran into exactly the same issue on my Sun Ultra 60 with partman
    getting stuck at 33% when starting (before even accessing the partioning
    menu).

    I found that the issue was related to the RAID detection, although I had
    no RAID and the only disk installed has been zeroed with dd.

    Here is what I did :
    - boot the installer in expert mode, where every step will be accessible
    in the installer menu,
    - after the stage "load installation components" and before "disk partitionning",
    - I opened a shell where I moved into /tmp the kernel module md.so and
    the command mdadm (localized with find),
    - check that no process mdadm was running and no module md/mdraid was
    loaded,
    - close the shell,
    - carry on with the partitionning,
    - there partman gets grumpy with a big red screen saying it cannot use
    the raid software, but not angry as it carries on straight to the disk partitioning.

    Hope it helps.

    I tried to find an option to tell the installer not to use RAID with no
    success (mdadm=false nor mdraid=false did not work).
    If somebody knows a better/simpler way ...

    Best regards,
    Florent.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)