Jump to content

[SOLVED] Unraid 5.0.5 fails to display disks or webgui after improper shutdown


Recommended Posts

What Happened:

There was a power outage and my UNRAID box went down improperly due to the event.

 

What's Wrong:

* UNRAID will boot up and I can login via Telnet only

* OSX Finder will display only the Flash drive and it's contents

* I'm unable to view any of my hard drives or the UNRAID webgui

* Going directly to the UNRAID IP address displays a blank white page via my web browser

* I also see this error message in the logs: "FAT-fs (sda1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck." I've done so many times and it doesn't seem to be resolving the issue.

 


root@OrigamiNET:~# dosfsck -av /dev/sda1   
dosfsck 2.11 (12 Mar 2005)
dosfsck 2.11, 12 Mar 2005, FAT32, LFN
Checking we can access the last sector of the filesystem
There are differences between boot sector and its backup.
Differences: (offset:original/backup)
  3:53/42, 4:59/53, 5:53/44, 6:4c/20, 7:49/20, 8:4e/34, 9:55/2e, 10:58/34
  , 65:01/00, 91:fc/31, 92:31/c0, 93:c9/8e, 94:8e/d0, 95:d1/bc, 96:bc/00
  , 97:76/7c, 98:7b/fb, 99:52/8e, 100:06/d8, 101:57/e8, 102:1e/00, 103:56/00
  , 104:8e/5e, 105:c1/83, 106:b1/c6, 107:26/19, 108:bf/bb, 109:78/07
  , 110:7b/00, 111:f3/fc, 112:a5/ac, 113:8e/84, 114:d9/c0, 115:bb/74
  , 116:78/06, 117:00/b4, 118:0f/0e, 119:b4/cd, 120:37/10, 121:0f/eb
  , 122:a0/f5, 123:56/30, 124:20/e4, 125:d2/cd, 126:78/16, 127:1b/cd
  , 128:31/19, 129:c0/0d, 130:b1/0a, 131:06/4e, 132:89/6f, 133:3f/6e
  , 134:89/2d, 135:47/73, 136:02/79, 137:f3/73, 138:64/74, 139:a5/65
  , 140:8a/6d, 141:0e/20, 142:18/64, 143:7c/69, 144:88/73, 145:4d/6b
  , 146:bc/0d, 147:50/0a, 149:50/72, 150:50/65, 151:cd/73, 152:13/73
  , 153:eb/20, 154:5c/61, 155:8b/6e, 156:55/79, 157:aa/20, 158:8b/6b
  , 159:75/65, 160:a8/79, 161:c1/20, 162:ee/74, 163:04/6f, 164:01/20
  , 165:f2/72, 166:81/65, 167:fa/62, 168:b7/6f, 169:07/6f, 170:73/74
  , 171:2b/0d, 172:f6/0a, 173:45/00, 174:b4/00, 175:7f/00, 176:75/00
  , 177:25/00, 178:38/00, 179:4d/00, 180:b8/00, 181:74/00, 182:20/00
  , 183:66/00, 184:3d/00, 185:21/00, 186:47/00, 187:50/00, 188:54/00
  , 189:75/00, 190:10/00, 191:80/00, 192:7d/00, 193:b8/00, 194:ed/00
  , 195:75/00, 196:0a/00, 197:66/00, 198:ff/00, 199:75/00, 200:ec/00
  , 201:66/00, 202:ff/00, 203:75/00, 204:e8/00, 205:eb/00, 206:0f/00
  , 207:51/00, 208:51/00, 209:66/00, 210:ff/00, 211:75/00, 212:bc/00
  , 213:eb/00, 214:07/00, 215:51/00, 216:51/00, 217:66/00, 218:ff/00
  , 219:36/00, 220:1c/00, 221:7c/00, 222:b4/00, 223:08/00, 224:cd/00
  , 225:13/00, 226:72/00, 227:13/00, 228:20/00, 229:e4/00, 230:75/00
  , 231:0f/00, 232:c1/00, 233:ea/00, 234:08/00, 235:42/00, 236:89/00
  , 237:16/00, 238:1a/00, 239:7c/00, 240:83/00, 241:e1/00, 242:3f/00
  , 243:89/00, 244:0e/00, 245:18/00, 246:7c/00, 247:fb/00, 248:bb/00
  , 249:aa/00, 250:55/00, 251:b4/00, 252:41/00, 253:8a/00, 254:16/00
  , 255:74/00, 256:7b/00, 257:cd/00, 258:13/00, 259:72/00, 260:10/00
  , 261:81/00, 262:fb/00, 263:55/00, 264:aa/00, 265:75/00, 266:0a/00
  , 267:f6/00, 268:c1/00, 269:01/00, 270:74/00, 271:05/00, 272:c6/00
  , 273:06/00, 274:45/00, 275:7d/00, 277:66/00, 278:b8/00, 279:92/00
  , 280:8e/00, 281:03/00, 283:66/00, 284:ba/00, 289:bb/00, 291:7e/00
  , 292:e8/00, 293:10/00, 295:66/00, 296:81/00, 297:3e/00, 298:24/00
  , 299:7e/00, 300:cb/00, 301:e0/00, 302:38/00, 303:73/00, 304:75/00
  , 305:76/00, 306:ea/00, 307:38/00, 308:7e/00, 311:66/00, 312:03/00
  , 313:06/00, 314:60/00, 315:7b/00, 316:66/00, 317:13/00, 318:16/00
  , 319:64/00, 320:7b/00, 321:b9/00, 322:10/00, 324:eb/00, 325:2b/00
  , 326:66/00, 327:52/00, 328:66/00, 329:50/00, 330:06/00, 331:53/00
  , 332:6a/00, 333:01/00, 334:6a/00, 335:10/00, 336:89/00, 337:e6/00
  , 338:66/00, 339:60/00, 340:b4/00, 341:42/00, 342:e8/00, 343:7f/00
  , 345:66/00, 346:61/00, 347:8d/00, 348:64/00, 349:10/00, 350:72/00
  , 351:01/00, 352:c3/00, 353:66/00, 354:60/00, 355:31/00, 356:c0/00
  , 357:e8/00, 358:70/00, 360:66/00, 361:61/00, 362:e2/00, 363:da/00
  , 364:c6/00, 365:06/00, 366:45/00, 367:7d/00, 368:2b/00, 369:66/00
  , 370:60/00, 371:66/00, 372:0f/00, 373:b7/00, 374:36/00, 375:18/00
  , 376:7c/00, 377:66/00, 378:0f/00, 379:b7/00, 380:3e/00, 381:1a/00
  , 382:7c/00, 383:66/00, 384:f7/00, 385:f6/00, 386:31/00, 387:c9/00
  , 388:87/00, 389:ca/00, 390:66/00, 391:f7/00, 392:f7/00, 393:66/00
  , 394:3d/00, 395:ff/00, 396:03/00, 399:77/00, 400:17/00, 401:c0/00
  , 402:e4/00, 403:06/00, 404:41/00, 405:08/00, 406:e1/00, 407:88/00
  , 408:c5/00, 409:88/00, 410:d6/00, 411:b8/00, 412:01/00, 413:02/00
  , 414:e8/00, 415:37/00, 417:66/00, 418:61/00, 419:72/00, 420:01/00
  , 421:c3/00, 422:e2/00, 423:c9/00, 424:31/00, 425:f6/00, 426:8e/00
  , 427:d6/00, 428:bc/00, 429:68/00, 430:7b/00, 431:8e/00, 432:de/00
  , 433:66/00, 434:8f/00, 435:06/00, 436:78/00, 438:be/00, 439:df/00
  , 440:7d/00, 441:e8/00, 442:09/00, 444:31/00, 445:c0/00, 446:cd/00
  , 447:16/00, 448:cd/00, 449:19/00, 450:f4/00, 451:eb/00, 452:fd/00
  , 453:66/00, 454:60/00, 455:ac/00, 456:20/00, 457:c0/00, 458:74/00
  , 459:09/00, 460:b4/00, 461:0e/00, 462:bb/00, 463:07/00, 465:cd/00
  , 466:10/00, 467:eb/00, 468:f2/00, 469:66/00, 470:61/00, 471:c3/00
  , 472:8a/00, 473:16/00, 474:74/00, 475:7b/00, 476:cd/00, 477:13/00
  , 478:c3/00, 479:42/00, 480:6f/00, 481:6f/00, 482:74/00, 483:20/00
  , 484:65/00, 485:72/00, 486:72/00, 487:6f/00, 488:72/00, 489:0d/00
  , 490:0a/00
  Not automatically fixing this.
Boot sector contents:
System ID "SYSLINUX"
Media byte 0xf8 (hard disk)
       512 bytes per logical sector
      4096 bytes per cluster
        32 reserved sectors
First FAT starts at byte 16384 (sector 32)
         2 FATs, 32 bit entries
   3938816 bytes per FAT (= 7693 sectors)
Root directory start at cluster 2 (arbitrary size)
Data area starts at byte 7894016 (sector 15418)
    984696 data clusters (4033314816 bytes)
32 sectors/track, 255 heads
         2 hidden sectors
   7892990 sectors total
Reclaiming unconnected clusters.
Checking free cluster summary.
/dev/sda1: 249 files, 30798/984696 clusters

 

Syslog Attached

 

 

I've been at this for hours and I'm needing another pair of eyes to figure out what's going on. I definitely appreciate any help.

 

Thank You

syslog.txt

Link to comment

Have you tried pulling the flash and running checkdisk on Windows (or Disk Utility on Mac)?

 

If that doesn't work you can try to copy what you can then reformat it, reinstall unRAID, copy your config and key file back and try it again.

 

If the flash drive can't be repaired you can get a key for a new flash from limetech.

Link to comment

Disk Utility doesn't work. It runs through and says everything is great, but still no dice.

 

I suspect that there is some sort of corruption somewhere with UNRAIDs filesystem. The flash drive itself appears to be working fine and I'm able to access it with no issues.

Link to comment

The file system on FLASH is pretty simple. You won't get a lot of feedback from Disk Utility.

If Disk Utility ran all the way through and fixed any errors,

then you should now see the web screen from unRAID.

 

If you don't have the unRAID screen, there's something else wrong.

If you do have the screen now, but the array won't start properly, then, telnet in (via the TERMINAL program) and run Reiserfsck on your DATA drives. 

http://lime-technology.com/wiki/index.php?title=Check_Disk_Filesystems

 

 

Link to comment

Try booting in safe mode or removing all addons. You have some addons that are not installing correctly according to your syslog. I've never heard of a data disk problem that caused a problem with the webGUI but addons are always suspect.

 

After getting rid of your addons also clear you browser cache.

Link to comment

Well this has been a very interesting adventure!  Everything is all fixed.

 

TL:DR

When switching ISPs, make sure you set your network settings to obtain your new network information automatically or else you won't be able to access your server.

 

What happened?

1) I switched ISPs and some of the network settings were mixed up between both my old and new ISP in my router.

2) UNRAID was unable to properly communicate with the Internet due the server IP being set to "Static" under the Network Settings tab.

3) UNRAID was also trying to update some of the plugins for Dynamix WebGUI and they were some how damaged.

4) I was unable to access my drives/shares/Dynamix WebGUI.

5) UNRAID was complaining that the flash drive was corrupted and needed to be repaired with FSCK.

 

How it was fixed?

1) The new ISP was having an outage the same time I was trying to correct the settings and get UNRAID back online. That made thing even more interesting until I figured out there was an outage going on. Once the outage was cleared, I got all the correct settings into place to get my router properly online and dishing out the *correct* IPs within my network.  The power outage only helped show me the connection issue when everything came back up and I was unable to connect to the server.

 

2) I was able to view the contents of the flash drive and it seemed to be behaving as normal with things loading and assigning, hence my not wanting to format the flash drive. I went in an edited the network.cfg file manually to remove the "Static" settings and to grab a new IP/DNS info. From there i was able to Telnet into the drive with no issues, but still no WebGUI.

 

3) Going off of an idea from trurl, I removed all plugins to help minimize potential issues. Boom! Classic WebGUI access obtained. Here's where I saw the array was "offline" and needed to be checked. Hence why I wasn't able to see or access them.

 

4) I brought the array back online and this resolved this issue. Afterwards, I did a brand new install of Dynamix WebGUI with Plugin Control Center to pull down everything else. Everything checks out.

 

5.) I ran fsck with the -r switch and it brought up a choice menu of overwriting the backup or the original files. I picked option 2 thinking that the now originals were out of whack with corruption. This however destroyed the boot partition and required me to pull the flash drive and use the "make bootable" batch file on the flash drive on another computer. After it finished, the drive was bootable again and behaved as it should be with no fsck error messaging.

 

Number 5 was the first issue resolved of the bunch. After I got everything up and running again, I started a parity check and it was running extremely slow at 2.3 MB/sec. I stopped the array, rebooted, and now I'm back to 160MB/sec again.

 

Thank you everyone for your suggestions and love. 

Link to comment

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...