November 8, 200916 yr I apologize, I didn't save my syslog - I know better for next time... I hadn't opened up my unraid management console for quite a few months, as it's been working behind the scenes great. I decided to check the status of it a few days ago, and noticed a red icon next to one of my disks, and there were some write errors to it. I had parity enabled, and didn't have time to troubleshoot or investigate. I forgot about the errors, and have been writing to the disk ever since, but today I noticed really slow write times - so I opened up the web console and was reminded about the disabled disk. I rebooted hoping this might solve the problem (oops, forgot to save the syslog) and after noticing that didn't help I reseated the cables and finally got the offending disk back to blue status. So my question is - what do I do next: 1) Start and Data Re-build 2) Restore Since the disk was disabled, I'm sure I've written to the array, so not sure how these changes will be updated? Another strange thing happened when trying to save the syslog after my latest reboot - when I tried to copy my syslog to the boot directory (flash drive), after I invoke the cp command, everything in my boot directory goes away? (see telnet session output below)... root@DIRECTO_MEDIA:/# cd boot root@DIRECTO_MEDIA:/boot# ls bzimage* bzroot* config/ memtest* syslinux.cfg* bzimage.433* bzroot.433* ldlinux.sys* menu.c32* syslog* bzimage.old* bzroot.old* license.txt* readme.txt* syslogs/ root@DIRECTO_MEDIA:/boot# cp /var/log/syslog /boot/syslogs/syslog-2009-11-08.txt root@DIRECTO_MEDIA:/boot# ls root@DIRECTO_MEDIA:/boot# ls -l total 0 Any help would be appreciated! I have a wife itching to watch some TV shows
November 8, 200916 yr Author Just noticed some other posts: I think the correct course of action is to actually take the offending drive out so that there is no drive (drive 4 / sdj in my case), and try to start the array like this. Then when that is squared away, try to reincorporate sdj into the mix. Is this correct?
November 8, 200916 yr That still doesn't explain why the stuff on your flash drive disappeared. root@DIRECTO_MEDIA:/boot# ls -l total 0 Have you run memory test lately?
November 8, 200916 yr Author well - I managed to bork that up! was doing a parity check (without the bad drive in the array) - and noticed the guid on my flash drive was -1 (wasn't there)....so I stopped the array, rebooted so I could get a backup of my flash drive, and when I restarted - unraid says parity is all good, drive 4 is recognized as new, and wants to format it... errr - clearly I shouldn't be using this system... is there any way to even attempt at getting the data off this disk? and no - haven;t run a memtest lately...apparently it's now on my list of to do's!
November 8, 200916 yr errr - clearly I shouldn't be using this system... Befor giving up on it, try the new version 4.5.8beta. (After you run your memory test of course)
November 9, 200916 yr Do not install anything else or make any further changes until we can see a syslog ("Capturing your syslog"), and Obtaining a SMART report for the faulty drive. There are many reasons for drives appearing to fail, and more often than not, it is NOT the fault of the physical drive. The drive may be perfectly fine. However, if you have been writing to the virtual drive, then you will probably want to rebuild the drive, once the array has been checked out. The memory test is a good idea, can be run any time. was doing a parity check (without the bad drive in the array) This may have been a mistake. Was it reporting a LOT of errors, and going very slow? Just a personal opinion, most users should be very hesitant to quickly move to a new beta version, especially with significant changes in it, and data integrity at stake.
Archived
This topic is now archived and is closed to further replies.