wazkaren

Members
  • Posts

    10
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wazkaren's Achievements

Noob

Noob (1/14)

0

Reputation

  1. It seems I was hasty on shutting down my system. It wasn't actually locked up, I have a bad drive and I think it was retrying to read or write the disk. Seeing these errors: » reallocated_sector_ct=12000 » reported_uncorrect=1081 » current_pending_sector=52736 » offline_uncorrectable=52736 » ata_error_count=1081 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: read failure 90% 40938 284536536 I assume at this point the only thing to do is replace the drive and let it rebuild? Is there anyway to tell if any files are corrupted after the rebuild completes and system is back up and running?
  2. It's been a few years since I've been to this forum and I'm not sure where to start looking. My unraid server has been running without issue for several years. Last night it locked up. When I restarted the server a parity check started and has found 8 errors so far. Can someone point me to info on this website on how to deal with parity errors? I'm thinking that I now have one or more files on my server that are now corrupted. Before I ask specific questions I wanted to do some catching up but there is a lot of info on this site. Is there a faq that deals with parity errors? Thanks, Greg
  3. Turns out I'm not really awake yet. I double checked and the array WAS started when I checked to see if the files are there. Glad I listened to you guys and did not start a rebuild. I still can't figure out what's wrong the the drive though. Smart test passes
  4. Ok, thanks. My current processor is not 64-bit. I'm looking into upgrading so I can move to the latest version of unRaid
  5. Thanks. I did replace the drive 2 weeks ago so bad cabling does seem likely. When I checked the contents of the drive the array was stopped (I checked from a the shell). The drive is assigned to it's slot so I'm puzzled as to why the rebuild button is missing? I will double check the cabling and reboot. And thanks for the warning about not rebuilding the parity disk. Thanks, Greg
  6. I have a drive that has been disabled (red ball). But it appears to be healthy, no smart errors, and data appears intact on the drive. I understand that once the drive is red balled I have to rebuild the array. But there is no option to do a parity rebuild, only start/stop array and reboot. I'm not sure what to do next. Any thoughts? I attached the syslog Thanks, Greg syslog-2017-01-28.txt
  7. The funny thing is everything in the 'test' share (with Private security) has nobody as owner as a result of running the newparms script. From Windows everything in the 'test' share is visible and accessible even though it has owner of nobody. Greg
  8. OK, I think I see what's happening. My share 'Movies' has public security. I also have another share 'test' that has private security and is shared as 'hidden'. I can reproduce my problem like this: 1. In Windows XP I open Network Places and browse to my UnRaid server and then to Movies share. Copy a file into 'Movies'. telnet to tower and ls -la shows files copied over to 'Movies' share have an owner of Nobody (which I believe is correct). 2. I close the 'Movies' window and enter \\tower\test in a file explorer window and enter my user name and password when prompted. I can successfully see the contents of 'test' share. 3. Follow step 1 again. The file copied to 'Movies' this time has owner of root. 4. I close both windows and run 'net use \\tower\test /delete' on a command line in Windows XP. 5. Follow step 1 again. The file copied to 'Movies' this time has owner of nobody. So I guess I have a simple workaround. I just have to make sure I run step #4 before I copy anything into a share with public security. Greg
  9. I'm a relatively new UnRaid user and have run 4.5.6 for about a month or so. A week ago I upgraded to 5.0 beta to experiment with the new security feature. Things are working well but I'm seeing one small issue. Sometimes when I copy a file to an UnRaid user share from a Windows XP box the owner is set to root. For example: I have a user share named "Movies" (with security set to Public) and I copy files to it from a Windows XP box. If I then telnet into UnRaid and look at /mnt/user/Movies. Sometimes the files are there with an owner of nobody but sometimes they have an owner of root. I can run newparams and it will set the owner correctly but I thought all new files should be created with nobody automatically? I did a search and haven't seen anyone else with this issue so I assume I'm just missing something. Anyone have any ideas? Thanks, Greg