shire Posted June 25 Share Posted June 25 (edited) Hello together, a fews days ago I saw a dead drive on the array (red x). I ordered a replacment drive which I received today. Than I did the following: 1. Powered down the server 2. Switch drive 3. Start server 4. Assign new drive 5. Selecte rebuilt For some reason the system stalled and showed 'Unknown' for finishing time and 'Paused' at the bottom left of the screen (also almost no writing to replacment disk). So I had to reboot the system. Now it only shows the 'Start will bring the array' online. I doesn't mention anything of rebuilding the arry. What can I do? Btw.: The connection between drive and board looks good. Edited June 25 by shire Quote Link to comment
itimpi Posted June 25 Share Posted June 25 You are likely to get better informed feedback if you attach your system’s diagnostics zip file to your next post in this thread. It is always a good idea when asking questions to supply your diagnostics so we can see details of your system, how you have things configured, and the current syslog. 1 Quote Link to comment
shire Posted June 25 Author Share Posted June 25 (edited) Attached Edited June 25 by shire Quote Link to comment
shire Posted June 25 Author Share Posted June 25 Drive 18 is the new replacment drive. Quote Link to comment
JorgeB Posted June 25 Share Posted June 25 Jun 25 13:01:36 Tower kernel: sd 10:0:0:0: [sdo] tag#9935 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=1s Jun 25 13:01:36 Tower kernel: sd 10:0:0:0: [sdo] tag#9935 CDB: opcode=0x8a 8a 00 00 00 00 00 00 00 0c 90 00 00 04 00 00 00 Jun 25 13:01:36 Tower kernel: I/O error, dev sdo, sector 3216 op 0x1:(WRITE) flags 0x4000 phys_seg 128 prio class 2 Jun 25 13:01:36 Tower kernel: md: disk18 write error, sector=3152 Jun 25 13:01:36 Tower kernel: md: disk18 write error, sector=3160 Jun 25 13:01:36 Tower kernel: md: disk18 write error, sector=3168 Jun 25 13:01:36 Tower kernel: md: disk18 write error, sector=3176 Jun 25 13:01:36 Tower kernel: md: disk18 write error, sector=3184 Write failed during the rebuild, check/replace cables or swap slots and try again. 1 Quote Link to comment
shire Posted June 25 Author Share Posted June 25 Changed the cable and moved the port from the add-on card to the mainboard. I started the array and it still says "Start will bring the array online" and nothing of rebuild. Quote Link to comment
itimpi Posted June 25 Share Posted June 25 5 minutes ago, shire said: Changed the cable and moved the port from the add-on card to the mainboard. I started the array and it still says "Start will bring the array online" and nothing of rebuild. That would be expected if the drive currently shows as disabled (which is likely if you got a failure in the previous rebuild attempt). In such case you need to follow the procedure outlined here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. 1 Quote Link to comment
shire Posted June 25 Author Share Posted June 25 47 minutes ago, itimpi said: That would be expected if the drive currently shows as disabled (which is likely if you got a failure in the previous rebuild attempt). In such case you need to follow the procedure outlined here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. Okay. That is a lot of text. I can't go any further form the present screen with 'Start will bring the array online'. So I should start maintenance mode and do a parity check/rebuilt? (optional) Tick the box to start in Maintenance mode. If you start the array in Maintenance mode you will need to press the Syncbutton to trigger the rebuild. The advantage of doing this in Maintenance mode is that nothing else can write to the array while the rebuild is running which maximises speed. The disadvantage is that you cannot use the array in the meantime and until you return to normal mode cannot see what the contents of the disk being rebuilt will look like. Drive18 shows indeed as disabled / emulated data... Quote Link to comment
Solution itimpi Posted June 25 Solution Share Posted June 25 You need to follow the steps outlined in the link I gave. For instance the first step is NOT to start the array but to unassign the disabled disk. 1 Quote Link to comment
shire Posted June 25 Author Share Posted June 25 Thanks!! It is rebuilding now. I guess the cable is dead or the port on my SATA add-on card. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.