Jump to content

No Web Interface and drive access is super slow


Recommended Posts

I went home today and decided at lunch to watch a little on XBMC. Fired up and watched a tv show I had recorded on Disk2(sdc). I then decided to check out how well a movie encoded on (sdb)Disk1. I noticed it started up really slow and I was confused. I thought well it is rather large, but I've never had an issue before other than when I thought I had a dieing drive. I tried watching video on another drive and it played just fine.

 

I walked into my room where the server lives and I had no web interface and I could login and pull a syslog which I've attached. I also attached syslog2 which is the results of the reboot.  

 

These are my drives in my machine

 

(sda) WDC_WD20EARS-00MVWB0_WD-WMAZ20201794 - Parity

(sdb) WDC_WD15EADS-00S2B0_WD-WCAVY1447030  - Disk1

(sdc) WDC_WD15EADS-00S2B0_WD-WCAVY1371380  - Disk2

(sdd) WDC_WD20EARS-00MVWB0_WD-WMAZA0138511 - Disk3

(sde) WDC_WD15EADS-00P8B0_WD-WMAVU0057608  - Disk4

 

Just from reading in Syslog it appears around Aug  3 07:45:02 ATA2 started going bonkers, which I'm assuming means in my case (sdb). Is that correct? I didn't have time to run a Smart test since I had to head back to work, but I'm guessing that drive is the issue and I've had an issue with it before. Last time it kinda acted up and when I ran a smart test on it, it didn't really indicate anything, but I do have a spare drive I can place in its place and move on.

 

Of course when I restarted my machine man it was a slow array start and said mounting forever, but I'm guessing thats because there is a problem and unRAID is trying to recover from it. Its doing a parity check on its own as of right now.

syslog.txt

syslog2.txt

Link to comment

Not yet its still beating its self up with a parity check. It launched by is self when I first booted it up. As soon as its done I'll run a couple of smart tests.

 

Oddly enough I just confused with all the ATA2 stuff in the logs because I just assumed ATA2 meant the second disk on the board since sdb seemed like the one that was a bit unresponsive today opposed to the sdc which you mentioned.

Link to comment

My biggest want is to identify which drive ATA2 is so I know to check its cables and make sure everything is fine with it. I'm feeling rather dumb honestly LOL

My mother board has 1,2,3,4,5,6 at least I think it does for Sata connections. Linux generally is sda,sdb,sdc,sdd,sde, but when I see ATA2 in the syslogs is it linux saying its the second drive sdb which would make since since its the drive that seemed really un-responsive.

 

Somebody else mentioned SDC, but honestly I'm not sure since its super quick and never glitched. Anyways throw me a bone here so I can do what I need to do and as well so I don't feel so dumb. ;)

Link to comment

My biggest want is to identify which drive ATA2 is so I know to check its cables and make sure everything is fine with it. I'm feeling rather dumb honestly LOL

My mother board has 0,1,2,3,4,5 at least I think it does for Sata connections. Linux generally is sda,sdb,sdc,sdd,sde, but when I see ATA2 in the syslogs is it linux saying its the second drive sdb which would make since since its the drive that seemed really un-responsive.

 

Somebody else mentioned SDC, but honestly I'm not sure since its super quick and never glitched. Anyways throw me a bone here so I can do what I need to do and as well so I don't feel so dumb. ;)

 

I am not sure if this is any help or not, but here is an example from my tower:

 

From Devices in GUI:

parity device: pci-0000:00:11.0-scsi-5:0:0:0 host6 (sdf) Hitachi_HDS722020ALA330_JK1170YAGS9G8T

disk1 device: pci-0000:00:11.0-scsi-0:0:0:0 host1 (sda) WDC_WD20EARS-00J2GB0_WD-WCAYY0217419

disk2 device: pci-0000:00:11.0-scsi-1:0:0:0 host2 (sdb) SAMSUNG_HD204UI_S2H7J1PB500855

disk3 device: pci-0000:00:11.0-scsi-2:0:0:0 host3 (sdc) SAMSUNG_HD204UI_S2H7J1PB500857

disk4 device: pci-0000:00:11.0-scsi-3:0:0:0 host4 (sdd) Hitachi_HDS722020ALA330_JK1174YAHLZZWW

disk5 device: pci-0000:00:11.0-scsi-4:0:0:0 host5 (sde) Hitachi_HDS722020ALA330_JK1170YAHLWY2P

disk6 device: pci-0000:04:05.0-scsi-1:0:0:0 host8 (sdg) WDC_WD10EALS-00Z8A0_WD-WCATR0710290

 

From SYSLOG

Aug  5 09:56:14 TODD-Svr kernel: ata3.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133 (Drive related)

Aug  5 09:56:14 TODD-Svr kernel: ata2.00: ATA-8: SAMSUNG HD204UI, 1AQ10001, max UDMA/133 (Drive related)

 

The two Samsung drives HD204UI, are referred to as "host 2" and "host 3".  These correlate to ATA2 and ATA3 respectively in my syslog.  The first in the string of 4 numbers IE 1:0:0:0, is the port number on my MB.  So if I am interpreting all this correctly.  My first samsung drive serial number S2H7J1PB500855 is ATA2 in my syslog and port 1 on my MB.

 

Hopefully you can use similar methods to figure out what drive is ATA-2 in your system.

 

As a side note, the port numbers on my MB (0-5) do NOT match between what the book shows for their respective locations and what actually shows up in software. The only way I figured out where they actually were was matching serial numbers based on the GUI.

 

Don't be confused by "Host 8" which is port 1 on a separate card.  Host 7 is an external port I don't use and obviously port 0 not shown.

 

Link to comment

Not yet its still beating its self up with a parity check. It launched by is self when I first booted it up. As soon as its done I'll run a couple of smart tests.

 

Oddly enough I just confused with all the ATA2 stuff in the logs because I just assumed ATA2 meant the second disk on the board since sdb seemed like the one that was a bit unresponsive today opposed to the sdc which you mentioned.

Hard to tell.  Linux does not give an easy way to map the ATA2 to a device that I've found.

 

In the syslog we see this:

Aug  2 11:11:29 Tower kernel: ata1.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata3.00: ATA-8: WDC WD15EADS-00S2B0, 01.00A01, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata5.00: ATA-8: WDC WD15EADS-00P8B0, 01.00A01, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata5.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata2.00: ATA-8: WDC WD15EADS-00S2B0, 01.00A01, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

 

 

and then this showing how That same make/model drive is mapped to scsi 1:0:0:0 and that it in turn is /dev/sdb:

Aug  2 11:11:29 Tower kernel: scsi 0:0:0:0: Direct-Access    ATA      WDC WD20EARS-00M 50.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: scsi 1:0:0:0: Direct-Access    ATA      WDC WD15EADS-00S 01.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel:  sdb:

Aug  2 11:11:29 Tower kernel:  sda:

Aug  2 11:11:29 Tower kernel: scsi 2:0:0:0: Direct-Access    ATA      WDC WD15EADS-00S 01.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: scsi 3:0:0:0: Direct-Access    ATA      WDC WD20EARS-00M 50.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel:  sdd:

Aug  2 11:11:29 Tower kernel:  sdc:

Aug  2 11:11:29 Tower kernel: scsi 4:0:0:0: Direct-Access    ATA      WDC WD15EADS-00P 01.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

 

Link to comment

Welp unless somebody see's something wrong with my Smart tests I'm feeling a bit dazed and confused lol. I just quadruple checked all my power cables everything is tight and they are straight off the power supply and all my Sata cables are locking.

 

I've had this same exact issue several months ago except I had a red ball on the drive and the web interface worked and my fix before was I pulled out what I thought was the problem disk sdb realized I didn't have a spare disk and threw it back in. It rebuilt and well its been running what I thought was fine for months since there was no indication in the Smart report. Yesterday I was tinkering around and did a reboot and well it went a little bonkers.

 

Of course my machine is completely shut down because I took it outside to blow it out and give all the cables a visual inspection. I guess once its back up I'll see what the little thing spits out in the syslogs.

 

I might just drop in a new drive anyways, but if its a power issue, cable issue or heck something else it will show its head again and at least I'll know, but if the logs don't show anything with the smart reports then I can only assume its something else.

Link to comment

Not yet its still beating its self up with a parity check. It launched by is self when I first booted it up. As soon as its done I'll run a couple of smart tests.

 

Oddly enough I just confused with all the ATA2 stuff in the logs because I just assumed ATA2 meant the second disk on the board since sdb seemed like the one that was a bit unresponsive today opposed to the sdc which you mentioned.

Hard to tell.  Linux does not give an easy way to map the ATA2 to a device that I've found.

 

In the syslog we see this:

Aug  2 11:11:29 Tower kernel: ata1.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata1.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata3.00: ATA-8: WDC WD15EADS-00S2B0, 01.00A01, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata3.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata5.00: ATA-8: WDC WD15EADS-00P8B0, 01.00A01, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata5.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata2.00: ATA-8: WDC WD15EADS-00S2B0, 01.00A01, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata2.00: 2930277168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

Aug  2 11:11:29 Tower kernel: ata4.00: ATA-8: WDC WD20EARS-00MVWB0, 50.0AB50, max UDMA/133

Aug  2 11:11:29 Tower kernel: ata4.00: 3907029168 sectors, multi 0: LBA48 NCQ (depth 31/32), AA

 

 

and then this showing how That same make/model drive is mapped to scsi 1:0:0:0 and that it in turn is /dev/sdb:

Aug  2 11:11:29 Tower kernel: scsi 0:0:0:0: Direct-Access     ATA      WDC WD20EARS-00M 50.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: scsi 1:0:0:0: Direct-Access     ATA      WDC WD15EADS-00S 01.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel: sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel:  sdb:

Aug  2 11:11:29 Tower kernel:  sda:

Aug  2 11:11:29 Tower kernel: scsi 2:0:0:0: Direct-Access     ATA      WDC WD15EADS-00S 01.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: scsi 3:0:0:0: Direct-Access     ATA      WDC WD20EARS-00M 50.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 3:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel: sd 2:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Aug  2 11:11:29 Tower kernel:  sdd:

Aug  2 11:11:29 Tower kernel:  sdc:

Aug  2 11:11:29 Tower kernel: scsi 4:0:0:0: Direct-Access     ATA      WDC WD15EADS-00P 01.0 PQ: 0 ANSI: 5

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 TB/1.36 TiB)

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] Write Protect is off

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00

Aug  2 11:11:29 Tower kernel: sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

 

Unfortunately, I missed that he has TWO drives with the same make/model.  The other being

/dev/sdc.

Aug  2 11:11:29 Tower emhttp: Device inventory:

Aug  2 11:11:29 Tower emhttp: pci-0000:00:11.0-scsi-0:0:0:0 host0 (sda) WDC_WD20EARS-00MVWB0_WD-WMAZ20201794

Aug  2 11:11:29 Tower emhttp: pci-0000:00:11.0-scsi-1:0:0:0 host1 (sdb) WDC_WD15EADS-00S2B0_WD-WCAVY1447030

Aug  2 11:11:29 Tower emhttp: pci-0000:00:11.0-scsi-2:0:0:0 host2 (sdc) WDC_WD15EADS-00S2B0_WD-WCAVY1371380

Aug  2 11:11:29 Tower emhttp: pci-0000:00:11.0-scsi-3:0:0:0 host3 (sdd) WDC_WD20EARS-00MVWB0_WD-WMAZA0138511

Aug  2 11:11:29 Tower emhttp: pci-0000:00:11.0-scsi-4:0:0:0 host4 (sde) WDC_WD15EADS-00P8B0_WD-WMAVU0057608

Link to comment

Joe L. here is what my device page looks like since I got my machine backup and running.

 

parity device: pci-0000:00:11.0-scsi-0:0:0:0 host0 (sda) WDC_WD20EARS-00MVWB0_WD-WMAZ20201794

disk1 device: pci-0000:00:11.0-scsi-1:0:0:0 host1 (sdb) WDC_WD15EADS-00S2B0_WD-WCAVY1447030

disk2 device: pci-0000:00:11.0-scsi-2:0:0:0 host2 (sdc) WDC_WD15EADS-00S2B0_WD-WCAVY1371380

disk3 device: pci-0000:00:11.0-scsi-3:0:0:0 host3 (sdd) WDC_WD20EARS-00MVWB0_WD-WMAZA0138511

disk4 device: pci-0000:00:11.0-scsi-4:0:0:0 host4 (sde) WDC_WD15EADS-00P8B0_WD-WMAVU0057608

Link to comment

Now I'm really dumbfounded. I turned on my htpc and it was all wigged out. I had to reclone my drive because it was stuck in a boot loop. Strangely enough the last time I had this random problem I rebuilt my htpc afterwards as well. Sure I could chalk it up as a htpc issue but what was with all the syslog entries?

 

I'm running XBMC on a linux build and trying to pull a syslog was well not possible. Next time if/when it happens I'll pull the drive and try to read externally.

 

At first I thought maybe it was a read write issue, but I'm using user shares and only set to read only. So I'm kinda in a confused state. Still don't understand why web interface was gone and all the syslog entries thou.

Link to comment

Archived

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

×
×
  • Create New...