Hidden folder in directory?

[Jhorts]

Hey guys, I made a mistake in my robocopy command transferring data from my computer to my Unraid server over the network.

 

robocopy E: "\\data\general\unsorted\Laforge 7-13-21"

 

The share is actually General (capital G), but robocopy reports that the copy was successful and if I try to create a new folder via the file explorer in ..\General\unsorted, it states that the folder already exists, even though it doesn't show it. CMD in windows and MC in Unraid don't show ...\general at all. I feel like I've done this before but I can't recall what the solution ended up being.

 

Additionally, I noticed that one of my drives is emulated at the moment. Not sure if that is related or not.

 

Not exactly sure what to do here. I can easily copy the files into the correct directory from the computer again, but do I need to free up the space or move the files from this ghost directory? Is this related to the emulated drive and fixing that may fix this? I'm running a read-check now. I don't think it's the drive, I think it's crappy hardware.

 

EDIT: I found the "ghost" folder in /mnt/disk2/General/unsorted. It is also showing in MC in /mnt/user/General/unsorted. What is the correct way to fix this? Delete the directory on the disk and recopy it from the computer to the share? Can I use a move or rename command to move it from the user or disk to a new directory in the correct share?

 

Edited July 13, 2021 by Jhorts
New info

[trurl]

Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. 

[trurl]

1 hour ago, Jhorts said:

I found the "ghost" folder in /mnt/disk2/General/unsorted. It is also showing in MC in /mnt/user/General/unsorted.

No, this is just the way user shares work. These are the same files. The user shares are just a combined view of all the disks.

 

57 minutes ago, trurl said:

Go to Tools-Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. 

 

[Jhorts]

Diagnostics attached. For some reason I thought that a folder could exist on the drive, without actually being a part of a share (unintentionally of course). But since it's in the .../user/General/... share, I guess I just made that up. Thanks in advance. Read-check 70% complete. Is that the same thing as a parity check?

data-diagnostics-20210713-1852.zip

[trurl]

No indication in your diagnostics that you currently have a share named "general", only "General". Thought you might have accidentally created one, and SMB won't show both because it isn't case-sensitive.

 

It does look like you probably had a "downloads" and a "Downloads" share at some time in the past though, but only one of those still exists.

 

1 hour ago, Jhorts said:

Read-check 70% complete. Is that the same thing as a parity check?

Read check only checks that the disks can be read. You can't do a parity check with a disabled disk. Mostly pointless since it takes time better spent getting your array back to parity protected.

 

Looks like you must have rebooted since disk3 was disabled so can't see what the problem was, but it does have a large number of CRC in SMART, as does disk1, which indicates connection problems.

 

Check all connections, all disks, both ends, power and SATA, including splitters.

 

SMART for disk3 looks OK. You can rebuild the disk to itself:

 

https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself

[Jhorts]

I'll start the rebuild now. I clicked "spin down" on the emulated drive because ...curiosity? (I know better).

 

Going forward:
1) Can the diagnostics and/or SMART logs be sent to a syslog server or is there another way to save those logs so we could have seen the issue even after a restart/spin down?

2) I can see the ghost folder in APF but not via SMB.  Is there a way to "recover" the data in "general" and free up that space on the array, or do I just delete it and recopy it? Not an issue in this case, but it could be in the future.

Edited July 14, 2021 by Jhorts
New info

[trurl]

You can send syslog to a syslog server, and syslog is where I would have looked to see I/O errors when they occurred.

https://wiki.unraid.net/Manual/Troubleshooting#Persistent_Logs_.28Syslog_server.29

 

As mentioned, I didn't see any "general" share in your diagnostics. Go to Shares - User Shares and post a screenshot.

[Jhorts]

[trurl]

As you can see in that screenshot, there is no "general" share, only "General".

 

Do you have something you can show me to demonstrate why you think there is something named "general"?

[Jhorts]

Thanks for the continued help trurl. I guess the issue really comes down to what's going on with the LaForge folder? On the left is SMB and the right is a terminal inside Unraid, inside the "user" directory.

[trurl]

From the command line, what do you get with this?

ls -lah /mnt/user/General/unsorted

 

[Jhorts]

I'm fairly green with linux and cmd lines.

[trurl]

That looks OK and since I have no experience with Mac I don't know why it won't show that folder

[Jhorts]

It’s like it exists on the disk but not the share. I don’t mind deleting that folder and recopying it, but I wonder why it did that? It was copied on a PC.

[JonathanM]

6 minutes ago, Jhorts said:

It was copied on a PC.

Does it show up on the PC?

[Jhorts]

It does not. The only place it shows up is on the terminal or MC on Unraid, and previously via AFP protocol. I just updated, so now AFP is not an option or I would show you.

 

But if I try to create a folder in that directory with the same name from my PC, it says it already exists and prompts for a merge. I did that and it still didn’t show.

Edited July 17, 2021 by Jhorts

[JonathanM]

What happens if you rename the folder in MC?

[Jhorts]

I copied the contents of the folder to a new folder, and the new folder shows in SMB correctly. MC shows both folders and if I try to create a folder in SMB with the same name as the original, it says it already exists. LaForge 7-13-21 is the original ghost folder, LaForge 2 7-13-21 is the copied folder.

[JonathanM]

38 minutes ago, Jhorts said:

I copied the contents of the folder to a new folder,

 

3 hours ago, jonathanm said:

What happens if you rename the folder in MC?

 

[Jhorts]

Renamed the folder to "NOT_LaForge 7-13-21" in MC and the situation didn't change. MC shows "NOT_LaForge 7-13-21" but SMB doesn't and won't let me create a folder called "NOT_LaForge 7-13-21" because it already exists.

[JonathanM]

Try rebooting in maintenance mode and doing a file system check on that disk.

[Jhorts]

File system check on disk 2 complete, now what? Restart the array and see if it's there?

[itimpi]

23 minutes ago, Jhorts said:

File system check on disk 2 complete, now what? Restart the array and see if it's there?

You need to run without the -n flag or no corrections are ever made.

 

I wonder if there us some hidden (unprintable) character in the name of the folder (or a file it contains) and that is upsetting Sambz.

[JonathanM]

Robocopy has caused issues in the past, but I haven't seen anybody complain about it for a few years. I wonder if there is a new issue with all the changes in SMB security recently.

[Jhorts]

No dice. Ran it without the -n flag and there was no change. I thought Robocopy was created to fix Microsoft's broken copy system. Now it doesn't work either?

At this point, I'm not even worried about the data as much as I am about what happened. Should I get Lime Tech involved at this point? I just want to know what I did so I don't do it again in the future. If SMB is not case sensitive, I shouldn't have done anything that caused an issue.