Have I inserted by SSD in upside down? Mochabin with WD Blue SA510

Hi All

I'm just checking if I've made a really silly mistake when putting an SSD in my Mochabin. I think I may have put it in upside down, but am confused because the system log still seems to be recognising the SSD, and I was previously able to access and partition it.

Looking at the Mochabin guide available here it says the SSD slot is a M.2-2280-B key socket. I've put in a WD Blue Sata SSD M.2 2280 SA510 1TB in there which I think is a B+M key SSD (as labelled in my image following).

I've inserted it on my Mochabin as per the image below.

It did previously seem to work, but has since stopped working and now I'm getting a load of log entries which I'll copy at the bottom of this post. From digging around a bit, my best guess is that I've put the SSD in upside down. That said, would you expect that it would have worked at all? I just want to confirm that I should turn it the other way up because I'm concerned that if it's some other issue and I've not got it the wrong way round, if I now turn it the other way up it might break it? For info I did take it out and put it back in again yesterday and I don't know if I put it back in the same way which is very poor drills. Any help appreciated.

Fri Jul 21 18:47:03 2023 kern.err kernel: [   62.036991] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:47:03 2023 kern.warn kernel: [   62.041401] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:47:14 2023 kern.err kernel: [   72.586963] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:47:14 2023 kern.warn kernel: [   72.591373] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:47:24 2023 kern.err kernel: [   82.776915] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:47:24 2023 kern.warn kernel: [   82.781324] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:47:59 2023 kern.err kernel: [  118.126805] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:47:59 2023 kern.err kernel: [  118.131245] ata2: reset failed, giving up
Fri Jul 21 18:48:02 2023 kern.err kernel: [  120.396782] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:48:02 2023 kern.warn kernel: [  120.401188] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:48:10 2023 kern.warn kernel: [  128.516780] ata2: limiting SATA link speed to <unknown>
Fri Jul 21 18:48:12 2023 kern.err kernel: [  130.756774] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:48:12 2023 kern.warn kernel: [  130.761181] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:48:20 2023 kern.warn kernel: [  138.756798] ata2: limiting SATA link speed to 3.0 Gbps
Fri Jul 21 18:48:22 2023 kern.err kernel: [  141.126787] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:48:22 2023 kern.warn kernel: [  141.131191] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:48:55 2023 kern.warn kernel: [  173.956779] ata2: limiting SATA link speed to 1.5 Gbps
Fri Jul 21 18:48:58 2023 kern.err kernel: [  176.316776] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:48:58 2023 kern.err kernel: [  176.321229] ata2: reset failed, giving up
Fri Jul 21 18:49:00 2023 kern.info kernel: [  178.956795] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Fri Jul 21 18:49:00 2023 kern.info kernel: [  178.974084] ata2.00: ATA-11: WD Blue SA510 M.2 2280 1000GB, 52015100, max UDMA/133
Fri Jul 21 18:49:00 2023 kern.info kernel: [  178.981766] ata2.00: 1953525168 sectors, multi 1: LBA48 NCQ (depth 32)
Fri Jul 21 18:49:00 2023 kern.info kernel: [  179.010602] ata2.00: Features: Dev-Sleep
Fri Jul 21 18:49:00 2023 kern.info kernel: [  179.028190] ata2.00: configured for UDMA/133
Fri Jul 21 18:49:00 2023 kern.notice kernel: [  179.032931] scsi 1:0:0:0: Direct-Access     ATA      WD Blue SA510 M. 5100 PQ: 0 ANSI: 5
Fri Jul 21 18:49:00 2023 kern.notice kernel: [  179.042576] sd 1:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Fri Jul 21 18:49:00 2023 kern.notice kernel: [  179.050358] sd 1:0:0:0: [sda] Write Protect is off
Fri Jul 21 18:49:00 2023 kern.debug kernel: [  179.055179] sd 1:0:0:0: [sda] Mode Sense: 00 3a 00 00
Fri Jul 21 18:49:00 2023 kern.notice kernel: [  179.060676] sd 1:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Fri Jul 21 18:49:00 2023 kern.info kernel: [  179.083743]  sda: sda1 sda2 sda3
Fri Jul 21 18:49:00 2023 kern.notice kernel: [  179.088007] sd 1:0:0:0: [sda] Attached SCSI removable disk
Fri Jul 21 18:49:03 2023 kern.err kernel: [  181.396771] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:49:03 2023 kern.warn kernel: [  181.401182] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:49:11 2023 kern.warn kernel: [  189.306776] ata2: limiting SATA link speed to 3.0 Gbps
Fri Jul 21 18:49:13 2023 kern.err kernel: [  191.676773] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:49:13 2023 kern.warn kernel: [  191.681177] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:49:21 2023 kern.warn kernel: [  199.546800] ata2: limiting SATA link speed to 1.5 Gbps
Fri Jul 21 18:49:23 2023 kern.err kernel: [  201.876800] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:49:23 2023 kern.warn kernel: [  201.881206] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:49:58 2023 kern.err kernel: [  237.036922] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:49:58 2023 kern.err kernel: [  237.041365] ata2: reset failed, giving up
Fri Jul 21 18:49:58 2023 kern.warn kernel: [  237.045405] ata2.00: disabled
Fri Jul 21 18:50:01 2023 kern.err kernel: [  239.486898] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:50:01 2023 kern.warn kernel: [  239.491319] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:50:09 2023 kern.warn kernel: [  247.556845] ata2: limiting SATA link speed to 3.0 Gbps
Fri Jul 21 18:50:11 2023 kern.err kernel: [  249.856826] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:50:11 2023 kern.warn kernel: [  249.861229] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:50:19 2023 kern.warn kernel: [  257.796775] ata2: limiting SATA link speed to 1.5 Gbps
Fri Jul 21 18:50:21 2023 kern.err kernel: [  260.126758] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:50:21 2023 kern.warn kernel: [  260.131173] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:50:57 2023 kern.err kernel: [  295.446555] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:50:57 2023 kern.err kernel: [  295.450971] ata2: reset failed, giving up
Fri Jul 21 18:50:59 2023 kern.err kernel: [  297.886535] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:50:59 2023 kern.warn kernel: [  297.890952] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:51:07 2023 kern.warn kernel: [  305.796560] ata2: limiting SATA link speed to 3.0 Gbps
Fri Jul 21 18:51:09 2023 kern.err kernel: [  308.166503] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:51:09 2023 kern.warn kernel: [  308.170914] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:51:17 2023 kern.warn kernel: [  316.026477] ata2: limiting SATA link speed to 1.5 Gbps
Fri Jul 21 18:51:20 2023 kern.err kernel: [  318.416457] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:51:20 2023 kern.warn kernel: [  318.420864] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:51:55 2023 kern.err kernel: [  353.636536] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:51:55 2023 kern.err kernel: [  353.640949] ata2: reset failed, giving up
Fri Jul 21 18:51:57 2023 kern.err kernel: [  356.016360] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:51:57 2023 kern.warn kernel: [  356.020768] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:52:05 2023 kern.warn kernel: [  364.026378] ata2: limiting SATA link speed to 3.0 Gbps
Fri Jul 21 18:52:08 2023 kern.err kernel: [  366.346333] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:52:08 2023 kern.warn kernel: [  366.350753] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:52:15 2023 kern.warn kernel: [  374.266328] ata2: limiting SATA link speed to 1.5 Gbps
Fri Jul 21 18:52:18 2023 kern.err kernel: [  376.766302] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:52:18 2023 kern.warn kernel: [  376.770716] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:52:53 2023 kern.err kernel: [  411.866227] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:52:53 2023 kern.err kernel: [  411.870668] ata2: reset failed, giving up
Fri Jul 21 18:52:55 2023 kern.err kernel: [  414.206233] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:52:55 2023 kern.warn kernel: [  414.210639] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:53:03 2023 kern.warn kernel: [  422.276208] ata2: limiting SATA link speed to 3.0 Gbps
Fri Jul 21 18:53:06 2023 kern.err kernel: [  424.536196] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:53:06 2023 kern.warn kernel: [  424.540594] ata2: reset failed (errno=-32), retrying in 8 secs
Fri Jul 21 18:53:14 2023 kern.warn kernel: [  432.506188] ata2: limiting SATA link speed to 1.5 Gbps
Fri Jul 21 18:53:16 2023 kern.err kernel: [  434.896175] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:53:16 2023 kern.warn kernel: [  434.900573] ata2: reset failed (errno=-32), retrying in 33 secs
Fri Jul 21 18:53:51 2023 kern.err kernel: [  470.106112] ata2: COMRESET failed (errno=-32)
Fri Jul 21 18:53:51 2023 kern.err kernel: [  470.110526] ata2: reset failed, giving up
Fri Jul 21 18:53:51 2023 kern.err kernel: [  470.114571] ata2: EH pending after 5 tries, giving up
Fri Jul 21 18:53:51 2023 kern.info kernel: [  470.120160] ata2.00: detaching (SCSI 1:0:0:0)
Fri Jul 21 18:53:51 2023 kern.notice kernel: [  470.156232] sd 1:0:0:0: [sda] Synchronizing SCSI cache
Fri Jul 21 18:53:51 2023 kern.info kernel: [  470.161558] sd 1:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK
Fri Jul 21 18:53:51 2023 kern.notice kernel: [  470.170929] sd 1:0:0:0: [sda] Stopping disk
Fri Jul 21 18:53:51 2023 kern.info kernel: [  470.175143] sd 1:0:0:0: [sda] Start/Stop Unit failed: Result: hostbyte=0x04 driverbyte=DRIVER_OK

It should be put with the label up.

The label also acts as a heat spreader, not many people know this but the label is a small sheet of very thin aluminium.

if it still does not work then I'm afraid the drive broke just to be sure: you can make a backup and then test it on a clean flashed build from a stable OpenWrt image.

Because maybe the firmware you currently use could have kernel regressions with the kmod drivers for the drive, I haven't seen them on stable OpenWrt images though now on (22.05.0-RC1).

Ah thanks for the reply, I'll hopefully get a chance to try it the other way up tomorrow and will cross my fingers that I haven't blown the drive. Hopefully there's some built in failsafes but that maybe just wishful thinking.

It's weird though that it seems to have worked on and off, I would have thought it just wouldn't work at all right? I was on 22.03 when it worked, have only noticed issues with it since moving onto 23.05 rc2.

1 Like

So I got around to checking which way round I'd mounted that SSD yesterday and it looks like I did have it in right, but it's missing the sticker that acts like a heat sink. It's a while back I got it, so it's perfectly possible I just took it off thinking it served no purpose. I reseated it and am still getting the same errors, both in 23.05 rc2 and 22.03.5. I've got a spare USB adaptor for it so will take it out later to check if it works when in that. If it's properly bust I have two further questions:

  1. Is not having the sticker on it likely to have caused it to overheat and break?
  2. Will that also mean that the warranty is likely void if it is bust?

Thanks very much.
Happy

Notice that the short side of the B end of the drive card has 6 pins while the M end has 5 pins. If you count the pins in the slot, it should match that.

Yes removing the sticker voids the warranty. Every one that I've seen says "Warranty Void if Removed" on the sticker.

Nightmare - although looking at their disk images online there's nothing that says it does void the warranty. I've got managed to check that disk now and it's definitely bust. Have it in a USB adaptor and managed to run a surface test via EaseUS partition tool which came up with 1000s of bad sectors so guess I'll be binning that then :frowning:

Thanks all for your help.

Happy

If I'm honest the chance it burned might be very low even if the spreader was removed but not impossible.

The reason why I say this is because 1) its slower than nvme and older gen pci-e which means less power, 2) it will probably never create so much heat like you would expect with newer generation nvme ssds, on the other hand if the device was made without the intention for this type of heat then it might break.

When I searched google it seems there are alot of people putting the ssd the opposite and nothing happened, except only on a few cheaper brands I readed some reports that it actually broke as design flaw.

What is more likely, from my point of view it could be that the drive was broken before but not detected as, you can have this also with ddr memory.

I think it's just a dodgy disk in the end. Tried it with an older version of Openwrt and still didn't work so took it out and put into a caddy to convert to USB hard drive, then attached that to a Windows 10 machine. Disk management saw it as a disk with the three partitions I'd previously put on there, then when I tried to reformat it the disk management console froze. I then tried to clean the disk using diskpart in CMD and that froze. I then downloaded EaseUS partition manager which has some surface test tool that threw up thousands of bad sectors. Although I did that I might have taken the heat sink sticker off, if what mk24 said is true about those stickers saying void if removed, I wouldn't have ignored that so I'm pretty sure it's how it came. I've also hardly used it, was going to set it up as a NAS drive but had only really got as far as using it to store snort rules, so like you say I'd be surprised if it had burnt out due to that. I'm going to raise an issue to see if I can get it replaced I think once I manage to find my receipt.

1 Like

So I raised a ticket with Western Digital who advised me to try the Western Digital Dashboard to check that disk. I did that, which showed the firmware needed an update. As soon as I did that the disk started working again. I've since re-inserted it into the Mochabin, with a 3rd part heat sink added, and it's now working with no issues at all. As a note, I have now got it formatted as ext4 instead of F2FS because I read somewhere that F2FS can struggle and corrupt with unexpected power failures. I'm not sure how true that is, but just out of caution sticking to the ext4 format for now and it will hopefully work OK. Thanks for all your suggestions.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.