FreeNAS disc gone

[inkui]

Hello!

I have been sitting around trying to learn FreeNAS, mostly through x quantities of google attempts but I have no succeded with something I need to ask about. So, I got FreeNAS up with two disks which I both could reach through windows (not my Pi. but that's another issue..). So far so good.

When I then was moving over some files through my main computer to the server of course I happened to put them in the "wrong" folder. I attempted to fix this through some classic ctrl+a, ctrl+c and then point it then the right spot. But, what I wasn't thinking of, was that it was also some other files, including the folder "jail" and a folder named after the username: inkui. Realised this and did very poorly in getting the files back in the right place. As tired as I were I did very poorly, it went to slow and it was late. Didn't think anything about consequences of moving important files. I suspect this is the cause of a problem I now have. That the important files of jail, and maybe also the files in the "userfolder", is not where they should be and therefore FreeNAS can't show the disc.

Could this be it, or is it something else causing this problem?

It is what I recall the last thing what I changed in FreeNAS before I couldn't find my files. This is also why I ask for help and not only googling this time. I do want to reach my files, of course.

I'd much appreciate the help given. Thanks in advance.
Regards,
Richard aka inkui

 

[dlavigne]

What makes you think the disk is gone? Is it not showing in Volume Status? Which version of FreeNAS?

 

[inkui]

Well, gone is maybe the wrong word, I guess I should've used quotation marks. It's showing up in Storage/Volumes. But not in Windows, nor in Raspberry Pi. The permissions is, what I can see set properly. Well, they should be as they are the same as the other disc which is reachable.

 

[Fraoch]

Your shares may be messed up. FreeNAS may see the volume but the only way it's accessible from outside is if it's defined as a share though the Sharing function and the Services function. Windows should be able to see a CIFS share and an NFS share by installing an appropriate program while a Raspberry Pi should be able to see both CIFS and NFS shares but it may require the installation of client programs - Google this.

 

[inkui]

Your shares may be messed up. FreeNAS may see the volume but the only way it's accessible from outside is if it's defined as a share though the Sharing function and the Services function. Windows should be able to see a CIFS share and an NFS share by installing an appropriate program while a Raspberry Pi should be able to see both CIFS and NFS shares but it may require the installation of client programs - Google this.

May be? Sadly they seem to be that, yes. As I saw both shares before, and therefore could move my files there I'd guess the problem came after I did what i explained. Isn't there a way to solve it? To make freenas treat the disc as it once did? I mean it's reachable when I check on the Web, well localy on the Web of course. I'd love to solve the windows problem first. The other is, indeed, very Googleable.

But as I reached the disks from start, and do reach them in the (what is it called?) webui (?) there should, and I very much hope so, a way to get it together again? Not only to reach my files, but to use the disk again?

Thanks for the fast response!
Regards,

 

[Fraoch]

Being more specific, there are two things going on here. Volumes (more precisely, vdevs) which FreeNAS sees, and shares, which is how FreeNAS presents the vdevs to your network clients.

You keep using the term 'disc' or drive. Is this disc part of a vdev? A RAIDZ, for example? You also indicate FreeNAS can see it. But can it share it? Can you make a new share pointing to it?

There's not much you can do to the share from a network client to kill it. The jail might be damaged and need to be recreated but FreeNAS should still see the vdev and the data may still be there.

 

[NickB]

Did you have snapshots enabled? If so, you can just roll everything back.

As for the CIFS shares, you might be better off in the future to setup a sub folder or even dataset so that the jails dataset isn't visible.

As Fraoch says, the only thing you would have messed up would have been the jails. If you weren't using it, then you can easily recreate it. Everything else is just your data - no damage to the OS itself.

 

[inkui]

Being more specific, there are two things going on here. Volumes (more precisely, vdevs) which FreeNAS sees, and shares, which is how FreeNAS presents the vdevs to your network clients.

You keep using the term 'disc' or drive. Is this disc part of a vdev? A RAIDZ, for example? You also indicate FreeNAS can see it. But can it share it? Can you make a new share pointing to it?

There's not much you can do to the share from a network client to kill it. The jail might be damaged and need to be recreated but FreeNAS should still see the vdev and the data may still be there.

Hmm. Right. I think I got that.. soon. Uh, I don't know? What I did was to install the disc then share it using "Add new Windows (CIFS) share". I got it to work in some way I can't really recall, but it wasn't advanced I guess. It can see it, indeed! I just tried to share it "again", doing what I once did. I can indeed point to it and therefore share it, I guess. But I can't see it in Windows anyway. So, how do I know if it's damaged and therefore needed to be recreated? And... (this sound's advanced!) how do I recreate it?

Did you have snapshots enabled? If so, you can just roll everything back.

As for the CIFS shares, you might be better off in the future to setup a sub folder or even dataset so that the jails dataset isn't visible.

As Fraoch says, the only thing you would have messed up would have been the jails. If you weren't using it, then you can easily recreate it. Everything else is just your data - no damage to the OS itself.

No, I didn't. Or, well, I don't think I did as there isn't none available. Shouldn't have had it then, I guess.
Yes! Yes! That would be awesome. yes.

So... how do I do this?

Thanks for taking the time, guys! Much appreciated!
Regards,

 

[Fraoch]

Hmm. Right. I think I got that.. soon. Uh, I don't know? What I did was to install the disc then share it using "Add new Windows (CIFS) share". I got it to work in some way I can't really recall, but it wasn't advanced I guess. It can see it, indeed! I just tried to share it "again", doing what I once did. I can indeed point to it and therefore share it, I guess. But I can't see it in Windows anyway. So, how do I know if it's damaged and therefore needed to be recreated? And... (this sound's advanced!) how do I recreate it?

Sounds like more of a permissions issue then. Those can be very complicated because there are many settings in FreeNAS that influence the visibility of a share and just as many (or more) in Windows. There are so many combinations of settings that each situation is unique.

Let's start "by the book" then.

http://doc.freenas.org/9.3/freenas_sharing.html#configuring-unauthenticated-access

 

[inkui]

I've tried a few things from the link now. Nothing works.
Isn't there a way to "restart" everything?

Thanks,
Richard

 

[Fraoch]

Just reinstall the latest 9.3 onto your USB drive. When you start it up, it should auto-import your pool, so your data should still be there.

I would say backup the configuration before doing this, but it looks like your configuration has been corrupted anyway.

 

[inkui]

Did reinstall. No auto-import of the pool. Didn't think and made a new volume. Data lost, but problem persists. I can't reach the disc from Windows. Other shares are there, but not this one.
Of course it's not that fun to lose data, but it wasn't that important. I just want it to work.

EDIT:

It now works. I can reach the disc. For some reason.
In the disc, though, there's a folder for my username inkui. Can I hide this? So this doens't repeat itself. There's also a folder just when entering FreeNAS folder named inkui. Would love this hidden aswell.

Thanks, yet again, for the help.
Kind regards,
inkui

 

[Fraoch]

The problem must be isolated to your Windows machines or your network.

Try to ping your FreeNAS box from your Windows machine.

Other than that, it's a file sharing issue. Check to see that all FreeNAS settings are as the documentation lists. Then you'll have to go into the Windows settings. I have no more advice unfortunately, I can barely get file sharing working myself. There are so many settings and so many settings combinations that it can get very complicated.

 

[NickB]

If you can post some screen shots, I can take a look and see if I can offer any advice.


Sent from my iPad using Tapatalk