Zpool import on Raspberry Pi4

tho

tho

My previous FreeBSD server is retired. Before retirement, FreeBSD was upgraded to 14.0 and the mirrored zpool upgraded as well. Today I got my Raspberry Pi4 NAS up and running. Connected the two 2.5" SATA SSD disks with USB 3.0 to SATA cable, imported the zpool and everything seems fine. But I am not sure why zpool reports the da0 disk different compared to the da1 disk.. And my question is: is everything OK or is there an issue somewhere... Writing to zpool works as expected.. The zpool was scrubbed on the retired NAS...

zpool status
pool: backups
state: ONLINE
scan: scrub repaired 0B in 00:08:10 with 0 errors on Thu Nov 9 08:04:53 2023
config:

NAME STATE READ WRITE CKSUM
backups ONLINE 0 0 0
mirror-0 ONLINE 0 0 0
diskid/DISK-12345678DB65 ONLINE 0 0 0
da1 ONLINE 0 0 0

errors: No known data errors
$ sudo su
# geom disk list
Geom name: mmcsd0
Providers:
1. Name: mmcsd0
Mediasize: 127865454592 (119G)
Sectorsize: 512
Stripesize: 4194304
Stripeoffset: 0
Mode: r3w3e10
descr: SDHC SR128 8.6 SN 4D8640E9 MFG 11/2022 by 3 SD
ident: 4D8640E9
rotationrate: 0
fwsectors: 0
fwheads: 0

Geom name: da0
Providers:
1. Name: da0
Mediasize: 500107862016 (466G)
Sectorsize: 512
Mode: r1w1e2
descr: ASMT 2235
lunid: 5000000000000001
ident: 12345678DB65
rotationrate: unknown
fwsectors: 63
fwheads: 255

Geom name: da1
Providers:
1. Name: da1
Mediasize: 500107862016 (466G)
Sectorsize: 512
Mode: r1w1e1
descr: ASMT 2235
lunid: 5000000000000001
ident: 12345679CE96
rotationrate: unknown
fwsectors: 63
fwheads: 255
 
I would even compare the two USB-SATA dongles with "dump_all_desc"
Check to see if any differences.

usbconfig -d ugen0.0 dump_all_desc
ugen.0.0 is example here. Use your devices address.
 
From everything I am seeing the geom is identical and it is reporting same size for drives.

You have not shown output where disks are different size or did I miss that?

u-boot is residing on mmcsd0 ?
 
I think the OP means difference in disk *names*, "diskid/DISK-12345678DB65" vs "da1". Probably best to ask on the freebsd-fs mailing list. [edit:] note that this should have no effect on zpool or zfs operation.

Hint to tho: Use code or command block to show terminal output.
 
bakul said:
I think the OP means difference in disk *names*, "diskid/DISK-12345678DB65" vs "da1". Probably best to ask on the freebsd-fs mailing list. [edit:] note that this should have no effect on zpool or zfs operation.

Hint to tho: Use code or command block to show terminal output.
Click to expand...
Yes, that is correct.. Will use code next time. I am wondering why zpool reports different disk names as you point out. The two mirrored disks are connected to the Raspberry by USB 3.0 ports..

Code: 
zpool status
  pool: backups
 state: ONLINE
  scan: scrub repaired 0B in 00:08:10 with 0 errors on Thu Nov  9 08:04:53 2023
config:

    NAME                          STATE     READ WRITE CKSUM
    backups                       ONLINE       0     0     0
      mirror-0                    ONLINE       0     0     0
        diskid/DISK-12345678DB65  ONLINE       0     0     0
        da1                       ONLINE       0     0     0

errors: No known data errors
 
Suggestion: ZFS sees da1 first, for some reason, and checks the meta data. The mirror is encoded using disk IDs, so that is what will show up.
You may probably check this by first connecting da0 and then da1 when ZFS complained that the mirror is degraded. If it is the other way round then, that may be it. But I would not do that if the data is important. Not taking chances is what I do there.
 
Crivens said:
Suggestion: ZFS sees da1 first, for some reason, and checks the meta data. The mirror is encoded using disk IDs, so that is what will show up.
You may probably check this by first connecting da0 and then da1 when ZFS complained that the mirror is degraded. If it is the other way round then, that may be it. But I would not do that if the data is important. Not taking chances is what I do there.
Click to expand...
Thanks for comments, I will try to switch ports on the two SSDs and see what zpool reports after that. Next time I reboot the Pi. I might try to scrub the pool as well..
 
You must log in or register to reply here.
Back
Top