JasenHicks

When you say "Mounts with UD" what do you mean? The old drive was XFS - but iirc when I created the array it just did all of that automatically. When I put the new drive in, I added it in slot 6 in the array, and started it up. Did I do this wrong? Should I have formatted it as XFS first and then added it to the array?

Interesting, when the new addition finished it also gave the same issue. Running the command above gave: Phase 1 - find and verify superblock... bad primary superblock - bad magic number !!! attempting to find secondary superblock... Then the scondary superblock just ran with ..... afterwards.

Issue: Drive 6 is showing Unmountable disk present: Unsupported or no file system. Background: Moved my UNRAID server built on a 45 drives Storinator from Japan to the US. Plugged all the drives back in and booted it up, Drive 6 showed failed. Shut the system down, pulled the old drive, and put in a new Western Digital 14TB. Added it to the array as Drive 6 and UNRAID did the rebuild on it as expected. Took just about a day. Came back after work last night and now it shows the error stated above. Did a SMART check on drive 6 and it passed with no issues. Unsure what to do next. Disk 12 is an expansion drive that's in the process of being cleared and added to the array. I didn't realize Drive 6 had the error when I started the expansion! Diags: hades-diagnostics-20230630-1300.zip Any thoughts would be appreciated!

Hiya! I migrated to a new UNRAID server and for the most part, its been spot on. I have noticed that one of my shares "GOHAN" allows me to create new subfolders and save files in it, but I can't rename, delete, add, etc. to existing folders. Any idea? The folder GOHAN is set to public, shared over SMB, and I am logged in using the right username from my windows machine. hades-diagnostics-20210620-1810.zip

You are a god damn hero. Thank you! I seem to be full up round again.

Post Reboot Diags. zeus-diagnostics-20210414-0554.zip

Current.zeus-diagnostics-20210414-0540.zip

OK. Did the following. 1. Stopped the Array. 2. Unassigned all the cache drives. It wouldn't let me start the array though. 3. Reassigned the cache drives. Started up the array. 4. Now we have GREEN BUBBLES next to each cache drive but still have the "Unmountable: No File System" on the NVME drive.

Not sure why. They are all in the system. I bet I dorked something up when adding them back; just not sure what.

@JorgeB - you are the man. The only thing that seems to still need attention is my cache pool.

OMG.... rsync is doing something. @JorgeB - I could kiss you on the face right now! I'll refrain until this is done and actually works or something Seriously, let me know how I can send you something as a token of my gratitude.

Cool, just stopped the array, went into maintenance mode and ran the command. Once its done, Ill go back to non-maintenance mode and re-run the rsync.

zeus-diagnostics-20210412-2307.zip

I'm sorry for the silly questions back and forth and am truly grateful for the assistance. I re-read the post and was like "DUH" UD = Unassigned device. Ran the command: rsync -av /mnt/disks/oldSeagate/ /mnt/disk7/ Output (error) below: Linux 4.19.107-Unraid. Last login: Mon Apr 12 05:29:17 -0700 2021 on /dev/pts/0. root@Zeus:~# rsync -av /mnt/disks/oldSeagate/ /mnt/disk7/ sending incremental file list rsync: ERROR: cannot stat destination "/mnt/disk7/": Input/output error (5) rsync error: errors selecting input/output files, dirs (code 3) at main.c(642) [Receiver=3.1.3] root@Zeus:~#

Sorry, I should have been more clear. Apologies... Is the first mounted disk in the rsync command the disk I just ran the XFS repair on and the second disk is the disk on the array I want to sync it to (in my case disk 7)

Is the name_of_UD_disk the stand alone disk we just did all the XFS repair on?

God dang you are a hero. That worked. Now, the hard part? 1. Start the Array 2. Mount the ZAD8EYTY drive 3. rsync between the two? Should I do that in the UNRAID terminal?

Cool got that done. Re-ran the UUIC change, gave an error Apr 12 05:20:28 Tower unassigned.devices: Error: shell_exec(/usr/sbin/xfs_admin -U generate /dev/sdd1) took longer than 1s! Apr 12 05:20:28 Tower unassigned.devices: Changing disk '/dev/sdd' UUID. Result: command timed out

I clicked it.... I saw this in the Syslog

Click this guy? Should it "do" anything that I can see? Once I get that done, I want to make sure I do this right: 1. Start the Array 2. Mount the ZAD8EYTY drive 3. rsync between the two? Should I do that in the UNRAID terminal?

Holy shit.... when I mounted it I was able to see files on it again! Looks like the SMART passed on it too... Now, I think I changed too much to figure out exactly what happened. That being said, I am not risking this long term and will still bring another server online to be safe and start a scratch UNRAID install on it. So, what's next? You're on this journey with me now @JorgeB and we're close to the end! tower-smart-20210412-0331.zip

1. It did report as failed, however, I do have it and I may just shut down and put it back in to see if I can access it. Nothing to lose at this point. 2. Yes, I understand that. Nothing mission critical was lost, however, its still not going to be fun recovering it from old backup drives, etc. if I can't get make that work. I guess ultimately, its probably OK that this happened. It's made me re-evaluate some architecture in the system and gave me an excuse to splurge on another server. - I assume I can just shut down the system, swap in the old HDD #7, and boot it back up re-assigning the old drive as #7?

So, I'm screwed then and lost those files?