Tweet
My brand new Phoenix Pro 120GB has data on it. Is this normal for a G.Skill SSD?
# file -s /dev/sdb
/dev/sdb: x86 boot sector, code offset 0xc0, OEM-ID " м", Bytes/sector 190, sectors/cluster 124, reserved sectors 191, FATs 6, root entries 185, sectors 64514 (volumes <=32 MB) , Media descriptor 0xf3, sectors/FAT 20644, heads 6, hidden sectors 309755, sectors 2147991229 (volumes > 32 MB) , physical drive 0x7e, dos < 4.0 BootSector (0x0)
I can't remember if I checked my last G.Skill SSD (Falcon 128GB) before I used it or not. Usually, running hexdump on a new drive shows it is initialized to all zeros (Seagate, WD). This clearly isn't the case here.
# file -s /dev/sdb
/dev/sdb: x86 boot sector, code offset 0xc0, OEM-ID " м", Bytes/sector 190, sectors/cluster 124, reserved sectors 191, FATs 6, root entries 185, sectors 64514 (volumes <=32 MB) , Media descriptor 0xf3, sectors/FAT 20644, heads 6, hidden sectors 309755, sectors 2147991229 (volumes > 32 MB) , physical drive 0x7e, dos < 4.0 BootSector (0x0)
I can't remember if I checked my last G.Skill SSD (Falcon 128GB) before I used it or not. Usually, running hexdump on a new drive shows it is initialized to all zeros (Seagate, WD). This clearly isn't the case here.
Comment