Quick info:  I have had unraid for several years now, no major issues at all since initial setup.  I have about 8 disks, 30% full with a few packages installed from the unmenu addon page.

 

Today, had some problems with name resolution, and the next thing you know, I wasnt able to boot up anymore.  

 

Looking into it further, I attached a monitor to my box, and saw that it was booting up fine until it gets to the part where it says : starting samba: /usr/sbin/nmbd -D /usr/sbin/smbd -D.

 

Then it goes on a never-ending string of >>WAITING...scrolling down the screen.  

 

One thing I have learned is that things can quickly escalate into major issues before asking for help.  So I am hoping someone can assist before matters get worse.  I havent added any disks, or packages, or anything like that.  When I couldnt get DNS to resolve, I did power if off uncleanly though.  The only other thing I tried was to plug my flash drive into my windows pc and see if the main files were ok - go, network, etc.  

 

Please help.

syslog-20110216-011204_shortened.txt

Followup - I saw a post where Joe recommended disabling packages, so I commented them out on the go script and I can now logon.  I am guessing one of the packages was corrupt?  I presume I can just go ahead and reinstall them through unmenu (redownload) and hopefully, that will solve it. 

 

 

Do a memory test overnight if the problem returns .

Thanks.  Now that I am back in at the console, the original problem persists - cannot access the box from my network.  Not being identified by my router.  and ifconfig shows eth0 but it was an interrupt 17 on it?  no clue what is going on.  i could try a different nic i suppose. 

 

fyi i ran a memtest for an hour and it came up ok.  i will do one tonight with all the modules reinstalled (i pulled all but one out for the sake of troubleshooting.

Copy your syslog to the flash drive and then post the whole thing. Zip it if needed.

Ok, it turns out there is a problem with my flash drive, I believe, but wanted to confirm with the experts online.  I attached my most recent syslog and as you will see, it reports that there is a prob with sdj, which is my flash.  I also ran into another post where the OP had the same issue with his flash drive. After replacing it , it seemed to have solved the issue. 

 

As a precaution, I ran the reiserfs check on all drives last night and today, and no errors were found. 

 

When I tried to install some packages this afternoon, I got that 'read-only' file system about not being able to write to the flash drive. 

 

So am I correct in assuming that all I need to do is replace the thumb drive ?

syslog-2011-02-17.txt

There is a "check disk" utility on windows that may fix it.

Oh so I dont need to replace it with a new drive?  Thats good news.  I will try that.  Thank you.

 

BTW, didnt even think of it - but how will I know if all is ok with the drive?  I can run a reiserf check on the actual thumb drive itself?  Or simply wait to see if an error comes up afterwards?

The reiserfs check won't work on the FAT32 drive. Windows has a FAT32 utility. Try to fix it and then see if it becomes writable. Make sure to copy your config directory. You can reformat and reinstall then. As a last resort replace the drive.

Thank you. Will report back if this solves it, so as to close the thread

Happy to report that following the guide on the wiki and this tool http://lime-technology.com/forum/index.php?topic=1367.msg9671#msg9671, all is back to normal.  Thank you for the help !