Ancestors

Toot

Written by Chris1776 on 2024-12-13 at 15:01

My SSD with windows 10 on it died, but before chatgpt pronounced it dead and entered the light, it renounced its sins to receive absolution. It remembered it was born as zfs pool. Amen.

Subtitle: if you reformat a disk for windows, clear the zfs label.

What happened? Windows does not boot, bios cant find efi entry. I want to check with cfdisk and gparted and it cant open the ssd because it suddenly is a zfs pool.

root /home/chris: fdisk -l /dev/sdb

Disk /dev/sdb: 223.57 GiB, 240057409536 bytes, 468862128 sectors

Disk model: SanDisk SSD PLUS

Units: sectors of 1 * 512 = 512 bytes

Sector size (logical/physical): 512 bytes / 512 bytes

I/O size (minimum/optimal): 512 bytes / 512 bytes

Disklabel type: gpt

Disk identifier: -----

Device Start End Sectors Size Type

/dev/sdb1 2048 206847 204800 100M EFI System

/dev/sdb2 206848 239615 32768 16M Microsoft reserved

/dev/sdb3 239616 467756586 467516971 222.9G Microsoft basic data

/dev/sdb4 467757056 468858879 1101824 538M Windows recovery environment

root /mnt: zdb -l /dev/sdb

failed to unpack label 0

failed to unpack label 1

LABEL 2 (Bad label cksum)

version: 5000

name: 'rpool'  

dmesg:

[ 45.428705] Buffer I/O error on dev sdb4, logical block 15, async page read

[ 45.428815] Buffer I/O error on dev sdb1, logical block 2, async page read

Now this disk is like 10 years old and was fine for 5 years after I reformatted it for windows. Maybe having NTFS partitions and a zpool label gave it split personality.

Lesson learned, back then I didnt know much how zfs works.

=> More informations about this toot | More toots from Chris1776@bsd.cafe

Descendants