News:

RAID is not a replacement for a backup! Here's why.

Main Menu

After Windows 2003 server reboot TeraStation III iSCSI had to be 'reactivated'?

Started by BrooksNorton, June 11, 2010, 12:35:49 PM

Previous topic - Next topic

BrooksNorton

I had to reboot our Windows 2003 Server.  It has 2 TeraStation III iSCSI arrays attached.  After rebooting TeraStation 1 came up normally and was accessable.  TeraStation 2 holds users folders and did not show up after they logged in.  I looked in Disk Manager on the server and the disks showed up but were not "Healthy".  I right clicked on them and had the option to 'reactivate'.  I did that and they disks came up looking good.  But then I went to look at them in Windows Explorer and all the folders were there.... but all the shares were gone.  I had to reenter the share names and permissions for 25 users.

 

Is there a procedure that has to be followed when rebooting a server with TeraStations attached to ensure it comes back up normally and doesn't lose share information?

 

Is something else up?

 

Thanks,

Brooks


AngelsAbys

It is strongly suggested that you stop the ISCSI service on either the unit itself, or from the ISCSI controller that you are currently using. Before any type of maint or rebooting


Browser ID: smf (is_webkit)
Templates: 4: index (default), Display (default), GenericControls (default), GenericControls (default).
Sub templates: 6: init, html_above, body_above, main, body_below, html_below.
Language files: 5: index+Modifications.english (default), Post.english (default), Editor.english (default), Drafts.english (default), StopForumSpam.english (default).
Style sheets: 4: index.css, attachments.css, jquery.sceditor.css, responsive.css.
Hooks called: 128 (show)
Files included: 35 - 1354KB. (show)
Memory used: 1000KB.
Tokens: post-login.
Queries used: 16.

[Show Queries]