URGENT HELP NEEDED

[fracai]

Did you type out "./fixup.sh + mount -o noatime -uw /"? Or is everything after and including the "+" output from the script?

 

[cyberjock]

Did you type out "./fixup.sh + mount -o noatime -uw /"? Or is everything after and including the "+" output from the script?

You don't do the mount at all... you do EXACTLY what I type, nothing more and nothing less.
The mounting is handled in the script already.

 

[fracai]

Right, but the output that goldenma posted includes that "+ mount..." text. I was clarifying what was typed.

 

[cyberjock]

Oh.. I see what he posted. Being that he posted a blob of text there's no way to know.

 

[goldenma]

sorry for being unclear. i typed exactly what was shown in note#11, and copied the whole screen. i got stuck after command #5, so i rebooted from the console. now i can turn off CIFS service, but it won't turn on again. i'm going to run these commands again in the webGUI

As root and in SSH do the following commands:

1. cd /tmp
2. fetch https://bugs.freenas.org/attachments/download/768/fixup.sh.txt
3. chmod +x fixup.sh.txt
4. mv fixup.sh.txt fixup.sh
5. ./fixup.sh

 

[goldenma]

hmm.. this time it stopped responding after i entered [./fixup.sh], and didn't even show "+mount -o noatime.." like last time. is this script supposed to take a while to run? i guess i should wait a few minutes...

 

[goldenma]

if nothing works, i could reinstall the FreeNAS system and try to start over. but i want to make sure, it will not affect any file on the old volume, right?

 

[fracai]

Even just remounting the OS volume usually takes a minute or two. I'd leave it for a while.

Reinastalling the OS should not touch your data. Backup your old configuration first in case you don't want to lose any config you've applied.

 

[cyberjock]

The last step of the script can take a few minutes.

 

[goldenma]

i waited long time and it still wasn't responding, CIFS service could not start. so i ended up reinstalling the system (9.2.1.5) on the same USB. but now i encounter problem as i try to boot up the new system for the first time. on the console screen it says
[freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list]
[freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to regiser AuthRecord 0000000800C30180 10.10.1.10.in-addr.arpa. (PTR) that's already in the list]

and stuck there on that screen :(

 

[fracai]

That mDNSResponder message shouldn't be a major issue and the actual problem is likely unrelated. Can you post the previous lines as well?

 

[goldenma]

i'm feeling quite dumb - trying everything i could find, but still not getting a result :( the server console is running (though the mdnsresponder error is still there), i can access webGUI and configure it as i did before (add volume, groups, users, shares, enable CIFS service, etc.) but client computer still cannot see or map the network drive. it can ping the server address, but will not connect. window diagnose says "The device or resource (10.1.10.10) is not set up to accept connections on port "The File and printer sharing (SMB)"." could someone please let me know what i'm doing wrong? thanks so much!

 

[joeschmuck]

@goldenma
If you really want to help yourself you will start using the code brackets so your data is in a readable format. I'm having a hard time following what the heck is going on. The messages you indicated above are not of concern. If you do not know how to map shares on a windows machine then you should be asking someone who does in your company. As well as messing around with FreeNAS as you need to be somewhat computer literate to make this advanced piece of software work properly. Also do you have a backup of your data?

@fracai and @cyberjock
Can't he just reboot the NAS and it load the CIFS, assuming the shares are done correctly?
Also he may need to turn off CIFS, reboot, remove the shares and redo them, then turn on CIFS.
I agree that he probably hasn't lost any data YET! but it could happen soon if he's not careful.

 

[goldenma]

i apologize if my posts weren't very clear. i'm not a programmer and not familiar with code language. i do'nt know how to rate my computer literacy.. all i know is that i put the system together last week, mapped all the drives on all computers and it was working well until this morning. so i guess i'm just an average user trying to troubleshoot an issue. i'd appreciate if anyone can shed some light on what could have went wrong. all i can think of now is to unmount the new harddrive and see if i can get the old setting from friday to work.

 

[alexg]

Goldenma, It is not that difficult. Read forum help http://forums.freenas.org/index.php?help/

 

[solarisguy]

@goldenma, you cannot execute fixup.sh in the shell window of the GUI ! :(

The script shuts down the GUI before the patching is done (service django stop).

You have to start SSH service, and login to your FreeNAS using SSH client (for example PuTTY for Windows). And only then execute the five steps you listed above.

P.S. Note #11 clearly says to use SSH, however I did not notice you confirming using SSH. And your symptoms are matching executing fixup.sh from within the shell in the FreeNAS GUI.

 

[joeschmuck]

i apologize if my posts weren't very clear. i'm not a programmer and not familiar with code language.

When you create a posting you have a menu bar with icons like Bold, Italics, Underline, etc... The one with the "{}#" is the code. You click on that and another window opens and you can cut and paste the text into that window. This allows the text to retain it's format. This has nothing to do with coding or programming.

 

[cyberjock]

@fracai and @cyberjock
Can't he just reboot the NAS and it load the CIFS, assuming the shares are done correctly?
Also he may need to turn off CIFS, reboot, remove the shares and redo them, then turn on CIFS.
I agree that he probably hasn't lost any data YET! but it could happen soon if he's not careful.

Yes, but doing a reboot after every change can be tedious.

You can't turn off CIFS, so trying to turn it off, reboot, remove the shares and redo them, then turn it on isn't possible.

The problem is that without the patch you can start the service but then you can never stop it. On reboot the service will still be "enabled" and will start automatically. In essence, once you start CIFS with 9.2.1.5 you can never stop it without hackery. Because of how serious the problem is for CIFS users the patch was released. ;)

Thankfully, 9.2.1.6-beta(which I'm using on my test machine) seems to be a very good OS.