Question I can't solve the problem IBM 528 to 512 ?

Apr 19, 2024
1
0
10
I have an IBM System x3250 M4

I purchased the 2 discs you see in the images. I hope image is clear.




Lines of code I tried;
Home · ahouston/setblocksize Wiki (I tried, it didn't work)
sg_format --format --size=512 /dev/sg2 ( I tried, it didn't work)
GitHub - Drive-Trust-Alliance/sedutil: DTA sedutil Self encrypting drive software (I tried, it didn't work)
sudo sg_format --format -v --size=4096 (I tried, it didn't work)
sg_format -F -F -F (I tried, it didn't work)


Code:
root@hpe:~# sg_format -v --format --size=512 /dev/sg1

IBM-SSG IBM-SSGSSVK3P2 6214 peripheral_type: disk [0x0]

PROTECT=0

Unit serial number: ZAM155MQ0000822150Z3

LU name: 5000c50030209c8c

mode sense(10) cdb: [5a 00 01 00 00 00 00 00 fc 00]

Mode Sense (block descriptor) data, prior to changes:

block count maxed out, set <<longlba>>

mode sense(10) cdb: [5a 10 01 00 00 00 00 00 fc 00]

<<< longlba flag set (64 bit lba) >>>

Number of blocks=6061802635 [0x1694fc48b]

Block size=528 [0x210]

mode select(10) cdb: [55 11 00 00 00 00 00 00 24 00]

mode select(10):

Descriptor format, current; Sense key: Illegal Request

Additional sense: Invalid field in parameter list

Descriptor type: Sense key specific: Field pointer:

Error in Data parameters: byte 21 bit 7

Descriptor type: Field replaceable unit code: 0x11

Descriptor type: Vendor specific [0x80]

00 00 05 26 00 11 ff ff ff ff 00 00 00 00

Try MODE SELECT again with SP=0 this time

mode select(10) cdb: [55 10 00 00 00 00 00 00 24 00]

mode select(10):

Descriptor format, current; Sense key: Illegal Request

Additional sense: Invalid field in parameter list

Descriptor type: Sense key specific: Field pointer:

Error in Data parameters: byte 21 bit 7

Descriptor type: Field replaceable unit code: 0x11

Descriptor type: Vendor specific [0x80]

00 00 05 26 00 11 ff ff ff ff 00 00 00 00

MODE SELECT command: Illegal request, type: sense key, apart from Invalid opcode

 

Ralston18

Titan
Moderator
To summarize: The objective is to change the currrent block size/Bytes per sector from 528 to 512 - correct?

More information needed.

Are you able to run fsutil on the drives via Powershell and post the results?

Reference:

https://www.partitionwizard.com/partitionmagic/ntfs-cluster-size.html

Results (bold) from my computer:

Windows PowerShell
Copyright (C) Microsoft Corporation. All rights reserved.

Install the latest PowerShell for new features and improvements! https://aka.ms/PSWindows

PS C:\WINDOWS\system32> fsutil fsinfo ntfsInfo C:
NTFS Volume Serial Number : 0x624c40524c4022e1
NTFS Version : 3.1
LFS Version : 1.1
Total Sectors : 469,770,239 (224.0 GB)
Total Clusters : 58,721,279 (224.0 GB)
Free Clusters : 21,067,106 ( 80.4 GB)
Total Reserved Clusters : 5,184 ( 20.3 MB)
Reserved For Storage Reserve : 0 ( 0.0 KB)
Bytes Per Sector : 512
Bytes Per Physical Sector : 512
Bytes Per Cluster : 4096 (4 KB)
Bytes Per FileRecord Segment : 1024
Clusters Per FileRecord Segment : 0
Mft Valid Data Length : 1.38 GB
Mft Start Lcn : 0x00000000000c0000
Mft2 Start Lcn : 0x0000000000000002
Mft Zone Start : 0x000000000160af60
Mft Zone End : 0x0000000001617780
MFT Zone Size : 200.13 MB
Max Device Trim Extent Count : 256
Max Device Trim Byte Count : 0xffffffff
Max Volume Trim Extent Count : 62
Max Volume Trim Byte Count : 0x40000000
Resource Manager Identifier : FB015E99-C60C-11E8-93EE-8CEC4B7E7ED4
PS C:\WINDOWS\system32>


No important data on the drives - correct?