blewstar Posted January 1 Share Posted January 1 Hi, I have been troubleshooting shares that disappeared until rebooted. It turned out that one of the 2 cache drives was read only. While troubleshooting this I unassigned the drives while switching them. I did not format them, but followed information to remove and start array for unraid to forget then assign them. I am at a lost of how to restore them after several hours of reading forums. I have very little experience with unraid only setting up and forgetting until I updated from version 6.9.2 to current. Think that is what caused my drive to go out. Been chasing my tail ever since. Any help appreciated Quote Link to comment
blewstar Posted January 2 Author Share Posted January 2 Here is the diagnostics. Thanks for your help blewstar-diagnostics-20240102-1639.zip Quote Link to comment
JorgeB Posted January 3 Share Posted January 3 Post the output of btrfs fi show Quote Link to comment
blewstar Posted January 3 Author Share Posted January 3 I opened up the console and entered that and there was nothing coming up. It's like pressing enter. It did think for a moment before Quote Link to comment
JorgeB Posted January 4 Share Posted January 4 That suggests the devices were wiped, and the output of: fdisk -l /dev/nvme0n1 fdisk -l /dev/nvme1n1 Quote Link to comment
blewstar Posted January 5 Author Share Posted January 5 (edited) Well, you burn and learn. Seems that info is gone. Thanks for your help. I have ordered new SSDs and will build the shares and dockers back up. Most of my info is on the array so shouldnt take me long. It taught me to make sure to review documentation and always do backups. What backup option covers shares including appdata? I thought I read flash in one place, perhaps an old thread. root@Blewstar:~# fdisk -1 /dec/nvme0n1 fdisk: invalid option -- '1' Try 'fdisk --help' for more information. root@Blewstar:~# fdisk -1 /dev/nvme0n1 fdisk: invalid option -- '1' Try 'fdisk --help' for more information. root@Blewstar:~# fdisk -1 /dev/nvme1n1 fdisk: invalid option -- '1' Try 'fdisk --help' for more information. root@Blewstar:~# fdisk help Welcome to fdisk (util-linux 2.38.1). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open help: No such file or directory root@Blewstar:~# Edited January 5 by blewstar grammer Quote Link to comment
blewstar Posted January 6 Author Share Posted January 6 Sorry, root@Blewstar:~# fdisk -l /dev/nvme0n1 Disk /dev/nvme0n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: SBX Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@Blewstar:~# fdisk -l /dev/nvme1n1 Disk /dev/nvme1n1: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors Disk model: SBX Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes root@Blewstar:~# Quote Link to comment
JorgeB Posted January 7 Share Posted January 7 There are no partitions, suggesting the devices were wiped, it may still be possible to recover them if you wan to try, but if there wasn't any important data it may be easier to start over. Quote Link to comment
blewstar Posted January 8 Author Share Posted January 8 Thank you for your help. I will start over using what I've learned from you. Quote Link to comment
Recommended Posts
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.