Re: Problem with umass/scsibus/wd0
Well, the power adapter cable arrived today but it doesn't solve the problem. With 'scsictl sd0 start' and 'dkctl sd0 makewedges' it works fine, so I'm moving on to finding something to address the display problem. Thanks for all the help so far. On Wed, 13 Mar 2024, Paul Goyette wrote: On Wed, 13 Mar 2024, Michael van Elst wrote: On Tue, Mar 12, 2024 at 11:00:02PM -0700, Paul Goyette wrote: ``scsictl sd0 start'' makes a little bit of progress, and claims to be "fabricating a geometry". ``gpt show -a sd0'' shows two partitions (one for NetBSD backups, and one for Windoze backups) # gpt show sd0 startsize index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 342014 Unused 2048 4294967296 1 GPT part - NetBSD FFSv1/FFSv2 4294969344 3518951424 2 GPT part - Windows basic data 7813920768 49119 Unused 7813969887 32 Sec GPT table 7813969919 1 Sec GPT header That looks fine. But it does not seem to progress to the discover-wedges process, and no wedges seem to exist: # dkctl sd0 listwedges /dev/rsd0: no wedges configured The wedge autodetection happens when the device attaches (and failed since the disk was offline). This is different from disklabels that are fetched by the first opener (and are usually dropped with the last close, except traditionally for vnd). You can manually trigger autodetection with dkctl sd0 makewedges Yup, that's the magic word. I used scsictl and dkctl both, and the external drive appeears normal. Thanks! +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+ !DSPAM:65f231e1156131740011365! +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+
Re: Problem with umass/scsibus/wd0
On Wed, 13 Mar 2024, Michael van Elst wrote: On Tue, Mar 12, 2024 at 11:00:02PM -0700, Paul Goyette wrote: ``scsictl sd0 start'' makes a little bit of progress, and claims to be "fabricating a geometry". ``gpt show -a sd0'' shows two partitions (one for NetBSD backups, and one for Windoze backups) # gpt show sd0 startsize index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 342014 Unused 2048 4294967296 1 GPT part - NetBSD FFSv1/FFSv2 4294969344 3518951424 2 GPT part - Windows basic data 7813920768 49119 Unused 7813969887 32 Sec GPT table 7813969919 1 Sec GPT header That looks fine. But it does not seem to progress to the discover-wedges process, and no wedges seem to exist: # dkctl sd0 listwedges /dev/rsd0: no wedges configured The wedge autodetection happens when the device attaches (and failed since the disk was offline). This is different from disklabels that are fetched by the first opener (and are usually dropped with the last close, except traditionally for vnd). You can manually trigger autodetection with dkctl sd0 makewedges Yup, that's the magic word. I used scsictl and dkctl both, and the external drive appeears normal. Thanks! +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+
Re: Problem with umass/scsibus/wd0
On Tue, Mar 12, 2024 at 11:00:02PM -0700, Paul Goyette wrote: > > ``scsictl sd0 start'' makes a little bit of progress, and claims > to be "fabricating a geometry". ``gpt show -a sd0'' shows two > partitions (one for NetBSD backups, and one for Windoze backups) > > # gpt show sd0 > startsize index contents > 0 1 PMBR > 1 1 Pri GPT header > 2 32 Pri GPT table > 342014 Unused > 2048 4294967296 1 GPT part - NetBSD FFSv1/FFSv2 > 4294969344 3518951424 2 GPT part - Windows basic data > 7813920768 49119 Unused > 7813969887 32 Sec GPT table > 7813969919 1 Sec GPT header That looks fine. > But it does not seem to progress to the discover-wedges process, > and no wedges seem to exist: > > # dkctl sd0 listwedges > /dev/rsd0: no wedges configured The wedge autodetection happens when the device attaches (and failed since the disk was offline). This is different from disklabels that are fetched by the first opener (and are usually dropped with the last close, except traditionally for vnd). You can manually trigger autodetection with dkctl sd0 makewedges Greetings, -- Michael van Elst Internet: mlel...@serpens.de "A potential Snark may lurk in every tree."
Re: Problem with umass/scsibus/wd0
On Tue, 12 Mar 2024, Paul Goyette wrote: On Wed, 13 Mar 2024, Simon Burge wrote: Not enough USB power? Same model external drive: https://forums.tomshardware.com/threads/2tb-wd-elements-2621-is-detected-on-one-of-my-computers-but-not-the-other.3720369/#post-22432202 Certainly a possibility. But I wouldn't have a clue on how to fix it. Ah, /i read further and found the links to Amazon. The new box _should_ have enuf power since it is USB3.2. But considering the price, I ordered a cable. I'll report results next week (I don't have Amazon Prime, so shipping takes a couple additional days!) +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+
Re: Problem with umass/scsibus/wd0
On Wed, 13 Mar 2024, Simon Burge wrote: Not enough USB power? Same model external drive: https://forums.tomshardware.com/threads/2tb-wd-elements-2621-is-detected-on-one-of-my-computers-but-not-the-other.3720369/#post-22432202 Certainly a possibility. But I wouldn't have a clue on how to fix it. +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+
Re: Problem with umass/scsibus/wd0
On Wed, 13 Mar 2024, Michael van Elst wrote: Sounds like that drive isn't spinning up. The "Elements" product doesn't exactly tell what it is, some units either come with their own power supply or require non-standard USB power. The device is pretty standard. One thing I forgot to mention in the original report is that it used to work just fine with NetBSD on the old build. Maybe 'scsictl sd0 start' helps to get the disk online. If that has an effect you may need 'dkctl sd0 makewedges' if you use a GPT label. ``scsictl sd0 start'' makes a little bit of progress, and claims to be "fabricating a geometry". ``gpt show -a sd0'' shows two partitions (one for NetBSD backups, and one for Windoze backups) # gpt show sd0 startsize index contents 0 1 PMBR 1 1 Pri GPT header 2 32 Pri GPT table 342014 Unused 2048 4294967296 1 GPT part - NetBSD FFSv1/FFSv2 4294969344 3518951424 2 GPT part - Windows basic data 7813920768 49119 Unused 7813969887 32 Sec GPT table 7813969919 1 Sec GPT header But it does not seem to progress to the discover-wedges process, and no wedges seem to exist: # dkctl sd0 listwedges /dev/rsd0: no wedges configured +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+
Re: Problem with umass/scsibus/wd0
Michael van Elst wrote: > p...@whooppee.com (Paul Goyette) writes: > > >[ 29641.773703] umass0 at uhub11 port 4 configuration 1 interface 0 > >[ 29641.773703] umass0: Western Digital (0x1058) Elements 2621 (0x2621), rev > >3.20/10.34, addr 4 > >[ 29641.773703] umass0: using SCSI over Bulk-Only > >[ 29641.793714] scsibus0 at umass0: 2 targets, 1 lun per target > >[ 29641.793714] sd0 at scsibus0 target 0 lun 0: > >disk fixed > >[ 29641.793714] sd0(umass0:0:0:0): Check Condition on CDB: 0x00 00 00 00 00 > >00 > >[ 29641.793714] SENSE KEY: Not Ready > >[ 29641.793714] ASC/ASCQ: Logical Unit Is In Process Of Becoming Ready > >[ 29641.793714] sd0: drive offline > > > Sounds like that drive isn't spinning up. > > The "Elements" product doesn't exactly tell what it is, some units > either come with their own power supply or require non-standard > USB power. Not enough USB power? Same model external drive: https://forums.tomshardware.com/threads/2tb-wd-elements-2621-is-detected-on-one-of-my-computers-but-not-the-other.3720369/#post-22432202 Cheers, Simon.
Re: Problem with umass/scsibus/wd0
p...@whooppee.com (Paul Goyette) writes: >[ 29641.773703] umass0 at uhub11 port 4 configuration 1 interface 0 >[ 29641.773703] umass0: Western Digital (0x1058) Elements 2621 (0x2621), rev >3.20/10.34, addr 4 >[ 29641.773703] umass0: using SCSI over Bulk-Only >[ 29641.793714] scsibus0 at umass0: 2 targets, 1 lun per target >[ 29641.793714] sd0 at scsibus0 target 0 lun 0: disk >fixed >[ 29641.793714] sd0(umass0:0:0:0): Check Condition on CDB: 0x00 00 00 00 00 00 >[ 29641.793714] SENSE KEY: Not Ready >[ 29641.793714] ASC/ASCQ: Logical Unit Is In Process Of Becoming Ready >[ 29641.793714] sd0: drive offline Sounds like that drive isn't spinning up. The "Elements" product doesn't exactly tell what it is, some units either come with their own power supply or require non-standard USB power. Maybe 'scsictl sd0 start' helps to get the disk online. If that has an effect you may need 'dkctl sd0 makewedges' if you use a GPT label.
Problem with umass/scsibus/wd0
On my new build, I finally got my monitor/display issues resolved, so today I turned to making my usual off-line backup. For several years I've used an external USB-driven hard-drive for the backups, but now when I try to attach the external drive, it never comes ready: [ 29641.773703] umass0 at uhub11 port 4 configuration 1 interface 0 [ 29641.773703] umass0: Western Digital (0x1058) Elements 2621 (0x2621), rev 3.20/10.34, addr 4 [ 29641.773703] umass0: using SCSI over Bulk-Only [ 29641.793714] scsibus0 at umass0: 2 targets, 1 lun per target [ 29641.793714] sd0 at scsibus0 target 0 lun 0: disk fixed [ 29641.793714] sd0(umass0:0:0:0): Check Condition on CDB: 0x00 00 00 00 00 00 [ 29641.793714] SENSE KEY: Not Ready [ 29641.793714] ASC/ASCQ: Logical Unit Is In Process Of Becoming Ready [ 29641.793714] sd0: drive offline ... [ 29671.778736] sd0: detached [ 29671.778736] scsibus0: detached [ 29671.778736] umass0: detached [ 29671.778736] umass0: at uhub11 port 4 (addr 4) disconnected I've waited patiently for the situation to resolve (in one case, I waited for several hours) but the drive never comes ready. And I've also tried numerous usb ports, all with the same result. The drive still works on my Windoze laptop with no issues. I cannot try any other NetBSD systems - I only have one. This is on a GENERIC 10.99.10 NetBSD built locally from sources updated ``Sun Mar 3 23:26:30 UTC 2024''. And here is the provenance of the usb port. (They're all pretty much the same, as this machine has only xhci controllers.) [ 1.039673] usb4 at xhci2: USB revision 3.1 [ 2.045963] uhub4 at usb4: NetBSD (0x) xHCI root hub (0x), class 9/0, rev 3.00/1.00, addr 0 [ 2.605967] uhub11 at uhub4 port 5: ASUS TEK. (0x174c) ASM107x (0x3074), class 9/0, rev 3.00/0.01, addr 1 Anyone got any suggestions? +-+--+--+ | Paul Goyette (.sig) | PGP Key fingerprint: | E-mail addresses:| | (Retired) | 1B11 1849 721C 56C8 F63A | p...@whooppee.com| | Software Developer | 6E2E 05FD 15CE 9F2D 5102 | pgoye...@netbsd.org | | & Network Engineer | | pgoyett...@gmail.com | +-+--+--+
