<div dir="auto">Not sure if I missed it or if the Dell and the Toshiba SSD device models are not mentioned. <div dir="auto">Several threads on the Dell support site (like the link below) suggests that the Toshiba's SSD firmware must be upgraded to play nice with Dell devices. <div dir="auto">Perhaps it worth to give it a shot and check for firmware updates for your ssd?</div><div dir="auto"><br><div dir="auto"><a href="https://www.dell.com/support/kbdoc/en-us/000143451/optiplex-7460-aio-resolving-intermittent-no-boot-device-found-error-with-ssd">https://www.dell.com/support/kbdoc/en-us/000143451/optiplex-7460-aio-resolving-intermittent-no-boot-device-found-error-with-ssd</a></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 26, 2023, 5:18 PM Calvin Harrigan via Ale <<a href="mailto:ale@ale.org">ale@ale.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Not for nothing, but Dells can be fickle.<br>
The large size of the disk is likely the issue, well the BIOS on the MB <br>
is the issue.<br>
You might consider a PCI(-e) SATA card to allow for larger disk.<br>
<br>
<br>
On 10/26/2023 17:15, Steve Tynor via Ale wrote:<br>
> Understood. FWIW, this is software RAID (mdadm). I ran the system <br>
> for a week and a half with the "bad" disk removed from the array <br>
> without any errors.<br>
><br>
> The system is old, but not ancient. A Dell Precision T1700 which I <br>
> bought refurb'd in 2018. As far as I can tell from the interwebs, it <br>
> was "new" in about 2015. So about 8 years old.<br>
><br>
> Steve<br>
><br>
><br>
> On 2023-10-26 5:02 PM, Derek Atkins wrote:<br>
>> I think the question was testing with the disks that the RAID did NOT <br>
>> read<br>
>> properly, to see if it's a busted RAID controller, bad disk, or b0rked<br>
>> BIOS.<br>
>><br>
>> How old IS this system, anyways? Unless it's like 15-20 years old, it<br>
>> should read any SATA drive.<br>
>><br>
>> -derek<br>
>><br>
>> On Thu, October 26, 2023 4:43 pm, Steve Tynor via Ale wrote:<br>
>>> FWIW, I'm not having any problems, no sign of errors with the new<br>
>>> disks. So not sure what I'd expect to learn from degrading the raid to<br>
>>> a single disk as a test...?<br>
>>><br>
>>> Steve<br>
>>><br>
>>><br>
>>> On 2023-10-26 4:40 PM, Steve Litt via Ale wrote:<br>
>>>> Here's my diagnostic advice Steve,<br>
>>>><br>
>>>> My first step would be to temporarily unplug your RAID and plug in <br>
>>>> each<br>
>>>> disk as a single disk (presumably sata) and see if 1), the BIOS<br>
>>>> recognizes it and 2) if it has errors.<br>
>>>><br>
>>>> If it fails as a single disk, it's probably the disk's fault: Return<br>
>>>> it. If it succeeds, that points an accusing finger at your RAID, so<br>
>>>> troubleshoot that.<br>
>>>><br>
>>>> HTH,<br>
>>>><br>
>>>> SteveT<br>
>>>> Steve Litt<br>
>>>><br>
>>>> Autumn 2023 featured book: Rapid Learning for the 21st Century<br>
>>>> <a href="http://www.troubleshooters.com/rl21" rel="noreferrer noreferrer" target="_blank">http://www.troubleshooters.com/rl21</a><br>
>>>><br>
>>>><br>
>>>> Steve Tynor via Ale said on Thu, 26 Oct 2023 20:03:47 +0000<br>
>>>><br>
>>>>> Steve -<br>
>>>>><br>
>>>>> I backup nightly. But would definitely look deeper if I knew <br>
>>>>> what to<br>
>>>>> look for. Ideas? Here are the relevant entries out of dmesg <br>
>>>>> showing<br>
>>>>> the disk initialization: (the two new disks are ata3 and ata4). The<br>
>>>>> ACPI warnings worry me, but I don't know what to make of them.<br>
>>>>><br>
>>>>> Thanks for any advice!<br>
>>>>><br>
>>>>> Steve<br>
>>>>><br>
>>>>> ...<br>
>>>>><br>
>>>>> [ 2.132317] ACPI Warning:<br>
>>>>> [ 2.274882] usb 1-1.4: New USB device found, idVendor=1a2c,<br>
>>>>> idProduct=2124, bcdDevice= 1.10<br>
>>>>> [ 2.290169] SystemIO range 0x0000000000001C30-0x0000000000001C3F<br>
>>>>> conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL)<br>
>>>>> (20210730/utaddress-204)<br>
>>>>> [ 2.316695] usb 1-1.4: New USB device strings: Mfr=1, Product=2,<br>
>>>>> SerialNumber=0<br>
>>>>> [ 2.316696] usb 1-1.4: Product: USB Keyboard<br>
>>>>> [ 2.343626] ACPI Warning:<br>
>>>>> [ 2.370278] usb 1-1.4: Manufacturer: SEM<br>
>>>>> [ 2.397059] SystemIO range 0x0000000000001C30-0x0000000000001C3F<br>
>>>>> conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR)<br>
>>>>> [ 2.658691] e1000e: Intel(R) PRO/1000 Network Driver<br>
>>>>> [ 2.685215] (20210730/utaddress-204)<br>
>>>>> [ 2.739682] e1000e: Copyright(c) 1999 - 2015 Intel Corporation.<br>
>>>>> [ 2.739742] hid: raw HID events driver (C) Jiri Kosina<br>
>>>>> [ 2.768035] ACPI: OSL: Resource conflict; ACPI support missing <br>
>>>>> from<br>
>>>>> driver?<br>
>>>>> [ 2.768425] i801_smbus 0000:00:1f.3: SPD Write Disable is set<br>
>>>>> [ 2.768447] i801_smbus 0000:00:1f.3: SMBus using PCI interrupt<br>
>>>>> [ 2.771923] i2c i2c-0: 4/4 memory slots populated (from DMI)<br>
>>>>> [ 2.772216] i2c i2c-0: Successfully instantiated SPD at 0x50<br>
>>>>> [ 2.772495] i2c i2c-0: Successfully instantiated SPD at 0x51<br>
>>>>> [ 2.772787] i2c i2c-0: Successfully instantiated SPD at 0x52<br>
>>>>> [ 2.773064] i2c i2c-0: Successfully instantiated SPD at 0x53<br>
>>>>> [ 2.796245] e1000e 0000:00:19.0: Interrupt Throttling Rate<br>
>>>>> (ints/sec) set to dynamic conservative mode<br>
>>>>> [ 2.823893] ACPI Warning:<br>
>>>>> [ 2.928035] e1000e 0000:00:19.0 0000:00:19.0 (uninitialized):<br>
>>>>> registered PHC clock<br>
>>>>> [ 2.935646] SystemIO range 0x0000000000001C00-0x0000000000001C2F<br>
>>>>> conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL)<br>
>>>>> [ 2.964764] ahci 0000:00:1f.2: version 3.0<br>
>>>>> [ 2.993537] (20210730/utaddress-204)<br>
>>>>> [ 2.993539] ACPI Warning: SystemIO range<br>
>>>>> 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion<br>
>>>>> 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)<br>
>>>>> [ 2.993542] ACPI: OSL: Resource conflict; ACPI support missing <br>
>>>>> from<br>
>>>>> driver?<br>
>>>>> [ 2.993543] lpc_ich: Resource conflict(s) found affecting gpio_ich<br>
>>>>> [ 3.023221] ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 6 ports 6<br>
>>>>> Gbps 0xf impl SATA mode<br>
>>>>> [ 3.082964] e1000e 0000:00:19.0 eth0: (PCI Express:2.5GT/s:Width<br>
>>>>> x1) 98:90:96:b5:b7:20<br>
>>>>> [ 3.109700] ahci 0000:00:1f.2: flags: 64bit ncq pm led clo pio <br>
>>>>> slum<br>
>>>>> part ems apst<br>
>>>>> [ 3.137850] e1000e 0000:00:19.0 eth0: Intel(R) PRO/1000 Network<br>
>>>>> Connection<br>
>>>>> [ 3.144572] usbcore: registered new interface driver usbhid<br>
>>>>> [ 3.144573] usbhid: USB HID core driver<br>
>>>>> [ 3.205236] scsi host0: ahci<br>
>>>>> [ 3.222318] e1000e 0000:00:19.0 eth0: MAC: 11, PHY: 12, PBA No:<br>
>>>>> FFFFFF-0FF<br>
>>>>> [ 3.250623] scsi host1: ahci<br>
>>>>> [ 3.428072] e1000e 0000:00:19.0 eno1: renamed from eth0<br>
>>>>> [ 3.457834] scsi host2: ahci<br>
>>>>> [ 3.488978] AVX2 version of gcm_enc/dec engaged.<br>
>>>>> [ 3.520282] scsi host3: ahci<br>
>>>>> [ 3.825901] AES CTR mode by8 optimization enabled<br>
>>>>> [ 3.854425] scsi host4: ahci<br>
>>>>> [ 3.882362] hid-generic 0003:051D:0002.0001: hiddev0,hidraw0: USB<br>
>>>>> HID v1.00 Device [American Power Conversion Back-UPS NS 650M1<br>
>>>>> FW:929.a8 .D USB FW:a8 ] on usb-0000:00:1a.0-1.2/input0<br>
>>>>> [ 3.909374] scsi host5: ahci<br>
>>>>> [ 3.936308] input: SEM USB Keyboard as<br>
>>>>> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:1A2C:2124.0002/input/input2 <br>
>>>>><br>
>>>>> [ 3.991986] ata1: SATA max UDMA/133 abar m2048@0xf7c3a000 port<br>
>>>>> 0xf7c3a100 irq 31<br>
>>>>> [ 4.076231] ata2: SATA max UDMA/133 abar m2048@0xf7c3a000 port<br>
>>>>> 0xf7c3a180 irq 31<br>
>>>>> [ 4.076628] hid-generic 0003:1A2C:2124.0002: input,hidraw1: USB <br>
>>>>> HID<br>
>>>>> v1.10 Keyboard [SEM USB Keyboard] on usb-0000:00:1a.0-1.4/input0<br>
>>>>> [ 4.105275] ata3: SATA max UDMA/133 abar m2048@0xf7c3a000 port<br>
>>>>> 0xf7c3a200 irq 31<br>
>>>>> [ 4.134962] input: SEM USB Keyboard Consumer Control as<br>
>>>>> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:1A2C:2124.0003/input/input3 <br>
>>>>><br>
>>>>> [ 4.164273] ata4: SATA max UDMA/133 abar m2048@0xf7c3a000 port<br>
>>>>> 0xf7c3a280 irq 31<br>
>>>>> [ 4.226932] ata5: DUMMY<br>
>>>>> [ 4.256594] input: SEM USB Keyboard System Control as<br>
>>>>> /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:1A2C:2124.0003/input/input4 <br>
>>>>><br>
>>>>> [ 4.258139] ata6: DUMMY<br>
>>>>> [ 4.290536] hid-generic 0003:1A2C:2124.0003: input,hidraw2: USB <br>
>>>>> HID<br>
>>>>> v1.10 Device [SEM USB Keyboard] on usb-0000:00:1a.0-1.4/input1<br>
>>>>> [ 4.635750] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 300)<br>
>>>>> [ 4.669083] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)<br>
>>>>> [ 4.702111] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)<br>
>>>>> [ 4.735319] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)<br>
>>>>> [ 4.767812] ata4.00: ATAPI: PLDS DVD+/-RW DH-16AES, 3D11, max<br>
>>>>> UDMA/100 [ 4.800890] ata3.00: ATA-10: WDC WD60EFPX-68C5ZN0,<br>
>>>>> 81.00A81, max UDMA/133 [ 4.834108] ata2.00: ATA-10: WDC<br>
>>>>> WD60EFPX-68C5ZN0, 81.00A81, max UDMA/133 [ 4.865922] ata1.00:<br>
>>>>> ATA-7: Hitachi HDS721075KLA330, GK8OAB0A, max UDMA/133<br>
>>>>> [ 4.898374] ata2.00: 11721045168 sectors, multi 16: LBA48 NCQ<br>
>>>>> (depth 32), AA<br>
>>>>> [ 4.929252] ata2.00: Features: NCQ-prio<br>
>>>>> [ 4.960353] ata3.00: 11721045168 sectors, multi 16: LBA48 NCQ<br>
>>>>> (depth 32), AA<br>
>>>>> [ 4.991976] ata3.00: Features: NCQ-prio<br>
>>>>> [ 5.023484] ata1.00: ATA Identify Device Log not supported<br>
>>>>> [ 5.054211] ata1.00: 1465149168 sectors, multi 16: LBA48 NCQ <br>
>>>>> (depth<br>
>>>>> 32), AA<br>
>>>>> [ 5.084691] ata4.00: configured for UDMA/100<br>
>>>>> [ 5.117030] ata2.00: configured for UDMA/133<br>
>>>>> [ 5.146743] ata3.00: configured for UDMA/133<br>
>>>>> [ 5.176185] ata1.00: ATA Identify Device Log not supported<br>
>>>>> [ 5.204540] ata1.00: configured for UDMA/133<br>
>>>>> [ 5.232800] scsi 0:0:0:0: Direct-Access ATA Hitachi<br>
>>>>> HDS72107 AB0A PQ: 0 ANSI: 5<br>
>>>>> [ 5.261873] sd 0:0:0:0: Attached scsi generic sg0 type 0<br>
>>>>> [ 5.262102] sd 0:0:0:0: [sda] 1465149168 512-byte logical blocks:<br>
>>>>> (750 GB/699 GiB)<br>
>>>>> [ 5.290979] scsi 1:0:0:0: Direct-Access ATA WDC<br>
>>>>> WD60EFPX-68C 0A81 PQ: 0 ANSI: 5<br>
>>>>> [ 5.319705] sd 0:0:0:0: [sda] Write Protect is off<br>
>>>>> [ 5.349259] sd 1:0:0:0: Attached scsi generic sg1 type 0<br>
>>>>> [ 5.349302] sd 1:0:0:0: [sdb] 11721045168 512-byte logical blocks:<br>
>>>>> (6.00 TB/5.46 TiB)<br>
>>>>> [ 5.349305] sd 1:0:0:0: [sdb] 4096-byte physical blocks<br>
>>>>> [ 5.349311] sd 1:0:0:0: [sdb] Write Protect is off<br>
>>>>> [ 5.349312] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00<br>
>>>>> [ 5.349323] sd 1:0:0:0: [sdb] Write cache: enabled, read cache:<br>
>>>>> enabled, doesn't support DPO or FUA<br>
>>>>> [ 5.371303] sd 1:0:0:0: [sdb] Attached SCSI disk<br>
>>>>> [ 5.378885] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00<br>
>>>>> [ 5.378909] sd 0:0:0:0: [sda] Write cache: enabled, read cache:<br>
>>>>> enabled, doesn't support DPO or FUA<br>
>>>>> [ 5.408998] scsi 2:0:0:0: Direct-Access ATA WDC<br>
>>>>> WD60EFPX-68C 0A81 PQ: 0 ANSI: 5<br>
>>>>> [ 5.481357] sda: sda1 sda2 sda3<br>
>>>>> [ 5.497373] sd 2:0:0:0: Attached scsi generic sg2 type 0<br>
>>>>> [ 5.497401] sd 2:0:0:0: [sdc] 11721045168 512-byte logical blocks:<br>
>>>>> (6.00 TB/5.46 TiB)<br>
>>>>> [ 5.497403] sd 2:0:0:0: [sdc] 4096-byte physical blocks<br>
>>>>> [ 5.497407] sd 2:0:0:0: [sdc] Write Protect is off<br>
>>>>> [ 5.497408] sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00<br>
>>>>> [ 5.497413] sd 2:0:0:0: [sdc] Write cache: enabled, read cache:<br>
>>>>> enabled, doesn't support DPO or FUA<br>
>>>>> [ 5.511525] sd 2:0:0:0: [sdc] Attached SCSI disk<br>
>>>>> [ 5.526727] sd 0:0:0:0: [sda] Attached SCSI disk<br>
>>>>> [ 5.558172] scsi 3:0:0:0: CD-ROM PLDS DVD+-RW<br>
>>>>> DH-16AES 3D11 PQ: 0 ANSI: 5<br>
>>>>> [ 5.929723] sr 3:0:0:0: [sr0] scsi3-mmc drive: 48x/48x writer<br>
>>>>> dvd-ram cd/rw xa/form2 cdda tray<br>
>>>>> [ 5.956577] cdrom: Uniform CD-ROM driver Revision: 3.20<br>
>>>>> [ 6.015681] sr 3:0:0:0: Attached scsi CD-ROM sr0<br>
>>>>> [ 6.015729] sr 3:0:0:0: Attached scsi generic sg3 type 5<br>
>>>>> [ 6.092297] Console: switching to colour dummy device 80x25<br>
>>>>> [ 6.092337] i915 0000:00:02.0: vgaarb: deactivate vga console<br>
>>>>> [ 6.093630] i915 0000:00:02.0: vgaarb: changed VGA decodes:<br>
>>>>> olddecodes=io+mem,decodes=io+mem:owns=io+mem<br>
>>>>> [ 6.110969] [drm] Initialized i915 1.6.0 20201103 for 0000:00:02.0<br>
>>>>> on minor 0<br>
>>>>><br>
>>>>><br>
>>>>> On 2023-10-26 3:17 PM, Steve Litt via Ale wrote:<br>
>>>>>> If your system is this picky about individual disks, I think you've<br>
>>>>>> got a much worse problem than you think, and your problems is<br>
>>>>>> anything but solved. I'd advise to diagnose this before everything<br>
>>>>>> goes to hell in a handbasket, and for gosh sakes back up very often.<br>
>>>>>><br>
>>>>>> SteveT<br>
>>>>>><br>
>>>>>><br>
>>>>>> Steve Tynor via Ale said on Wed, 25 Oct 2023 15:55:46 +0000<br>
>>>>>><br>
>>>>>>> To follow up on how i managed to solve this... The original failed<br>
>>>>>>> drive was a WD 4T. I tried two different Toshiba drives (8T and <br>
>>>>>>> 4T)<br>
>>>>>>> and neither were recognized by the Dell BIOS. So I tried WD.<br>
>>>>>>> Their 8T was recognized by the BIOS, but its size was misidentified<br>
>>>>>>> as 0T and the kernel refused to recognize it as a valid disk. WD<br>
>>>>>>> 6T, however, worked fine. So I've build a new array with 6T WD.<br>
>>>>>>> Why the WD works and Toshiba didn't will remain a mystery. I don't<br>
>>>>>>> see anything significant in their spec sheets.<br>
>>>>>>><br>
>>>>>>> In any case, Hurray for RAID1 - I didn't lose any data and didn't<br>
>>>>>>> have to resort to backups.<br>
>>>>>>><br>
>>>>>>> Steve<br>
>>>>>>><br>
>>>>>>><br>
>>>>>>> On 2023-10-15 8:50 PM, Steve Tynor via Ale wrote:<br>
>>>>>>>> Thanks Jim. It's a software RAID via mdadm. The array was<br>
>>>>>>>> originally built with Ubuntu 18 - have kept it going through<br>
>>>>>>>> various system upgrades - now on Ubuntu 22. And you are right - I<br>
>>>>>>>> misspoke when calling it LVM RAID - if my notes are right from<br>
>>>>>>>> back then, I created it via the "full disk" partitions:<br>
>>>>>>>><br>
>>>>>>>> mdadm --create --verbose /dev/md0 --level=1 <br>
>>>>>>>> --raid-devices=2<br>
>>>>>>>> /dev/sdb1 /dev/sdc1<br>
>>>>>>>><br>
>>>>>>>> When these errors start happening, it brings the machine to its<br>
>>>>>>>> knees. Anything I can do to "repair" the array to avoid those<br>
>>>>>>>> segments? Even when the errors are happening, mdstat looks<br>
>>>>>>>> healthy:<br>
>>>>>>>><br>
>>>>>>>> ricotta:~> cat /proc/mdstat<br>
>>>>>>>> Personalities : [raid1] [linear] [multipath] [raid0] [raid6]<br>
>>>>>>>> [raid5] [raid4] [raid10]<br>
>>>>>>>> md0 : active raid1 sdc1[0] sdb1[1]<br>
>>>>>>>> 3906884608 blocks super 1.2 [2/2] [UU]<br>
>>>>>>>> bitmap: 10/30 pages [40KB], 65536KB chunk<br>
>>>>>>>><br>
>>>>>>>> unused devices: <none><br>
>>>>>>>><br>
>>>>>>>> For now I've just removed the errant disk from the array again<br>
>>>>>>>> pending inspiration...<br>
>>>>>>>><br>
>>>>>>>> Steve<br>
>>>>>>>><br>
>>>>>>>><br>
>>>>>>>> On 2023-10-15 5:47 PM, Jim Kinney wrote:<br>
>>>>>>>>> The Errors look like the raid recognized a block/segment failure<br>
>>>>>>>>> on sdb and handled it by redirects to a new location and copied<br>
>>>>>>>>> in the data from the mirror.<br>
>>>>>>>>><br>
>>>>>>>>> Is the the drive bad? Not yet. Sectors do fail in time.<br>
>>>>>>>>><br>
>>>>>>>>> But raid system specified sdb, not sdb1, so the raid subsystem is<br>
>>>>>>>>> either using the entire drive for sdb or there's a raid<br>
>>>>>>>>> controlling hardware or software that is doing the low level<br>
>>>>>>>>> hardware management and that layer needs to be worked on to<br>
>>>>>>>>> recognize the new drive. It really sounds like there's a raid<br>
>>>>>>>>> controller in there somewhere.<br>
>>>>>>>>><br>
>>>>>>>>> On Sun, Oct 15, 2023, 2:40 PM Steve Tynor via Ale <<a href="mailto:ale@ale.org" target="_blank" rel="noreferrer">ale@ale.org</a>><br>
>>>>>>>>> wrote:<br>
>>>>>>>>><br>
>>>>>>>>> And I guess one more question... I was not able to learn<br>
>>>>>>>>> much about these errors from the interwebs, but perhaps they <br>
>>>>>>>>> don't<br>
>>>>>>>>> necessarily suggest an actual drive failure but some <br>
>>>>>>>>> sort of<br>
>>>>>>>>> soft problem with the array - perhaps repartition the bad drive<br>
>>>>>>>>> and add it back to the array and hope the errors don't come back?<br>
>>>>>>>>> The errors look scary to me, but most people on this list<br>
>>>>>>>>> have a lot more sysadm chops than I do...<br>
>>>>>>>>><br>
>>>>>>>>> Oct 13 21:11:48 ricotta kernel: [714090.323895] <br>
>>>>>>>>> md/raid1:md0:<br>
>>>>>>>>> read error correct<br>
>>>>>>>>> ed (8 sectors at 7339070832 on sdb1)<br>
>>>>>>>>> Oct 13 21:12:01 ricotta kernel: [714104.108320] <br>
>>>>>>>>> md/raid1:md0:<br>
>>>>>>>>> redirecting sector<br>
>>>>>>>>> 7338806424 to other mirror: sdb1<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.347389] ata2.00:<br>
>>>>>>>>> exception Emask 0x0 SAc<br>
>>>>>>>>> t 0x140000 SErr 0x0 action 0x0<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.347501] ata2.00:<br>
>>>>>>>>> irq_stat 0x40000008<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.347558] ata2.00:<br>
>>>>>>>>> failed command: READ FP<br>
>>>>>>>>> DMA QUEUED<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.347621] <br>
>>>>>>>>> ata2.00: cmd<br>
>>>>>>>>> 60/78:90:98:5c:71/0<br>
>>>>>>>>> 1:00:b5:01:00/40 tag 18 ncq dma 192512 in<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: <br>
>>>>>>>>> [714111.347621] res<br>
>>>>>>>>> 41/40:00:88:5d:71/0<br>
>>>>>>>>> 0:00:b5:01:00/00 Emask 0x409 (media error) <F><br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.347809] ata2.00:<br>
>>>>>>>>> status: { DRDY ERR }<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.347860] ata2.00:<br>
>>>>>>>>> error: { UNC }<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.350759] ata2.00:<br>
>>>>>>>>> configured for UDMA/133<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.350801] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#18 FAILED<br>
>>>>>>>>> Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=7s<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.350811] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#18 Sense K<br>
>>>>>>>>> ey : Medium Error [current]<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.350817] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#18 Add. Se<br>
>>>>>>>>> nse: Unrecovered read error - auto reallocate failed<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.350824] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#18 CDB: Re<br>
>>>>>>>>> ad(16) 88 00 00 00 00 01 b5 71 5c 98 00 00 01 78 00 00<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.350827]<br>
>>>>>>>>> blk_update_request: I/O error, d<br>
>>>>>>>>> ev sdb, sector 7339072664 op 0x0:(READ) flags 0x0 <br>
>>>>>>>>> phys_seg 47<br>
>>>>>>>>> prio class 0<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.351018] <br>
>>>>>>>>> md/raid1:md0:<br>
>>>>>>>>> sdb1: rescheduling<br>
>>>>>>>>> sector 7338806424<br>
>>>>>>>>> Oct 13 21:12:09 ricotta kernel: [714111.351111] ata2: EH<br>
>>>>>>>>> complete Oct 13 21:12:20 ricotta kernel: [714122.174015]<br>
>>>>>>>>> md/raid1:md0: redirecting sector<br>
>>>>>>>>> 7338806424 to other mirror: sdb1<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.594981] ata2.00:<br>
>>>>>>>>> exception Emask 0x0 SAc<br>
>>>>>>>>> t 0x1000 SErr 0x0 action 0x0<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.595089] ata2.00:<br>
>>>>>>>>> irq_stat 0x40000008<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.595146] ata2.00:<br>
>>>>>>>>> failed command: READ FP<br>
>>>>>>>>> DMA QUEUED<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.595209] <br>
>>>>>>>>> ata2.00: cmd<br>
>>>>>>>>> 60/78:60:98:5c:71/0<br>
>>>>>>>>> 1:00:b5:01:00/40 tag 12 ncq dma 192512 in<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: <br>
>>>>>>>>> [714126.595209] res<br>
>>>>>>>>> 41/40:00:78:5d:71/0<br>
>>>>>>>>> 0:00:b5:01:00/00 Emask 0x409 (media error) <F><br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.603898] ata2.00:<br>
>>>>>>>>> status: { DRDY ERR }<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.608263] ata2.00:<br>
>>>>>>>>> error: { UNC }<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.615103] ata2.00:<br>
>>>>>>>>> configured for UDMA/133<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.615136] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#12 FAILED<br>
>>>>>>>>> Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=4s<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.615145] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#12 Sense K<br>
>>>>>>>>> ey : Medium Error [current]<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.615151] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#12 Add. Se<br>
>>>>>>>>> nse: Unrecovered read error - auto reallocate failed<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.615158] sd <br>
>>>>>>>>> 1:0:0:0:<br>
>>>>>>>>> [sdb] tag#12 CDB: Re<br>
>>>>>>>>> ad(16) 88 00 00 00 00 01 b5 71 5c 98 00 00 01 78 00 00<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.615162]<br>
>>>>>>>>> blk_update_request: I/O error, d<br>
>>>>>>>>> ev sdb, sector 7339072664 op 0x0:(READ) flags 0x0 <br>
>>>>>>>>> phys_seg 47<br>
>>>>>>>>> prio class 0<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.619470] <br>
>>>>>>>>> md/raid1:md0:<br>
>>>>>>>>> sdb1: rescheduling<br>
>>>>>>>>> sector 7338806424<br>
>>>>>>>>> Oct 13 21:12:24 ricotta kernel: [714126.623671] ata2: EH<br>
>>>>>>>>> complete<br>
>>>>>>>>><br>
>>>>>>>>> On 2023-10-15 3:01 PM, Steve Tynor via Ale wrote:<br>
>>>>>>>>>> Forgot to include: the original WD drives are also <br>
>>>>>>>>>> "AF", so<br>
>>>>>>>>>> I think that rules out sector size incompatibility.<br>
>>>>>>>>>><br>
>>>>>>>>>> Steve<br>
>>>>>>>>>><br>
>>>>>>>>>><br>
>>>>>>>>>> On 2023-10-15 2:16 PM, Steve Tynor via Ale wrote:<br>
>>>>>>>>>>> I'm not certain how to be sure. A quick duckduckgo <br>
>>>>>>>>>>> search<br>
>>>>>>>>>>> suggests that 4k native sector also being marketed as<br>
>>>>>>>>>>> "Advanced Format" - is that right? Looking at the Toshiba spec<br>
>>>>>>>>>>> page, I see AF listed as "Yes" for the 8T (the first drive I<br>
>>>>>>>>>>> tried) and "No" for the 4T (which also didn't work).<br>
>>>>>>>>>>><br>
>>>>>>>>>>> <a href="https://storage.toshiba.com/docs/support-docs/toshiba_n300_salessheet_english_07-27-21.pdf?Status=Master" rel="noreferrer noreferrer" target="_blank">https://storage.toshiba.com/docs/support-docs/toshiba_n300_salessheet_english_07-27-21.pdf?Status=Master</a><br>
>>>>>>>>>>><br>
>>>>>>>>>>> Steve<br>
>>>>>>>>>>><br>
>>>>>>>>>>> On 2023-10-15 2:08 PM, Robert Tweedy via Ale wrote:<br>
>>>>>>>>>>>> Hi Steve,<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> Out of curiosity, are the new drives "4K native" sector<br>
>>>>>>>>>>>> drives, and is this the same as the old drives you're<br>
>>>>>>>>>>>> replacing? If the system's old enough its BIOS might <br>
>>>>>>>>>>>> not<br>
>>>>>>>>>>>> support that & is expecting to have "512n" <br>
>>>>>>>>>>>> (512-native) or<br>
>>>>>>>>>>>> "512e" (512-emulated) sector-size drives.<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> Other than that, I'm not sure what it could be beyond<br>
>>>>>>>>>>>> being Toshiba brand (which I've personally never had good<br>
>>>>>>>>>>>> experience with, but that's only anecdotal).<br>
>>>>>>>>>>>><br>
>>>>>>>>>>>> -Robert<br>
>>>>>>>>>>>><br>
>>>>>>>>>>> _______________________________________________<br>
>>>>>>>>>>> Ale mailing list<br>
>>>>>>>>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>>>>>>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>>>>>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>>>>>>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>>>>>>>>> _______________________________________________<br>
>>>>>>>>>> Ale mailing list<br>
>>>>>>>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>>>>>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>>>>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>>>>>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>>>>>>>> _______________________________________________<br>
>>>>>>>>> Ale mailing list<br>
>>>>>>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>>>>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>>>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>>>>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>>>>>>>><br>
>>>>>>>> _______________________________________________<br>
>>>>>>>> Ale mailing list<br>
>>>>>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>>>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>>>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>>>>> SteveT<br>
>>>>>><br>
>>>>>> Steve Litt<br>
>>>>>><br>
>>>>>> Autumn 2023 featured book: Rapid Learning for the 21st Century<br>
>>>>>> <a href="http://www.troubleshooters.com/rl21" rel="noreferrer noreferrer" target="_blank">http://www.troubleshooters.com/rl21</a><br>
>>>>>> _______________________________________________<br>
>>>>>> Ale mailing list<br>
>>>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>>>> _______________________________________________<br>
>>>>> Ale mailing list<br>
>>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>>> _______________________________________________<br>
>>>> Ale mailing list<br>
>>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>> _______________________________________________<br>
>>> Ale mailing list<br>
>>> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
>>> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
>>> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
>>> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
>>><br>
>><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
> <a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org" target="_blank" rel="noreferrer">Ale@ale.org</a><br>
<a href="https://mail.ale.org/mailman/listinfo/ale" rel="noreferrer noreferrer" target="_blank">https://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" rel="noreferrer noreferrer" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>