When I try to update the mymovies MCE database on any movies on disk4, the application freezes or crashes.

I tried with different versions of mymovies, on different PCs in the house. I updated the unraid server to the latest beta, still same problem.

I can still play the files on the disk, a parity check was performed finding no errors.

I tested updating other movies on other drives, and mymovies works fine...

Find attached the log file

I am now getting error messages when opening the divx or dvd folders on drive 4. Inconsistent behaviour (drive stops responding and windows explorer is unable to browse the drive). After the error message, if I click on it again, I might get a response from the drive.

Sounds like the drive could be going...you could try and copy one of the movies you played to a different drive and see if it still does it.  I know with Mymovies I also used a mapped drive instead of UNP just to help windows out.  I know if I play a movie just in WMP then it will sometimes crash/stop responding but playing the same movie over a mapped drive WMP works like a champ.

 

Movies play fine. The problem seems to write to the drive, not read from it...

I am going to test today by replacing the drive with a brand new one, and see if unraid can restore the files to it.

If it works, I wil format the faulty drive, and start from scratch.

Replaced the drive, unraid rebuilt the data on the new drive, and I am having the same issue as I was having before.

Data corruption?

How to check for data corruption on the drive?

Tomm, can you please help me out?

I have mapped the drive, and I can see the folder structure (DVDS and DIVX), but when I click on any of the two folders, the window times out.

If I use ms-dos I can go as far as the subfolder (e.g \good boy) and the divx file inside....

Just tried to stop the array, and when I do that, the unraid web application stops responding.

I have to manually reboot the machine, and that should not happen, should it?

What version of unraid are you running.  I've had a few hiccups with unraid but when I've rebooted everything turned out to be fine.  I think my switch might be dying on me.  You can always try to telnet into the server and use unmenu (search for it in the user customizations section)

I am running the latest beta of server 4.

I have logged in via telnet, and the command restart does not work, apart from the message in dos, the server fails to reboot. I have to Reboot it manually.

Looking at your log, there appears to be a file system corruption.  Please follow directions in this thread.

Looking at your log, there appears to be a file system corruption.  Please follow directions in this thread.

 

Do I have to reiserfsck only drive4, which is the one showing problems? Or is the file system corruption affecting all the drives?

Thanks for getting back to me Tomm!

Please start with disk4, i.e., "/dev/md4"

Run reiserfsck: this is the result

 

 

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

Will put log info to 'stdout'

 

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

root@Tower:~# reiserfsck /dev/md4

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/md4

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 Fri Jul  6 19:38:04 2007

###########

Replaying journal..

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

Checking internal tree..finished

Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs.

Checking Semantic tree:

finished

1 found corruptions can be fixed when running with --fix-fixable

###########

reiserfsck finished at Fri Jul  6 19:49:57 2007

###########

root@Tower:~#

Typed the command

 

reiserfsck --fix-fixable /dev/md4

 

Let's see what happens...

 

###########

reiserfsck --fix-fixable started at Fri Jul  6 20:19:28 2007

###########

Replaying journal..

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

Checking internal tree..finished

Comparing bitmaps..vpf-10630: The on-disk and the correct bitmaps differs. Will

be fixed later.

Checking Semantic tree:

finished

No corruptions found

There are on the filesystem:

        Leaves 120052

        Internal nodes 741

        Directories 334

        Other files 1431

        Data block pointers 121323342 (0 of them are zero)

        Safe links 0

 

###########

reiserfsck finished at Fri Jul  6 20:35:52 2007

###########

root@Tower:~#

root@Tower:~#

Am able again to write the mymovies.xml files to the drive, but MyMovies crashed again whilst writing to the drive.

Will report on the results later on. Parity was being calculated, I stopped that and will restart it later on.

Thanks Tomm, it worked, I was able to finish to assign covers to the drive affected.

Now I know what to do if I have problems accessing a drive again!

If I want to format a drive (my old drive needs to be wiped now that I fixed the issue on the replacement drive) is there a command I can use from tower, once I have mapped it?

I have a feeling that that drive is now dead....

It says disk missing when I restarted the tower, a number of times.

I have ordered a new disk, so I can rebuild it.

It is the second Seagate that dies on me, since I started building the server about a year ago. Isn't the mortality rate a bit high?

Could I be doing something wrong? I restart the server about once a month, when it stops connectivity with the network. All disks (9) are in "4 in 3" caddies, provided with the Coolermaster case.

Temperature should not be an issue, as the drives are mostly spun down, and when they are all spinning the temp is below 40C.

2 Seagates failing in one year is probably just a case of bad luck.

 

You say it shows up as "missing" - does it show up in the bios?

 

All  your symptoms do point to a failing drive.

Replaced the drive, and halfway through rebuilding the drive, the server shut down. I restarted the server, and it continued rebuilding the drive (I hope succesfully).

 

Log file attached

Nothing unusual in that log.  When you say, "the server shut down", do you mean that it powered itself off?

 

What you might have to do is actively monitor the system log in a telnet window in order to capture messages that might indicate the reason for crash.  Refer to this topic in the wiki.

I found out that the drive had nothing wrong with it, when after rebuilding the new drive, it was showing the same issue (drive not detected upon bootup).

It turns out that the common element between the two drives, is that they are both on the same TX Sata card.

As I was unable to slot card in, I removed the metal plate and simply inserted it in the PCI slot. That obviously is creating issues, and I need to find an alternative solution.

When I said, the server has shut down, I did mean it powered itself off.

I can't recall having seen any cases of "spontaneous power off".

 

Re: sata controller - yep, you need to secure that thing...