My unRAID setup had been running great for months and it suddenly became unresponsive so I tried to shut down and restart.  But when I restarted.  The drives remain at "Mounting" and does not progress any further.  Included is my syslog file.

 

Any help and/or suggestions would be highly appreciated.  Thanks in advance.

syslog.txt

My unRAID setup had been running great for months and it suddenly became unresponsive so I tried to shut down and restart.  But when I restarted.  The drives remain at "Mounting" and does not progress any further.  Included is my syslog file.

 

Any help and/or suggestions would be highly appreciated.  Thanks in advance.

 

What version of unRAID are you running? What was going on when the server went unresponsive?  Have you tried refreshing the unRAID web page? What does unMenu say about the status of the server?

 

It looks like a parity sync started and found 128 errors.  This is not to be unexpected if you had to shutdown by holding the power button.

 

A little more info and another syslog would be great.

It is probably re-playing the transactions in the file-system journals.  I've seen that take as long as 15 minutes if there was a lot of write activity prior to the abrupt shutdown.

 

Just let it finish its mounting....

 

Joe L.

I'm running unRAID 4.5.6.

 

Yes, I had to shut down by holding the power button.  I've left it in the "Mounting" phase for about two hours now and it's still mounting.  However, there is a lot of read and write activity.  Most of it on the parity drive.  It appears to be doing a parity check.

I'm running unRAID 4.5.6.

 

Yes, I had to shut down by holding the power button.  I've left it in the "Mounting" phase for about two hours now and it's still mounting.  However, there is a lot of read and write activity.  Most of it on the parity drive.  It appears to be doing a parity check.

It is doing exactly that.  Have you refreshed the browser?  It does not update itself.

Yes.  I have refreshed the browser many times.  It is still "Mounting" and the reads and writes are still climbing.  However, it seems to be going very slow.  After almost 3 hours, the parity drive has only read about 10,500 and written about 9,500.

Yes.  I have refreshed the browser many times.  It is still "Mounting" and the reads and writes are still climbing.

 

As long as you see read/write counts still increasing, journal replay is still going on.  in syslog you should see in the end how many has been replayed back.

 

Meanwhile your syslog shown, parity check is in progress, maybe due to dirty shutdown. one interesting thing is why system try to spin down disk 0/3 right after system is up? the default spin down timer is 1 hour.

 

 

Nov  1 12:26:37 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks.

Nov  1 12:26:46 Tower ntpd[2687]: synchronized to 169.229.70.201, stratum 3

Nov  1 12:27:00 Tower unmenu-status: Starting unmenu web-server

Nov  1 12:27:16 Tower kernel: mdcmd (27): spindown 0

Nov  1 12:27:17 Tower kernel: mdcmd (28): spindown 3

 

Nov  1 12:29:44 Tower kernel: md: parity incorrect: 128

 

Yes.  I have refreshed the browser many times.  It is still "Mounting" and the reads and writes are still climbing.  However, it seems to be going very slow.  After almost 3 hours, the parity drive has only read about 10,500 and written about 9,500.

 

Attach another syslog if you could.  The read and write count that is going up is probably because of the parity check that is going on.

 

Also, if you have unMenu installed try to open it and look at what might be going on with the server.

Here is the most recent syslog.  Thanks to everyone for the help.

syslog-2010-11-01.txt.zip

Don't know if this helps but i just restart my UnRAid with the reset button and when the server came up started a arity check and the disk showed as mounting for around 10 min. Over those 10 Mins the parithy check was running super slow (over 1300 mins for 2.2 TB data).

 

After a while the disk mounted and the parity time went down to normal.

 

I reset the box, was't necesary shut down

I'm not exactly sure what I'm reading, but it looks like the parity drive may be the center of my problems...

I'm not exactly sure what I'm reading, but it looks like the parity drive may be the center of my problems...

From a quick look through the syslog I would agree.  it looks like there are a lot of read errors happening on the parity drive.

 

disk sdf seems to be having trouble with a data cable or something as it keeps doing this:

ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
Nov  1 12:59:53 Tower kernel: ata3.00: irq_stat 0x40000001
Nov  1 12:59:53 Tower kernel: ata3.00: failed command: READ DMA EXT
Nov  1 12:59:53 Tower kernel: ata3.00: cmd 25/00:10:57:00:48/00:00:d1:00:00/e0 tag 0 dma 8192 in
Nov  1 12:59:53 Tower kernel:          res 51/40:00:5f:00:48/00:00:d1:00:00/e0 Emask 0x9 (media error)
Nov  1 12:59:53 Tower kernel: ata3.00: status: { DRDY ERR }
Nov  1 12:59:53 Tower kernel: ata3.00: error: { UNC }
Nov  1 12:59:54 Tower kernel: ata3.00: configured for UDMA/133
Nov  1 12:59:54 Tower kernel: ata3: EH complete

 

This is sdf:

Nov  1 12:45:57 Tower kernel:scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EADS-00S 01.0 PQ: 0 ANSI: 5

Is it safe to pull the parity drive and run the array for several days until I can order a replacement?

Is it safe to pull the parity drive and run the array for several days until I can order a replacement?

 

Safe is a matter of opinion. If you feel comfortable running without protection them go ahead and do it.

 

Wait for JoeL or someone to give some input on there opinion of the problem.

 

If you do not have unMenu installed try to get it installed and see what it tells you about the status of the array.

 

I would not run the server without a parity drive but I usually air on the side of caution.

 

Try to get a smartctl report from the drive and report back on what it says.

Is it safe to pull the parity drive and run the array for several days until I can order a replacement?

 

Without parity disk, you are running you server without protection, same as those USB external disks you have. If you are comfortable with this situation you can do it. You might want to check/replace cables to this disk see if it helps, so many read errors at same time, doesn't look normal.

 

---------------------- From your syslog ---------------------------------------------------------------------------------------------

 

Media error : Software detect a media error.

DRDY ERR : Device is ready with error

UNC : Uncorrectable error - often due to bad sectors on the disk

 

Nov  1 13:00:00 Tower kernel: ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0

Nov  1 13:00:00 Tower kernel: ata3.00: irq_stat 0x40000001

Nov  1 13:00:00 Tower kernel: ata3.00: failed command: READ DMA EXT

Nov  1 13:00:00 Tower kernel: ata3.00: cmd 25/00:10:57:00:48/00:00:d1:00:00/e0 tag 0 dma 8192 in

Nov  1 13:00:00 Tower kernel:          res 51/40:00:5f:00:48/00:00:d1:00:00/e0 Emask 0x9 (media error)

Nov  1 13:00:00 Tower kernel: ata3.00: status: { DRDY ERR }

Nov  1 13:00:00 Tower kernel: ata3.00: error: { UNC }

Nov  1 13:00:02 Tower kernel: ata3.00: configured for UDMA/133

Nov  1 13:00:02 Tower kernel: ata3: EH complete

 

The weird thing is that I don't have any PATA devices connected and never have.

The weird thing is that I don't have any PATA devices connected and never have.

 

Your syslog doesn't say you have either, so why it is weird? 

 

 

Nov  1 12:45:57 Tower emhttp: Device inventory:

Nov  1 12:45:57 Tower emhttp: pci-0000:00:1f.2-scsi-0:0:0:0 host3 (sdf) WDC_WD20EADS-00S2B0_WD-WCAVY1848948

Nov  1 12:45:57 Tower emhttp: pci-0000:00:1f.2-scsi-1:0:0:0 host4 (sdg) ST31500341AS_9VS26V8A

Nov  1 12:45:57 Tower emhttp: pci-0000:00:1f.2-scsi-2:0:0:0 host5 (sdh) WDC_WD20EADS-00S2B0_WD-WCAVY1818991

Nov  1 12:45:57 Tower emhttp: pci-0000:00:1f.2-scsi-3:0:0:0 host6 (sdi) ST31500341AS_9VS26NCP

Nov  1 12:45:57 Tower emhttp: pci-0000:02:00.0-scsi-1:0:0:0 host1 (sdb) ST31500341AS_9VS26R1M

Nov  1 12:45:57 Tower emhttp: pci-0000:02:00.0-scsi-1:1:0:0 host1 (sdc) ST31500341AS_9VS26ZC8

Nov  1 12:45:57 Tower emhttp: pci-0000:02:00.0-scsi-1:2:0:0 host1 (sdd) ST31500341AS_9VS0MQZ4

Nov  1 12:45:57 Tower emhttp: pci-0000:02:00.0-scsi-1:3:0:0 host1 (sde) WDC_WD20EARS-00J2GB0_WD-WCAYY0176691

 

Okay.  So I pulled the parity drive and connected it to my Mac.  Smart Utility found over 1400 bad sectors.  I never did have any luck with Western Digitals...

Okay.  So I pulled the parity drive and connected it to my Mac.  Smart Utility found over 1400 bad sectors.  I never did have any luck with Western Digitals...

 

Fun, Fun...

 

Now see, I have just the opposite experience.  The WD drives I have in my server have been running great.  They are 500GB drives that have given me 0 trouble since i bought them.  The drives that I have the most trouble with are my Seagates (I think i have sent in more RMA's on seagate's then I have drives in my server).

 

The drives that have given me the least amount of trouble are the 2 Hitachi 2Tb 7200RPM drives.

Just luck of the draw, I suppose...  Last month, I had to return a Scorpio Blue after only a week of use...

 

Anyway, thanks to everyone for all the help.  I really appreciate it!!