Adaptec 5325301507 Administration Guide - Page 224

Miscellaneous Issues, Back Up Applications

Page 224 highlights

Miscellaneous Issues You Cannot Log in as Root to the SnapServer GuardianOS allows you to log in as root over SMB. If this operation has failed or you have trouble logging in, be sure that you have enabled root login in the Network > Windows page. Also note that the root account password is tied to the admin account password. If you cannot log in as root, change the password for the admin account on the Network > Windows screen. Use the admin password to log in as root. Snap Disk 10 Disk Drives do not Appear on the Storage > Disks/Units Screen Verify that the Snap Disk 10 is connected properly to the Serial ATA connector at the rear of the SnapServer and that the expansion array is properly connected to the power supply. Then, to initialize the Snap Disk 10, power off and then power on the SnapServer. Caution Make sure to use a screwdriver to firmly seat the connectors on the Snap Disk 10 and the SnapServer. Tightening the connectors by hand will not work. You Are Unable to See Your Domain Users When Trying to Set Up Windows Security Permissions on File Folders The SnapServer (GuardianOS) has joined the Active Directory domain properly, and you can see the domain users when you set Share permissions from the browser-based Administration Tool. Make sure the Windows client (PC) you are trying to set permissions from is assigned a valid DNS server. You can check your Windows client using the ipconfig command from a command prompt. Miscellaneous Issues These are some miscellaneous issues you may encounter when using your SnapServer. Back Up Applications You Backed Up Your Snapshot Share, Are Now Attempting to Restore It, and the Operation Fails A snapshot share is read-only. You can restore the data to a read-write accessible share. The NetVault Client Cannot Connect to the NetVault Server on the SnapServer Occasionally, after enabling NetVault for GuardianOS for the first time, the NetVault for GuardianOS Server may not start properly. If this happens, the 208 SnapServer Administrator Guide

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250

Miscellaneous Issues
208
SnapServer Administrator Guide
You Cannot Log in as Root to the SnapServer
GuardianOS allows you to log in as root over SMB. If this operation has failed or
you have trouble logging in, be sure that you have enabled root login in the
Network
> Windows
page. Also note that the root account password is tied to the admin
account password. If you cannot log in as root, change the password for the admin
account on the
Network > Windows
screen. Use the admin password to log in as root.
Snap Disk 10 Disk Drives do not Appear on the Storage > Disks/Units Screen
Verify that the Snap Disk 10 is connected properly to the Serial ATA connector at
the rear of the SnapServer and that the expansion array is properly connected to the
power supply. Then, to initialize the Snap Disk 10, power off and then power on the
SnapServer.
Caution
Make sure to use a screwdriver to firmly seat the connectors on the Snap
Disk 10 and the SnapServer. Tightening the connectors by hand will not work.
You Are Unable to See Your Domain Users When Trying to Set Up Windows
Security Permissions on File Folders
The SnapServer (GuardianOS) has joined the Active Directory domain properly,
and you can see the domain users when you set Share permissions from the
browser-based Administration Tool.
Make sure the Windows client (PC) you are trying to set permissions from is
assigned a valid DNS server. You can check your Windows client using the
ipconfig
command from a command prompt.
Miscellaneous Issues
These are some miscellaneous issues you may encounter when using your
SnapServer.
Back Up Applications
You Backed Up Your Snapshot Share, Are Now Attempting to Restore It, and
the Operation Fails
A snapshot share is read-only. You can restore the data to a read-write accessible
share.
The NetVault Client Cannot Connect to the NetVault Server on the SnapServer
Occasionally, after enabling NetVault for GuardianOS for the first time, the
NetVault for GuardianOS Server may not start properly. If this happens, the