Issue Upgrading to Larger Disks

E

erilaz

Cadet
Joined
Jan 9, 2022
Messages
2
Hello, I have performed this process in order to upgrade my disks from 3TB to 6TB drives.

1: locate the correct drive using one of the mentioned method above.
2: offline the 3Tb disk,
3: unplug the 3TB disk.
4: plug in the new 6TB disk.
5: select replace disk for the new disk.

TrueNAS resilvers the pool during the replacement process.
Repeat the process again for another disk.

The weird thing is that the GUI shows a disk that has been unplugged and is not present in the server any more.
I think that the /dev/sdf is the one who is resilvering.

I think that the "disk by uuid" is referring to the removed disk.

The fdisk -l command also mentions that.
The zpool status does show one unavailable disk ( /dev/sdf )

The server is a Dell R720 with 8X 3.5" disk slots. Controller flashed to the proper mode by the previous owner.

I hope that the system eventually will return to a full, 100% working pool, and that the "ghost disk" will disappear.

Screenshots are after the text dumps.

Code:
Last login: Sun Jan  9 17:15:15 2022 from 192.168.132.158

        TrueNAS (c) 2009-2021, iXsystems, Inc.
        All rights reserved.
        TrueNAS code is released under the modified BSD license with some
        files copyrighted by (c) iXsystems, Inc.

        For more information, documentation, help or support, go here:
        http://truenas.com
Welcome to TrueNAS

Warning: settings changed through the CLI are not written to
the configuration database and will be reset on reboot.

root@truenas[~]# zpool status -vvv                                                   pool: Mypool
 state: DEGRADED
status: One or more devices is currently being resilvered.  The pool will
        continue to function, possibly in a degraded state.
action: Wait for the resilver to complete.
  scan: resilver in progress since Sun Jan  9 13:54:23 2022
        8.24T scanned at 690M/s, 2.79T issued at 234M/s, 8.24T total
        693G resilvered, 33.84% done, 06:48:08 to go
config:

        NAME                                          STATE     READ WRITE CKSUM
        Mypool                                        DEGRADED     0     0     0
          raidz2-0                                    DEGRADED     0     0     0
            c6febe17-7fd8-43ec-9bdb-1891a17eeac6      ONLINE       0     0     0
            spare-1                                   DEGRADED     0     0     0
              replacing-0                             ONLINE       0     0     0
                14c7faaa-257b-49f4-9a5f-c458d2f84597  ONLINE       0     0     0
                f54c13a9-c655-4788-9a9f-72820381bb7e  ONLINE       0     0     0  (resilvering)
              1944838941989898340                     UNAVAIL      0     0     0  was /dev/disk/by-partuuid/1a2dedf1-7c13-449c-a263-5d9ee1c961ab
            0a447919-6db7-4182-8aee-15ee39a90ce4      ONLINE       0     0     0
            59364659-836d-46c3-a12a-948fc26f2fc3      ONLINE       0     0     0
        spares
          1a2dedf1-7c13-449c-a263-5d9ee1c961ab        UNAVAIL

errors: No known data errors

  pool: boot-pool
 state: ONLINE
status: Some supported and requested features are not enabled on the pool.
        The pool can still be used, but some features are unavailable.
action: Enable all features using 'zpool upgrade'. Once this is done,
        the pool may no longer be accessible by software that does not support
        the features. See zpool-features(7) for details.
  scan: scrub repaired 0B in 00:00:43 with 0 errors on Sun Jan  9 03:45:44 2022
config:

        NAME        STATE     READ WRITE CKSUM
        boot-pool   ONLINE       0     0     0
          mirror-0  ONLINE       0     0     0
            sdc3    ONLINE       0     0     0
            sda3    ONLINE       0     0     0

errors: No known data errors

root@truenas[~]# fdisk -l                                                         

Disk /dev/sdb: 5.46 TiB, 6001175126016 bytes, 1465130646 sectors
Disk model: HUS726060AL4210
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: BECEBEC1-408C-43D7-AC4E-781F2B81D97F

Device      Start        End    Sectors  Size Type
/dev/sdb1     128     524288     524161    2G Linux swap
/dev/sdb2  524416 1465130640 1464606225  5.5T Solaris /usr & Apple ZFS


Disk /dev/sdd: 5.46 TiB, 6001175126016 bytes, 1465130646 sectors
Disk model: HUS726060AL4210
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5CF4091A-21D9-49C1-A367-63B429BFB2C5

Device      Start        End    Sectors  Size Type
/dev/sdd1     128     524288     524161    2G Linux swap
/dev/sdd2  524416 1465130640 1464606225  5.5T Solaris /usr & Apple ZFS


Disk /dev/sde: 5.46 TiB, 6001175126016 bytes, 1465130646 sectors
Disk model: HUS726060AL4210
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 72098B14-BDED-4A1D-94CC-52BD9F7D5469

Device      Start        End    Sectors  Size Type
/dev/sde1     128     524288     524161    2G Linux swap
/dev/sde2  524416 1465130640 1464606225  5.5T Solaris /usr & Apple ZFS


Disk /dev/sdg: 5.46 TiB, 6001175126016 bytes, 1465130646 sectors
Disk model: HUS726060AL4210
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: A8E6B823-98C4-429B-9309-A40D3217DCEA

Device      Start        End    Sectors  Size Type
/dev/sdg1     128     524288     524161    2G Linux swap
/dev/sdg2  524416 1465130640 1464606225  5.5T Solaris /usr & Apple ZFS


Disk /dev/sdc: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC  WDS500G2B0A
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: 8EF9E316-BA31-4223-B57B-E303EAE2A880

Device        Start       End   Sectors   Size Type
/dev/sdc1        40      2087      2048     1M BIOS boot
/dev/sdc2      2088   1050663   1048576   512M EFI System
/dev/sdc3  34605096 976773134 942168039 449.3G Solaris /usr & Apple ZFS
/dev/sdc4   1050664  34605095  33554432    16G Linux swap

Partition table entries are not in disk order.


Disk /dev/sda: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: WDC  WDS500G2B0A
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: 7D6E2CDA-E132-41C5-8995-FF0BAB74835A

Device        Start       End   Sectors   Size Type
/dev/sda1        40      2087      2048     1M BIOS boot
/dev/sda2      2088   1050663   1048576   512M EFI System
/dev/sda3  34605096 976773134 942168039 449.3G Solaris /usr & Apple ZFS
/dev/sda4   1050664  34605095  33554432    16G Linux swap

Partition table entries are not in disk order.


Disk /dev/zd0: 300 GiB, 322122547200 bytes, 629145600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disklabel type: dos
Disk identifier: 0x29e43003

Device     Boot   Start       End   Sectors   Size Id Type
/dev/zd0p1 *       2048    999423    997376   487M 83 Linux
/dev/zd0p2      1001470 629143551 628142082 299.5G  5 Extended
/dev/zd0p5      1001472 629143551 628142080 299.5G 83 Linux

Partition 2 does not start on physical sector boundary.


Disk /dev/zd16: 300 GiB, 322122547200 bytes, 629145600 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 16384 bytes
I/O size (minimum/optimal): 16384 bytes / 16384 bytes
Disklabel type: dos
Disk identifier: 0x05edd433

Device      Boot   Start       End   Sectors   Size Id Type
/dev/zd16p1 *       2048   1026047   1024000   500M  7 HPFS/NTFS/exFAT
/dev/zd16p2      1026048 629143551 628117504 299.5G  7 HPFS/NTFS/exFAT

*this is weird, this disk has been removed*
Disk /dev/sdf: 2.73 TiB, 3000592982016 bytes, 5860533168 sectors
Disk model: ST33000650SS
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: 1936C6DA-4957-4B0B-9153-A4C5B4CF4676

Device       Start        End    Sectors  Size Type
/dev/sdf1      128    4194304    4194177    2G Linux swap
/dev/sdf2  4194432 5860533134 5856338703  2.7T Solaris /usr & Apple ZFS

Disk /dev/md127: 2 GiB, 2146963456 bytes, 524161 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

Disk /dev/mapper/md127: 2 GiB, 2146963456 bytes, 524161 sectors
Units: sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
root@truenas[~]#


Before the process:



p.jpeg


Present GUI:

p.jpeg
 
M

morganL

Captain Morgan
Administrator
Moderator
iXsystems
Joined
Mar 10, 2018
Messages
2,694
erilaz said:
Hello, I have performed this process in order to upgrade my disks from 3TB to 6TB drives.

1: locate the correct drive using one of the mentioned method above.
2: offline the 3Tb disk,
3: unplug the 3TB disk.
4: plug in the new 6TB disk.
5: select replace disk for the new disk.

TrueNAS resilvers the pool during the replacement process.
Repeat the process again for another disk.

The weird thing is that the GUI shows a disk that has been unplugged and is not present in the server any more.
I think that the /dev/sdf is the one who is resilvering.
Click to expand...

I renamed the tread so that the title is descriptive of the problem.
SCALE is young and so few people will have upgraded their systems and tested this functionality.
If you don't get a response from other users... please "report a bug"
 
You must log in or register to reply here.

Important Announcement for the TrueNAS Community.

The TrueNAS Community has now been moved. This forum will now become READ-ONLY for historical purposes. Please feel free to join us on the new TrueNAS Community Forums.

Related topics on forums.truenas.com for thread: "Issue Upgrading to Larger Disks"

Similar threads

S
Pool Created from CLI, RMA replaced via GUI, extra 2G Linux swap created on replacement drive, the larger partition is smaller than other pool members
Replies
3
Views
2K
Sgt_Bizkit
S
H
Unable to Import Pool After Reboot
Replies
0
Views
1K
hootyhoot
H
A
SAS drives off an LSI 9211 not detected by fdisk/lsblk but visible to WebUI & smartctl
Replies
1
Views
2K
aean
A
ctag
Migrating to Scale breaks the boot pool
Replies
4
Views
2K
ctag
ctag
waldauf
SOLVED Problem with "non-unique serial numbers disks"
Replies
13
Views
7K
waldauf
waldauf
Top