Jump to content

Lost drive after creating pool (v6.12)

Jaybau

By Jaybau
in General Support

Go to solution Solved by Jaybau,

Recommended Posts

Jaybau Explorer

Jaybau

Posted
Posted

I lost a drive after:

 

  1. Upgraded from 6.11.5 to 6.12.1.
  2. Removed drive from the 6.11.5 pool (I can't remember if it was called pool or cache in the previous version), named "backup".  This was my drive for temporary backups that I didn't want on the parity array or my SSD cache.
  3. Created a new 6.12.1 "Pool".
  4. Added two slots and two drives to the pool (6.12.1 pool name = "temp" and it automatically created another called "temp 2").
  5. Started the array.
  6. Had problems with the new pool, and wouldn't start.
  7. Shutdown array. (would be nice if the array was separate from pools)
  8. Removed the new pool, and put the separate drives into their original pool names (which would be a new pool).
  9. The pool with the problem drive does not start.  It is now an "Unassigned Device", no partition information, and Unraid is asking me to format the drive.

 

During the process I did not see an option to touch the drive to format/partition or do anything destructive.  I believe the data is still there.


Drive:
WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
I cannot remember which filesystem is used.

 

Log: 

Jun 23 16:27:25 Tower kernel: sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Jun 23 16:27:25 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off
Jun 23 16:27:25 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 00 00 00
Jun 23 16:27:25 Tower kernel: sd 1:0:0:0: [sda] Asking for cache data failed
Jun 23 16:27:25 Tower kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Jun 23 16:27:25 Tower kernel: sda: sda1
Jun 23 16:27:25 Tower kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Jun 23 16:28:15 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:28:15 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:28:15 Tower emhttpd: read SMART /dev/sda
Jun 23 16:32:26 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:32:26 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:32:26 Tower emhttpd: read SMART /dev/sda
Jun 23 16:32:34 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:32:34 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:32:34 Tower emhttpd: read SMART /dev/sda
Jun 23 16:35:08 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:35:08 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:35:08 Tower emhttpd: read SMART /dev/sda
Jun 23 16:35:40 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:35:40 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:35:40 Tower emhttpd: read SMART /dev/sda
Jun 23 16:35:52 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:35:52 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:35:52 Tower emhttpd: read SMART /dev/sda
Jun 23 16:36:00 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:36:00 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:36:00 Tower emhttpd: read SMART /dev/sda
Jun 23 16:36:34 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:36:34 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:36:34 Tower emhttpd: read SMART /dev/sda
Jun 23 16:36:40 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:36:40 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:36:40 Tower emhttpd: read SMART /dev/sda
Jun 23 16:36:49 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:36:50 Tower emhttpd: read SMART /dev/sda
Jun 23 16:36:57 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:36:57 Tower emhttpd: import 32 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:36:57 Tower emhttpd: read SMART /dev/sda
Jun 23 16:37:14 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:37:14 Tower emhttpd: import 32 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:37:14 Tower emhttpd: read SMART /dev/sda
Jun 23 16:37:25 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:37:25 Tower emhttpd: import 31 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:37:25 Tower emhttpd: read SMART /dev/sda
Jun 23 16:38:22 Tower emhttpd: /sbin/btrfs filesystem show /dev/sda1 2>&1
Jun 23 16:38:22 Tower emhttpd: ERROR: no btrfs on /dev/sda1
Jun 23 16:38:22 Tower emhttpd: /usr/sbin/zpool import -d /dev/sda1 2>&1
Jun 23 16:42:56 Tower emhttpd: read SMART /dev/sda
Jun 23 16:45:06 Tower emhttpd: read SMART /dev/sda
Jun 23 16:45:12 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:45:12 Tower emhttpd: import 31 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:45:13 Tower emhttpd: read SMART /dev/sda
Jun 23 16:45:55 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:45:55 Tower emhttpd: read SMART /dev/sda
Jun 23 16:46:02 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:46:02 Tower emhttpd: read SMART /dev/sda
Jun 23 16:46:22 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:46:23 Tower emhttpd: read SMART /dev/sda
Jun 23 16:46:29 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:46:29 Tower emhttpd: read SMART /dev/sda
Jun 23 16:46:34 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:46:34 Tower emhttpd: read SMART /dev/sda
Jun 23 16:46:41 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:46:41 Tower emhttpd: read SMART /dev/sda
Jun 23 16:46:57 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:46:57 Tower emhttpd: read SMART /dev/sda
Jun 23 16:47:04 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:47:04 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:47:04 Tower emhttpd: read SMART /dev/sda
Jun 23 16:47:25 Tower emhttpd: shcmd (970): /sbin/wipefs -a /dev/sda
Jun 23 16:47:25 Tower root: /dev/sda: 2 bytes were erased at offset 0x000001fe (dos): 55 aa
Jun 23 16:47:25 Tower root: /dev/sda: calling ioctl to re-read partition table: Success
Jun 23 16:47:32 Tower emhttpd: shcmd (981): mount -t xfs -o noatime,nouuid /dev/sda1 /mnt/backup
Jun 23 16:47:33 Tower root: mount: /mnt/backup: special device /dev/sda1 does not exist.
Jun 23 16:47:33 Tower kernel: /dev/sda1: Can't open blockdev
Jun 23 16:47:34 Tower emhttpd: /mnt/backup: no btrfs or device /dev/sda1 is not single
Jun 23 16:47:34 Tower emhttpd: /usr/sbin/zpool import -d /dev/sda1 2>&1
Jun 23 16:47:34 Tower emhttpd: shcmd (982): mount -t reiserfs -o noatime,user_xattr,acl /dev/sda1 /mnt/backup
Jun 23 16:47:34 Tower root: mount: /mnt/backup: special device /dev/sda1 does not exist.
Jun 23 16:49:03 Tower emhttpd: read SMART /dev/sda
Jun 23 16:49:10 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:49:10 Tower emhttpd: import 30 cache device: (sda) WDC_WD1600AAJS-08WAA0_WD-WCAS28920125
Jun 23 16:49:11 Tower emhttpd: read SMART /dev/sda
Jun 23 16:49:21 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:49:21 Tower emhttpd: read SMART /dev/sda
Jun 23 16:49:27 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 23 16:49:27 Tower emhttpd: read SMART /dev/sda
Jun 24 08:42:47 Tower kernel: sd 1:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Jun 24 08:42:47 Tower kernel: sd 1:0:0:0: [sda] Write Protect is off
Jun 24 08:42:47 Tower kernel: sd 1:0:0:0: [sda] Mode Sense: 00 00 00 00
Jun 24 08:42:47 Tower kernel: sd 1:0:0:0: [sda] Asking for cache data failed
Jun 24 08:42:47 Tower kernel: sd 1:0:0:0: [sda] Assuming drive cache: write through
Jun 24 08:42:47 Tower kernel: sd 1:0:0:0: [sda] Attached SCSI disk
Jun 24 08:42:52 Tower emhttpd: WDC_WD1600AAJS-08WAA0_WD-WCAS28920125 (sda) 512 312581808
Jun 24 08:42:52 Tower emhttpd: read SMART /dev/sda

 

 

Diagnostics attached.

 

Thank you.

 

tower-diagnostics-20230624-0856.zip

Link to comment
JorgeB Grand Master

JorgeB

Posted
Posted
17 hours ago, Jaybau said: 
Jun 23 16:47:25 Tower emhttpd: shcmd (970): /sbin/wipefs -a /dev/sda
Jun 23 16:47:25 Tower root: /dev/sda: 2 bytes were erased at offset 0x000001fe (dos): 55 aa

Drive was wiped, depending on the filesystem it may still be recoverable, start by posting the output of: 

btrfs-select-super -s 1 /dev/sda1

 

Link to comment
Jaybau Explorer

Jaybau

Posted
  • Author
Posted

  

# btrfs-select-super -s 1 /dev/sda1
ERROR: mount check: cannot open /dev/sda1: No such file or directory
ERROR: cannot check mount status: No such file or directory

# btrfs-select-super -s 1 /dev/sda
No valid Btrfs found on /dev/sda
ERROR: open ctree failed

 

Quote

Drive was wiped

 

I wonder how that happened.  I don't believe I explicitly did anything to wipe the drive.  I created a pool.  I tried adding the drive to the pool.  Started the array.  Array wouldn't start because of the drive (I didn't investigate why).  I stopped the array.  I took the drive out of the pool.  I also rebooted somewhere in those steps.

Link to comment
JorgeB Grand Master

JorgeB

Posted
Posted
1 hour ago, Jaybau said:

I don't believe I explicitly did anything to wipe the drive.

From what I can see in the syslog you assigned that disk to a pool, started array, stopped array, then assigned a different disk to the same pool without re-setting the pool, this will make Unraid wipe the previously assigned disk.

 

 

2 hours ago, Jaybau said: 
# btrfs-select-super -s 1 /dev/sda1
ERROR: mount check: cannot open /dev/sda1: No such file or directory
ERROR: cannot check mount status: No such file or directory

I forgot that since v6.12 Unraid wipes the full device, destroying the partition layout, you can try this: 

sfdisk /dev/sda

then type 64 and hit return, if that was the correct partition start sector you will see something like:
  

Partition #1 contains a btrfs (or xfs) signature.

Do you want to remove the signature? [Y]es/[N]o:

Type N plus return to keep the signature, the type 

write

and hit return again, let me know if that worked and which filesystem it was, if you don't see the signature message abort with CTRL + C and retry with 2048 instead of 64.

 

 

  • Like 1
Link to comment
Jaybau Explorer

Jaybau

Posted
  • Author
Posted
Quote

assigned a different disk to the same pool without re-setting the pool, this will make Unraid wipe the previously assigned disk.

 

Ouch.  That was too easy to do, and without warning or user confirmation. 

I'll need to figure out how to add/remove drives to a pool without wiping the existing data.

Link to comment
  • Solution
Jaybau Explorer

Jaybau

Posted
  • Author
  • Solution
Posted

This worked!  Thank you!

 

48 minutes ago, JorgeB said:

Try this: 

sfdisk /dev/sda

then type 64 and hit return, if that was the correct partition start sector you will see something like:
  

Partition #1 contains a btrfs (or xfs) signature.

Do you want to remove the signature? [Y]es/[N]o:

Type N plus return to keep the signature, the type 

write

and hit return again, let me know if that worked and which filesystem it was, if you don't see the signature message abort with CTRL + C and retry with 2048 instead of 64.

 

 

 

 

Output: 

>>> 64
Created a new DOS disklabel with disk identifier 0x81bec7f8.
Created a new partition 1 of type 'Linux' and of size 149.1 GiB.
Partition #1 contains a xfs signature.

Do you want to remove the signature? [Y]es/[N]o: N
   /dev/sda1 :           64    312581807 (149.1G) Linux
/dev/sda2: write

New situation:
Disklabel type: dos
Disk identifier: 0x81bec7f8

Device     Boot Start       End   Sectors   Size Id Type
/dev/sda1          64 312581807 312581744 149.1G 83 Linux

The partition table has been altered.
Calling ioctl() to re-read partition table.
Syncing disks.

 

Thanks again.

Link to comment
Jaybau Explorer

Jaybau

Posted
  • Author
Posted

  

# xfs_repair /dev/sda1
Phase 1 - find and verify superblock...
Phase 2 - using internal log
        - zero log...
        - scan filesystem freespace and inode maps...
        - found root inode chunk
Phase 3 - for each AG...
        - scan and clear agi unlinked lists...
        - process known inodes and perform inode discovery...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
        - process newly discovered inodes...
Phase 4 - check for duplicate blocks...
        - setting up duplicate extent list...
        - check for inodes claiming duplicate blocks...
        - agno = 0
        - agno = 1
        - agno = 2
        - agno = 3
Phase 5 - rebuild AG headers and trees...
        - reset superblock...
Phase 6 - check inode connectivity...
        - resetting contents of realtime bitmap and summary inodes
        - traversing filesystem ...
        - traversal finished ...
        - moving disconnected inodes to lost+found ...
Phase 7 - verify and correct link counts...
done

 

Drive also mounted, no issues.

 

Thank you.

  • Like 1
Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
Go to topic listing
×
×
  • Create New...