May 31, 20179 yr I'm in the process of setting up my second unRAID server (set up first 2 months ago, so still inexperienced with it all). Going to be a wall of text, but want to give as much context as possible (just ask if more info is needed!). Step by step how it happened Last night I wanted to expand the array from 2 disks to 3 after the 3rd passed a 3 cycle preclear without problems. 1) I click to stop the array, page seems unresponsive, no reaction apart from loading page in bottom left of browser. 2) Let it sit for a couple of minutes, then hits refresh on the page. Array has stopped. 3) Add new drive as Array 3, then hit start array. Again it's unresponsive. 4) Let it sit for another couple of minutes. Hits refresh, but now it just keeps not loading. Open new tab: keeps loading (tab circle spinning). Try Firefox, same thing 5) Let it sit overnight, still no response Hardware Dell ProLiant DL180 G6 2x Intel Xeon X5550 24GB RAM IBM M1015 (crossflashed to LSI9211-8i IT mode) 1x HGST Deskstar NAS 6TB (brand new) 3x Seagate Barracuda 4TB (brand new) 2x WD Green 2TB (from 2011) 1x WD Green 1.5TB (from 2010) 1x Seagate Barracuda 1.5TB (from 2010) Background 2 of the 4TB disks had been precleared in a different system using 3 cycles, then 1 cycle in this system. The 3rd disk was precleared with 3 cycles in this system. [problem occurred when adding this disk to array] At the same time as the array expansion happened all 4 of the smaller disks (2TB and 1.5TB) were preclearing [Was it a bad idea expanding the array when this was going on?]. The system has really only been powered on this one time after adding the disks (the 6TB and 4TBs were added when server was off, the smaller disks were added with machine running, but unRAID picked them up no problem in the GUI, so I assumed no restart was needed) So the attached log contains pretty much the entire systems log. (the time stamps are off, when I refer to last night it shows as around May 30 11AM, and today shows as May 30 10PM). From what I can see in the logs the disk identified as [sdh] is having some problems, I assume this is one of the disks currently preclearing, but don't know which one as I can't find the serial number for that disk. What next The 1.5TB Seagate disk finished preclearing 2 hours after the GUI went unresponsive. I'm able to access through SSH and /servername/flash, so the server is up and running. Just that I'm not able to access the WebGUI. Also 3 of the disks should still be preclearing (2x WD Green 2TB + 1x WD Green 1.5TB). So I'm hesitant to restart the server at the moment. Any help would be much appreciated! syslog.txt
May 31, 20179 yr Looks like disk 1 and 2 have some problems. It would help if you provide a full diagnostic.
May 31, 20179 yr Author Started a diagnostics through SSH: root@SkyLin:/boot# diagnostics Starting diagnostics collection... Been hanging there for 1 hour now. Might have to restart the server, but want to wait until the last 2 disks (2TB WD Greens) have completed the preclear first.
May 31, 20179 yr Community Expert This disk has a pending sector and is causing problems: Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA0207915 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 1 May 30 22:30:30 SkyLin kernel: blk_update_request: critical medium error, dev sdh, sector 0 May 30 22:30:33 SkyLin kernel: sd 1:0:20:0: [sdh] tag#63 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 30 22:30:33 SkyLin kernel: sd 1:0:20:0: [sdh] tag#63 Sense Key : 0x3 [current] May 30 22:30:33 SkyLin kernel: sd 1:0:20:0: [sdh] tag#63 ASC=0x11 ASCQ=0x0 May 30 22:30:33 SkyLin kernel: sd 1:0:20:0: [sdh] tag#63 CDB: opcode=0x28 28 00 00 00 00 00 00 00 20 00 May 30 22:30:33 SkyLin kernel: blk_update_request: critical medium error, dev sdh, sector 0 May 30 22:30:37 SkyLin kernel: sd 1:0:20:0: [sdh] tag#64 UNKNOWN(0x2003) Result: hostbyte=0x00 driverbyte=0x08 May 30 22:30:37 SkyLin kernel: sd 1:0:20:0: [sdh] tag#64 Sense Key : 0x3 [current] May 30 22:30:37 SkyLin kernel: sd 1:0:20:0: [sdh] tag#64 ASC=0x11 ASCQ=0x0 May 30 22:30:37 SkyLin kernel: sd 1:0:20:0: [sdh] tag#64 CDB: opcode=0x28 28 00 00 00 00 08 00 00 01 00 May 30 22:30:37 SkyLin kernel: blk_update_request: critical medium error, dev sdh, sector 8
Archived
This topic is now archived and is closed to further replies.