[SOLVED] 'Missing' drives reported in zpool

[nicks88]

Hello all,

My server was setup with 1x1TB Western Digital hard drive (for NAS4Free installation ver 9.0.0.1.83) and 4x2TB Samsung hdd in a zfs raidz1 pool.

The other day, it appeared I had a drive failure on the 1TB Western Digital drive (BIOS kept moaning about it being in a bad state), so I replaced this with a new drive (unfortunately I did not get the opportunity to export the zpool). After installation of the latest version of NAS4free on the new drive I am experiencing the below error when trying to import the pool:

http://imgur.com/3cN1k

I've checked all cables are connected OK and tried various zpool import commands (even force), but nothing seems to work. Seems like 3 drives cannot be found. Anyone know the reason for this? Could it be a motherboard failure? I have the exact same spec secondary server, so would it be worth trying the zpool disks in there?

Many thanks for all responses

[raulfg3]

Please post your boot log and result of this command:

Code: Select all

# diskinfo -v ada1
# diskinfo -v ada2
# diskinfo -v ada3
# diskinfo -v ada0 <- if ada0 is your boot disk
# sysctl kern.geom

[nicks88]

Hi raulfg3,

Thanks for the reply - I believe you helped me over on the FreeNAS forums before, so good of you to help again!

For the boot log - do you mean that which is held in /var/log/system.log ? Here is the important bits I can find:

Code: Select all

Sep 17 17:04:13 nas4free kernel: ada0 at ahcich0 bus 0 scbus0 target 0 lun 0
Sep 17 17:04:13 nas4free kernel: ada0: <SAMSUNG HD203WI 1AN10002> ATA-8 SATA 2.x device
Sep 17 17:04:13 nas4free kernel: ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Sep 17 17:04:13 nas4free kernel: ada0: Command Queueing enabled
Sep 17 17:04:13 nas4free kernel: ada0: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Sep 17 17:04:13 nas4free kernel: ada0: Previously was known as ad4
Sep 17 17:04:13 nas4free kernel: ada1 at ahcich1 bus 0 scbus1 target 0 lun 0
Sep 17 17:04:13 nas4free kernel: ada1: <SAMSUNG HD203WI 1AN10002> ATA-8 SATA 2.x device
Sep 17 17:04:13 nas4free kernel: ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Sep 17 17:04:13 nas4free kernel: ada1: Command Queueing enabled
Sep 17 17:04:13 nas4free kernel: ada1: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Sep 17 17:04:13 nas4free kernel: ada1: Previously was known as ad6
Sep 17 17:04:13 nas4free kernel: ada2 at ahcich2 bus 0 scbus2 target 0 lun 0
Sep 17 17:04:13 nas4free kernel: ada2: <SAMSUNG HD203WI 1AN10002> ATA-8 SATA 2.x device
Sep 17 17:04:13 nas4free kernel: ada2: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Sep 17 17:04:13 nas4free kernel: ada2: Command Queueing enabled
Sep 17 17:04:13 nas4free kernel: ada2: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Sep 17 17:04:13 nas4free kernel: ada2: Previously was known as ad8
Sep 17 17:04:13 nas4free kernel: ada3 at ahcich3 bus 0 scbus3 target 0 lun 0
Sep 17 17:04:13 nas4free kernel: ada3: <SAMSUNG HD203WI 1AN10002> ATA-8 SATA 2.x device
Sep 17 17:04:13 nas4free kernel: ada3: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes)
Sep 17 17:04:13 nas4free kernel: ada3: Command Queueing enabled
Sep 17 17:04:13 nas4free kernel: ada3: 1907729MB (3907029168 512 byte sectors: 16H 63S/T 16383C)
Sep 17 17:04:13 nas4free kernel: ada3: Previously was known as ad10
Sep 17 17:04:13 nas4free kernel: ada4 at ata0 bus 0 scbus4 target 0 lun 0
Sep 17 17:04:13 nas4free kernel: ada4: <WDC WD10EADS-00L5B1 01.01A01> ATA-8 SATA 2.x device
Sep 17 17:04:13 nas4free kernel: ada4: 133.000MB/s transfers (UDMA6, PIO 8192bytes)
Sep 17 17:04:13 nas4free kernel: ada4: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C)
Sep 17 17:04:13 nas4free kernel: ada4: Previously was known as ad0

Seems like the drive mappings have become different to what was in the previous system. Here is the diskinfo bits you requested:

Code: Select all

nas4free:~# diskinfo -v ada1
ada1
        512             # sectorsize
        2000398934016   # mediasize in bytes (1.8T)
        3907029168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        3876021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        S1UYJ1BZ300370  # Disk ident.

nas4free:~# diskinfo -v ada2
ada2
        512             # sectorsize
        2000398934016   # mediasize in bytes (1.8T)
        3907029168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        3876021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        S1UYJ1BZ300362  # Disk ident.

nas4free:~# diskinfo -v ada3
ada3
        512             # sectorsize
        2000398934016   # mediasize in bytes (1.8T)
        3907029168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        3876021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        S1UYJ1BZ300364  # Disk ident.

nas4free:~# diskinfo -v ada4
ada4
        512             # sectorsize
        1000204886016   # mediasize in bytes (931G)
        1953525168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        1938021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        WD-WCAU47810435 # Disk ident.

nas4free:~# diskinfo -v ada0
ada0
        512             # sectorsize
        2000398934016   # mediasize in bytes (1.8T)
        3907029168      # mediasize in sectors
        0               # stripesize
        0               # stripeoffset
        3876021         # Cylinders according to firmware.
        16              # Heads according to firmware.
        63              # Sectors according to firmware.
        S1UYJ1BZ300366  # Disk ident.

nas4free:~#

How can I remap them to what they were before? Any help appreciated.

Many thanks!

[raulfg3]

you only need to identify physical SATA connector to ada4 & ada0 and interchange SATA Ports, when power on, the pool use the correct adax disk ( ada1,2,3,4) and your boot disk become ada0


PD: revise first that boot order in your BIOS are corect and point to 1TB disk , perhaps the problem are in the BIOS boot order section.

[nicks88]

Thanks - but still issues.

Prior to your suggestion, I had not changed BIOS hard drive boot sequence. This has not made a difference.

Also, I'm not sure swapping SATA connecting of ada4 and ada0. The reason is because my system has 4xSATA connectors (used for 4x2TB ZFS) and an IDE->SATA card which has the 1TB disk. It does not make sense to me to switch the connections - it was not like this before. All connections are the same as when the previous 1TB disk failed.

Any other suggestions I can try? (Tried lots of different boot orders).

Thanks

[raulfg3]

please try to boot from cdrom ( live Nas4free) and import your pool. if this time works fine, you can do a fresh new install and import your pool.

If none works, save your config.xml file, and using a copy to preserve original, try to edit by hand, disk section to correct disk order (if you do something wrong, you only need to replace erroneous config.xml by your previosly saved.

[raulfg3]

Any other suggestions I can try? (Tried lots of different boot orders).

you don't need to try a lot of diferent boot order, only one, make your IDE boot disk your first disk in the boot order and save bios, when done try to do a new fresh full install.

PD: boot order
1 CD-ROM
2 Disk

disk section:
1 IDE Disk of 1TB
2
3
4 the rest of SATA disk

[nicks88]

Appreciate the help, but this is still not working. I can't fully try your suggestion as I do not have the capabilities of attaching CD-ROM,1TB and 4x2TB drives in the system at one time.

Here is what I have tried:

1. Disconnected all ZFS drives
2. Made 1TB SATA->IDE drive as first in boot sequence.
3. Attached CD-ROM.
4. Made CD-ROM boot first.
5. Install NAS4free to 1TB drive (ad0)
6. Disconnected CD-ROM drive
7. Attached ZFS drive back up (cabling all same)

Still have same problems with 1TB drive switching to ad4 when all drives connected.

[nicks88]

Not sure if it helps, but in the /dev directory I have:

Code: Select all

lrwxr-xr-x  1 root  wheel            4 Sep 18 20:00 ad0 -> ada4
lrwxr-xr-x  1 root  wheel            6 Sep 18 20:00 ad0s1 -> ada4s1
lrwxr-xr-x  1 root  wheel            7 Sep 18 20:00 ad0s1a -> ada4s1a
lrwxr-xr-x  1 root  wheel            6 Sep 18 20:00 ad0s2 -> ada4s2
lrwxr-xr-x  1 root  wheel            7 Sep 18 20:00 ad0s2a -> ada4s2a
lrwxr-xr-x  1 root  wheel            4 Sep 18 20:00 ad10 -> ada3
lrwxr-xr-x  1 root  wheel            4 Sep 18 20:00 ad4 -> ada0
lrwxr-xr-x  1 root  wheel            4 Sep 18 20:00 ad6 -> ada1
lrwxr-xr-x  1 root  wheel            4 Sep 18 20:00 ad8 -> ada2

I have been reading about the glabel functionality...seems a bit drastic though.

[raulfg3]

Appreciate the help, but this is still not working. I can't fully try your suggestion as I do not have the capabilities of attaching CD-ROM,1TB and 4x2TB drives in the system at one time.

Here is what I have tried:

1. Disconnected all ZFS drives
2. Made 1TB SATA->IDE drive as first in boot sequence.
3. Attached CD-ROM.
4. Made CD-ROM boot first.
5. Install NAS4free to 1TB drive (ad0)
6. Disconnected CD-ROM drive
7. Attached ZFS drive back up (cabling all same)

Still have same problems with 1TB drive switching to ad4 when all drives connected.

try to do full install using all disk (in stept 1, DO NOT disconect all ZFS drives, if you add Disk after install your boot order changes.
you only need to be carefully when select boot drive during install menu, to choose 1TB disk and no choose one of 2TB disk.

PD : If possible for you , use a old ( and cheap and small) SATA disk to boot Nas4Free and do not use SATA2IDE converter, use of 1TB disk to boot Nas4Free is a waste of space, other possibilities are use a good USB key to install Nas4Free and save one SATA port for future use or to conect CD-ROM.

[nicks88]

The saga continues...

I have now tried:
1) Having all drives connected. (1TB and ZFS pool)
2) Creating USB bootable image of NAS4free.
3) Booting from USB and installing to 1TB drive.
4) Booting NAS4free from 1TB....same issue.

Secondly:
1) Disconnecting 1TB drive (ZFS pool still attached).
2) Booting and installing NAS4free to USB drive.
3) Booting NAS4free from USB...same issue.

Any further advice? Can't understand why this is so complicated for freebsd to automatically handle.

Thanks

[raulfg3]

1) Having all drives connected. (1TB and ZFS pool)
2) Creating USB bootable image of NAS4free.
3) Booting from USB and installing to 1TB drive.
4) Booting NAS4free from 1TB....same issue

same issue is that you can't acess to your pool?.

Do you import your previosly saved config?.

please repeat step 1, 2 and 3 , when boot in step 4 use default values (change IP if necesary, but do not load previosly saved config), and go to ZFS > Configuration > Detected > import

try was described on this post: viewtopic.php?f=16&t=1271

your pool must be detected and can be loaded and must work, if not, sorry I don't have more ideas.

If works, you need to recreate users/shares/ etc... by hand ( do not reload config.xml)

[nicks88]

Yes - it is the same issue as cannot access pool.

I have tried importing the config previously but that did not work.

I've carried out your recommendation - but still not working. Also tried as the thread you mention - but it is unable to detect the pool after importing the disks.

Tearing my hair out over this now, as I am sure it is just configuration issue. Data pool should still be valid.

Just to check it is not a motherboard issue - can I put the disks in another system and try setting up nas4free on that (then trying zpool import?). Any reason why this won't work? ZFS pool is transferrable to different hardware right?

Thanks

[raulfg3]

ZFS pool is transferrable to different hardware right?

yes, I change one time my motherboard, and other time my HD controller, and Zpools survive and can be imported.

Please do a zpool export yourpool before to do ( not necessary , but recomended).

[nicks88]

For reference, I was able to resolve this issue from advice found on the freebsd forums. Hopefully this will aide others on this forum - here's what I had to do:

Find the raid id:

Code: Select all

graid status -g

Stop the raid:

Code: Select all

graid stop <raid id>

Force import the zpool array:

Code: Select all

zpool import -f <zpool name>

Thanks