NASLite Network Attached Storage

after rebooting my naslite server, i can't see my drive status in url window but if i go to \\Server\disk-0 , 1 , 2 ,3 ,4 i can see them and access them fine, now i booted the system twice but same thing is there somthing wrong in software or on my config?

please help dont wana loose my TB data

Thanks
TaNk

Is this something that just happened or is this a new box with the data just loaded on it. A little more info will help all figure this out and in turn help you as well. Also have you entered the unlock code, saved and rebooted?

Mike

Hello TaNk

If I understand this correctly, you can see the stats via SMB but not via HTTP. If that's correct then the problem is caused by one of 2 reasons:

1. You have HTTP disabled in your configuration. Enable HTTP, save and reboot.
2. Your browser cache is showing incorrect content. Clear your browser cache.

Those are the only reasons I can think of offhand.

Thanks for reply guys,

what im trying to say is, when i go to my http://192.168.0.1 (naslite ip) and then on hard-drive status page some times it show's up only one drive and some time it shows all three drives now if i get to my //server/disk-2 i can access the drive.

so what im saying is i can't see the drive in htt:// but i can access thro \\server\disk-2.

i think few more people are having the same issue.
http://www.serverelements.com/phpBB2/vi ... d798ee801a

Ah,

So you are not saying that you can’t access the disk via HTTP as in http://server/Disk-2/ but rather the disk status page is missing disk status for the drive in question.

If that is correct, then what you are observing is normal. The status generation code has very low priority and is designed to yield to any and all other processes. In addition, if a device takes too long to respond, some critical blocks of the status generation code are designed to exit on timeout. A common problem with some disks is a slow-to-respond SMART check. So, on occasion the storage status page may be incomplete. The process will likely complete on the next status cycle. If a disk is consistently slow to respond, then it may be necessary that SMART be disabled for that disk only.

Regardless, this has no effect on the performance of the system and is behavior by design.

Hope that helps.

Thanks tony .. that just cleared lota things

TaNk