Adaptec 5325301656 Administration Guide - Page 197

Snap Disk 10 Disk Drives do not Appear on the Storage > Disks/Units Screen

Get Adaptec 5325301656 - Snap Server 14000 NAS PDF manuals and user guides
UPC - 753253016563
View all Adaptec 5325301656 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 197 highlights

Networking Issues is missing a forward slash (/) in the command, which will return an Access Denied message. The correct syntax should be the following: mount 192.168.32.124:/SHARE1 /mnt Note The share name is case sensitive. You Cannot Log in as Root to the Snap Server 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 Snap Server 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 Snap Server. Caution Make sure to use a screwdriver to firmly seat the connectors on the Snap Disk 10 and the Snap Server. 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 Snap Server (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. Appendix C Troubleshooting Snap Servers 183

  • 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
Networking Issues
Appendix C
Troubleshooting Snap Servers
183
is missing a forward slash (/) in the command, which will return an Access Denied
message. The correct syntax should be the following:
mount 192.168.32.124:/SHARE1 /mnt
Note
The share name is case sensitive.
You Cannot Log in as Root to the Snap Server
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 Snap Server 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
Snap Server.
Caution
Make sure to use a screwdriver to firmly seat the connectors on the Snap
Disk 10 and the Snap Server. 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 Snap Server (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.