July 27, 201114 yr short story: rebooted array and all discs (1-11) show green and parity shows orange. I click "start" and after the page refreshes, nothing has changed. What could be causing my array to suddenly not start and what can I do about it? (Parity was checked a couple of weeks ago w/no errors and since I'm running 4.4, I've had this going for awhile) Thanks for any and all help!
July 27, 201114 yr short story: rebooted array and all discs (1-11) show green and parity shows orange. I click "start" and after the page refreshes, nothing has changed. What could be causing my array to suddenly not start and what can I do about it? (Parity was checked a couple of weeks ago w/no errors and since I'm running 4.4, I've had this going for awhile) Thanks for any and all help! We need the information asked for in the stickies at the top of this subforum. Give us a compelete hardware breakdown and a copy of the syslog. Instructions for getting the syslog can be found via the troubleshooting link in my signature.
July 27, 201114 yr Author Trying-when I enter "//tower/log/syslog" I get an "Oops! This link appears to be broken" error message- Any chance we're just looking at a parity drive failing/failed?
July 27, 201114 yr No way to tell without more information. If you have no network connection to the server, then you will need to hook up a keyboard and monitor and capture a syslog from the system console. The command is: cp /var/log/syslog /boot That should take just a second to run. After that completes, type 'powerdown' to cleanly shut down the server. Once the server is powered off, remove the flash drive and hook it up to another computer. The syslog will be in the root directory of the flash drive. Rename it and add a '.txt' file extension. Attach it to your next post.
July 27, 201114 yr Trying-when I enter "//tower/log/syslog" I get an "Oops! This link appears to be broken" error message- Any chance we're just looking at a parity drive failing/failed? You can't get to the syslog via the network. You have to log into the server via telnet. This post explains it pretty well.
July 27, 201114 yr Author I'll see what I can accomplish later - thanks for the help. You can't get to the syslog via the network. You have to log into the server via telnet This post explains it pretty well. Actually, it didn't explain it very well at all-that post was what I'd used to try and and get to the syslog via the network... And simply saying "Via the console or telnet session, you can type this command:" doesn't "explain it pretty well" at all- I apologize if I sound snippy - frustrated a bit (not the first, I'm sure!) and w/o having my machine connected to a monitor/keyboard I don't seem to be able to do anything btw-I do have a network connection to the server-which is how I'm able to see the dashboard and attempt the "start" - it's just the "//tower/log/syslog" (from the post that was linked to) that doesn't work.
July 27, 201114 yr btw-I do have a network connection to the server-which is how I'm able to see the dashboard and attempt the "start" - it's just the "//tower/log/syslog" (from the post that was linked to) that doesn't work. Are you typing the //tower/log/syslog into the web browser or into Explorer? Also, I do not remember which version of unRAID the //tower/log/syslog support was added. The version you are running may be older than when that was added. Do a google search for "telnet" and "putty" and you should be able to figure out how to get the syslog off the machine.
July 28, 201114 yr sdl=disk1 appears to be bad. Enter "smartctl -a -d ata /dev/sdl" on the command line and post the results.
July 28, 201114 yr Author error while loading shared libraries: libstdc++.so.6: cannot open shared object file: No such file or directory
July 28, 201114 yr Author upgraded to 4.7 so that all these commands will now work can't see the whole screen, but have a line that reads: 40 51 08 00 00 00 e0 Error: UNC 8 sectors at LBA = 0x00000000 = 0
July 28, 201114 yr Author New syslog attached after 4.7 upgrade (and now I can see it over the network) syslog.txt
July 28, 201114 yr New syslog attached after 4.7 upgrade (and now I can see it over the network) Now you can try smartctl -a /dev/sdl and post the output. The disk errors looked like media errors, but it could be more (media errors are unreadable sectors) Look for sectors pending re-allocation, or already re-allocated in the smart report.
July 28, 201114 yr Author your patience is much appreciated- not sure what to do after running cmartctl- doesn't show up in syslog and I don't know how to grab the output
July 28, 201114 yr your patience is much appreciated- not sure what to do after running cmartctl- doesn't show up in syslog and I don't know how to grab the output its not cmartctl- it is smartctl -a /dev/sdl
July 28, 201114 yr Author I understand-i was abbreviating it in my post ran it and the results are (as stated in a previous post) too long for me to see on my screen I don't know how to capture it for you and the highest line I can read is the same as in a previous post: 40 51 08 00 00 00 e0 Error: UNC 8 sectors at LBA = 0x00000000 = 0
July 28, 201114 yr I understand-i was abbreviating it in my post ran it and the results are (as stated in a previous post) too long for me to see on my screen I don't know how to capture it for you and the highest line I can read is the same as in a previous post: 40 51 08 00 00 00 e0 Error: UNC 8 sectors at LBA = 0x00000000 = 0 Ok, I just wanted to be sure you can try: smartctl -a /dev/sdl > /boot/smart_report_sdl.txt After that is done there will be a file (smart_report_sdl.txt) on your flash drive.
July 28, 201114 yr attached! The drive has some current pending sectors looking to be reallocated most likely. You can try rebuilding onto the same drive if you like. You will need to unassign the drive from the slot, start the array, make sure you can see the content on the simulated drive, stop the array, add the drive back into the same slot, start the array.
July 28, 201114 yr Author Thanks for all your help - will give it a go later today and report back- thanks!
July 28, 201114 yr Author Nope - did everything you suggested, but when I reassigned disk 1 and tried to restart the array I had the same problem- bad disk then??
July 28, 201114 yr Nope - did everything you suggested, but when I reassigned disk 1 and tried to restart the array I had the same problem- bad disk then?? We don't know... you did not attach a new syslog.
July 29, 201114 yr Author You will need to unassign the drive from the slot, start the array, make sure you can see the content on the simulated drive, stop the array, add the drive back into the same slot, start the array. Yup - not so good news. In the process of doing exactly this-the server decided that since drive 1 was missing/unassigned from the array, it was time to conduct/start a parity synch w/o asking for any input first. I've got a few things I'm going to try over the next few days to try and recover the data on that drive- I do appreciate the help though and am confident it will be sorted out in time.
July 29, 201114 yr How did you shutdown? The system will start a parity check if not shutdown cleanly.
Archived
This topic is now archived and is closed to further replies.