blk_update_request: protection error

fahadshery

Member
Feb 13, 2021
131
8
23
42
Hi,

I upgraded from SAS2 HBA to SAS3, I can see my drives attached at the start up:
Screenshot 2021-12-21 at 23.08.57.png

I can also see them without any problems during proxmox installation:
Screenshot 2021-12-21 at 23.03.33.png

Install goes through fine but I can't access the GUI?? it just times out. why?

I also captured the following before the installer loaded:Screenshot 2021-12-21 at 23.00.41.png

What are these errors?
I didn't clean the disks before attaching them with my new backplane and 2 x SAS3 cards. So I deleted the partitions on some of them. But I still see these errors.

These SSDs were working fine without any issues with my previous SAS2 controller.
 
then I'd blame your new SAS controller ;)
 
then I'd blame your new SAS controller ;)
I did too but how do you explain the following:

I have 2 identical drives, I was able to remove the type 2 protection from one drive but unable to do it on the second??

Here is what I did:

Code:
sg_format --format --size=512 /dev/da2

After the format, it shows this:

Code:
sg_readcap -l /dev/da2
Read Capacity results:
   Protection: prot_en=0, p_type=0, p_i_exponent=0
   Logical block provisioning: lbpme=0, lbprz=0
   Last LBA=3516328367 (0xd196e9af), Number of logical blocks=3516328368
   Logical block length=512 bytes
   Logical blocks per physical block exponent=3 [so physical block length=4096 bytes]
   Lowest aligned LBA=0
Hence:
   Device size: 1800360124416 bytes, 1716957.2 MiB, 1800.36 GB

Now if I try to do the same for another drive attached to the same controller, it says its write protected??

Code:
sg_format --format --size=512 /dev/da1 -v
    HGST      HUC101818CS4205   NE02   peripheral_type: disk [0x0]
      PROTECT=1
      << supports protection information>>
      Unit serial number:         08GYSP8A
      LU name: 5000cca02c361eb4
    mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00]
Mode Sense (block descriptor) data, prior to changes:
  Number of blocks=3516328368 [0xd196e9b0]
  Block size=512 [0x200]
 
  A FORMAT UNIT will commence in 5 seconds
    ALL data on /dev/da1 will be DESTROYED
        Press control-C to abort
    Format unit cdb: [04 18 00 00 00 00]
Format unit:
Fixed format, current; Sense key: Data Protect
Additional sense: Access denied - no access rights
Format unit command: Data protect, type: sense key; write protected media?
FORMAT UNIT failed

READCAP command still shows this:
Code:
sg_readcap -l /dev/da1
Read Capacity results:
   Protection: prot_en=1, p_type=1, p_i_exponent=0 [type 2 protection]
   Logical block provisioning: lbpme=0, lbprz=0
   Last LBA=3516328367 (0xd196e9af), Number of logical blocks=3516328368
   Logical block length=512 bytes
   Logical blocks per physical block exponent=3 [so physical block length=4096 bytes]
   Lowest aligned LBA=0
Hence:
   Device size: 1800360124416 bytes, 1716957.2 MiB, 1800.36 GB

See the difference??

any other ideas?
 
might be some sort of interference with the SED (self-encrypting drive) feature - maybe there is some way to reset that via the controller firmware/tools?