Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

why do i have to keep restarting my array every day

Featured Replies

i am running unraid 4.5.1 and it seems like for the past week or so i have to restart my array on at least a daily basis.  i am connecting to it from windows 7 machines on my home network and what happens is that when i browse to \\tower\sharename for any of the shares they just appear to be empty.  and then if i stop and restart the array via the web gui, everything comes back.  this is very frustrating.

 

about a month ago I had a similar problem and when I posted my syslog i was told i had a failing/failed drive so I replaced it and life was good for a while.  but not its happening again.

 

the only other difference is that since then I have also added a cache disk and I have installed unMenu.  I tried attaching my syslog but it saidthe file was too big.  I also tried to paste it below but it said mypost was too big.  So I am not sure how to get that to you - please advise.

I would appreciate any help so I don't have to restart the array every day.

 

  • Replies 66
  • Views 12.3k
  • Created
  • Last Reply

i am running unraid 4.5.1 and it seems like for the past week or so i have to restart my array on at least a daily basis.  i am connecting to it from windows 7 machines on my home network and what happens is that when i browse to \\tower\sharename for any of the shares they just appear to be empty.  and then if i stop and restart the array via the web gui, everything comes back.  this is very frustrating.

 

about a month ago I had a similar problem and when I posted my syslog i was told i had a failing/failed drive so I replaced it and life was good for a while.  but not its happening again.

 

the only other difference is that since then I have also added a cache disk and I have installed unMenu.  I tried attaching my syslog but it saidthe file was too big.  I also tried to paste it below but it said mypost was too big.  So I am not sure how to get that to you - please advise.

I would appreciate any help so I don't have to restart the array every day.

 

Compress the syslog, then attach it.  The zipped log is usually small enough.  If not, upload it somewhere and provide a link.

 

Joe L.

 

the only other difference is that since then I have also added a cache disk and I have installed unMenu.  I tried attaching my syslog but it saidthe file was too big.  I also tried to paste it below but it said mypost was too big.  So I am not sure how to get that to you - please advise.

I would appreciate any help so I don't have to restart the array every day.

 

 

pastebin.com, pastebin.org or pastebin.ca are good sites for dumping your syslog then provide a link.

Wow, what's opening all those files? You running some sort of server or is windows 7 keeping files open?

  • Author

Which files?  Sorry I don't really know how to read the syslog. Are they all from a certain share?  Where do I look in the syslog to see? Which lines?

What are you running a web site off of yout unRAID?

Have you opened it to be accessible from the Internet?

 

  • Author

no i9 am definitely not runnign a website from it... not doing anything fancy other than unMenu.

no i9 am definitely not runnign a website from it... not doing anything fancy other than unMenu.

 

Then there is something very wrong. We can't see it from the syslog you posted because it's already been rotated.

 

Reboot your server, and from the console boot menu, select Memtest86+

Let the memtest run for a few hours, so we can get any suspicions about bad RAM out of the way.

 

Then start the server normally, and after it is all started, then take the syslog and post it.

Don't wait too long for the syslog, because whatever is causing the problem may overfill it again and it will get rotated.

 

I'll point out that the syslog is sharing document names with the world... so if there are any sensitive ones, you might try coming up with a more secure way to post the syslog.

 

Are you running Picasa or some other photo organizer that can upload to a website, by chance? Looks like most of the files that are churning are pics and while it doesn't seem very bright for an app like that to keep the file locked, it might be worth investigating.

 

Also, as far as not knowing how to read the syslog... join the club! Just opening it up and seeing what's in there is a good first step toward eliminating non-unRAID issues before coming to the ludicrously helpful experts lingering around here.

 

Looks like he is mapping his unraid to a webserver or something. Very strange. We need more info on his setup to figure it out.

 

bdee1, try unplugging everything from your network except unraid and your win 7 machine and see if this still happens.

  • Author

dee, you're in the business of web hosting, right?

 

 

thats correct - i do web hosting - but i don't host anything on the web from my unraid server at all.

Something's churning those files... xaminder's suggesting of isolating the two boxes seems a good idea. And following purko's suggestion about a fresh syslog would also be very handy.

  • Author

I just got the fresh syslog...  see attached.

syslog-2010-03-23.txt

Your disk7  (/dev/md7) needs to have its file-system checked and repaired.

 

Mar 23 07:51:46 StorageTower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 56953 does not match to the expected one 2

Mar 23 07:51:46 StorageTower kernel: REISERFS error (device md7): vs-5150 search_by_key: invalid format found in block 50338696. Fsck?

Mar 23 07:51:46 StorageTower kernel: REISERFS (device md7): Remounting filesystem read-only

Mar 23 07:51:46 StorageTower kernel: REISERFS error (device md7): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1 2 0x0 SD]

Mar 23 07:51:46 StorageTower kernel: REISERFS (device md7): Using r5 hash to sort names

 

That does not explain the too-many-open-files errors from before, but it is an issue that will cause all kinds of problems.

Instructions on how to check/fix are in the wiki:

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

 

 

  • Author

hmm thats interesting - after you posted that i went and checked in the web gui and noticed that disk 7 was listed as unformatted.

 

i think there is definitely something weird going on... i had my tower running flawlessly for a year or two and then it seems like the past few months i have just had nothing but problems... as soon as i fix one, a week goes by and then a new one pops up...

 

the folks on the forums have been phenomenal with helping me get it patched up every time but i gotta say its getting frustrating to have these problems so often. 

 

anyway - i appreciate the help l and will let you know how the disk check goes...

 

thanks!!

 

  • Author

ok so i ran the disk check - here's a transcript of my telnet session:

 

 

StorageTower login: xxxxxxxx

Linux 2.6.31.12-unRAID.

root@StorageTower:~# cd

root@StorageTower:~# samba stop

root@StorageTower:~# umount /dev/md7

umount: /dev/md7: not mounted

root@StorageTower:~# reiserfsck /dev/md7

reiserfsck 3.6.19 (2003 www.namesys.com)

 

*************************************************************

** If you are using the latest reiserfsprogs and  it fails **

** please  email bug reports to [email protected], **

** providing  as  much  information  as  possible --  your **

** hardware,  kernel,  patches,  settings,  all reiserfsck **

** messages  (including version),  the reiserfsck logfile, **

** check  the  syslog file  for  any  related information. **

** If you would like advice on using this program, support **

** is available  for $25 at  www.namesys.com/support.html. **

*************************************************************

 

Will read-only check consistency of the filesystem on /dev/md7

Will put log info to 'stdout'

 

Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes

###########

reiserfsck --check started at Tue Mar 23 08:15:52 2010

###########

Replaying journal..

Reiserfs journal '/dev/md7' in blocks [18..8211]: 0 transactions replayed

Checking internal tree..finished

Comparing bitmaps..finished

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 95786

        Internal nodes 594

        Directories 927

        Other files 20464

        Data block pointers 95719388 (97188 of them are zero)

        Safe links 0

###########

reiserfsck finished at Tue Mar 23 08:26:55 2010

###########

root@StorageTower:~#

 

hmm thats interesting - after you posted that i went and checked in the web gui and noticed that disk 7 was listed as unformatted.

 

i think there is definitely something weird going on... i had my tower running flawlessly for a year or two and then it seems like the past few months i have just had nothing but problems... as soon as i fix one, a week goes by and then a new one pops up...

 

the folks on the forums have been phenomenal with helping me get it patched up every time but i gotta say its getting frustrating to have these problems so often. 

 

anyway - i appreciate the help l and will let you know how the disk check goes...

 

thanks!!

 

unformatted is a display error.  It simply indicates the drive could not be mounted.  Do NOT press the format button if you see it on the web-interface.

Interesting in that no errors were found.  (Good, but interesting)

 

To me, it indicates you have some hardware issue to resolve... probably memory, but it could be the disk-controller, or even the disk (if intermittent).  It could easily be a sign of bad capacitors on the MB.

 

I'd start with an overnight run of the memory test and go from there. 

All these seemingly un-related errors are clues... (they are probably related)

 

  • Author

so after running the disk check i stopped and restarted the array and disk 7 is back.

 

i still have no idea what keeps opening all those files.  at first i thought it was because the windows 7 "always available offline" feature was enabled on one of my shares, but i disabled that and its still happening.

 

my only other thought is that i have windows 7 backup running every night (and every night it tells me it fails - i am assuming because the array craps out during or before the backup)

  • Author

so after running the disk check i stopped and restarted the array and disk 7 is back.

 

i still have no idea what keeps opening all those files.  at first i thought it was because the windows 7 "always available offline" feature was enabled on one of my shares, but i disabled that and its still happening.

 

my only other thought is that i have windows 7 backup running every night (and every night it tells me it fails - i am assuming because the array craps out during or before the backup)

 

i am not home right now - i have been remoting in to my home machine from work to get the syslog and stuff so i think i will have to wait till i get home and i am in front of the console to run the memtest right?

Yes, you need to select it from the boot menu.  Really tough to do remotely.

  • Author

ok thats what I thought - well I will have to run that one night this week when I am home and i will be sure to post after i do that.

 

thanks again for all the help!!

i have been remoting in to my home machine from work

How do you mean? Are you remoting directly to your unRAID server?

Or are you remoting to a windows machine on your local network, and checking on your unRAID from there?

 

Either way, if you want to start the memtest remotely, there is a way to do so:

Edit the file 'syslinux.cfg' that's on your boot flash key, and move the line 'menu default' from the unRAID label to the Memtest86 label.

Then reboot your server. You won't be able to monitor how memtest is doing, but you'll see that when you get home.

 

NOTE: Before you edit anything, make sure you read this:

http://lime-technology.com/wiki/index.php?title=FAQ#Why_do_my_scripts_have_problems_with_end-of-lines.3F

 

Archived

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

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.