chrishorton7

Ok managed to solve it. For some reason it didnt like my SSD being plugged into the sata add on card. Moved it to sata port on the motherboard and now booting ok. Thanks for the speedy help SiNtEnEl

Ok so memtest completed all fine. I tried a quick boot before I start unplugging the drives and it seemed to get a little further before hanging. I now see the following message: Tower login: md: unRAID driver 2.9.3 installed mdcmd (1): import 0 md: import_slot: 0 missing Not sure if that gives any more clues before I start unplugging the drives individually?

Just a thought, I noticed that while running the memtest that my server 'tower' isn't showing in my attached devices list for my router. At what point would it connect? Only once the OS is fully loaded?

Ok running memtest now. When you say disconnected new drives. I assume you mean just the new data drive and SSD drive rather than all of them? Or should I try it with no drives connected to see if I can at least get the OS to boot?

Happy to run a memtest though, how long does it take to run?

Should have added when I swapped the memory out I started Unraid fine to confirm all was ok and it was. I then shut down to change and add the drive

Hi, I have been using Unraid for a few years now and everything has been fine. Today I did some upgrades to my server: Upgrade RAM Swapped a data drive for a larger one Added a SSD which I intend to use as cache drive Did all the hardware and then booted. Everything seemed as usual and it got to the blue Unraid OS screen. It then seems to load as normal but seems to be stuck. The last message is: tower login: md: unraid driver 2.9.3 installed It seems to be hanging from there. Have left for a while and no movement. Any ideas?

Thanks both, I don't have a PC with SATA cable to do the WD diagnostics unfortunately. I have just downloaded a SMART report from the Unraid 'Main' section which is attached. I'm popping out now, but later on will shut down and restart and get full diagnostics then to post. tower-smart-20170129-0928.zip

Hi, A couple of weeks ago I had a drive suddenly show red ball against. I bought a new drive to replace, but when I run the new drive through pre-clear I am getting the following error: unRAID's signature on the MBR failed The drive then dissapears as an option to pre-clear, although still shows on the main screen under unassigned disks. I thought it might have been the SATA cable so replaced this but I'm still getting the same issue. Logs are attached. Any advice on things i can try, I don't think its anything to do with the disk itself. tower-diagnostics-20170128-2003.zip

I've attached the latest diagnostics following the drop off, if anyone could take a look and see if they could spot anything else other than it losing connection tower-diagnostics-20170108-2237.zip

Ok, so had a look and couldnt see anything obviously loose. Restarted and found the disk fine and started pre-clear, after a couple of hours though it has aborted and the disk is no longer showing in the unassigned disks list. I'm going to order a new Sata cable and see if that resolves

Thanks Trurl, I thought that earlier and checked and couldnt see anything obvious loose. I will open up and double check again. Anything else it could be or anything else I could try?

Hi, A couple of days ago a disk in my server showed a red cross. I bought a new disk which I have added. When I go to pre-clear the disk though it started running for an hour or so and then showed the error 'UnRAID's signature on the MBR failed - Aborted'. The new disk is still showing in the unassigned devices list, but when I go to the preclear tool it says no unassigned disks available? Any help appreciated. I attached the diagnostics that I took yesterday (I had to do a reboot to run the pre-clear). tower-diagnostics-20170107-2110.zip

I viewed the disk as you said and was able to see all files and everything looked fine. I rebuilt it but now the drive shows with a red ball next to it. I have run a SMART test on the drive (attached) which seems to say no errors and that it passed, but I may be reading it incorrectly. Any advice on next steps welcome smart.txt

Thanks for the advice, I have rebooted and can now select the drive from the dropdown to assign it. When I do it shows a blue ball next to it and says when I start the array it will start a data rebuild - is this safe? Will it remove any data that existed on that drive?

Hi all, This morning I noticed that sabnzbd failed to copy a download over. When I logged into my unraid server one of my drive (drive 3) had a red ball next to it. I stopped the array and restarted it and drive 3 now shows as not installed. I've attached my syslog - what are the best next steps? syslog.zip

@RobJ - long delay over Christmas but finally got time to run the badblocks through - it has completed all the passes and found 0 bad blocks. I tried adding the drive back to the array as the cache drive and it still shows unformatted but with a green ball. I have now run the format on the drive and it appears to be ok now, will let you know if I get any more issues - thanks for all your help

I'm looking at setting up SabNZB, CouchPotato, Sickbeard and Plex using the Phaze plugins. Currently on my unraid I don't have a cache drive but I will be adding one in the next couple of weeks. If I set up all the plugins for their configs/settings etc to be on the array can I easily change these directories to the cache drive at a later date? Will this retain all my settings?

@RobJ - thanks for looking at that. The badblocks was going fine (first 2 passes complete no errors - unless it specifies them at the end - the 3rd pass was nearly complete but I stupidly tried to copy the text from the putty client and it stopped the process! :-( I'm rerunning it now and will let you know how it goes

@RobJ - I am running the badblocks as discussed but I found the attached preclear report files on the flash drive - I didn't realise it created these on the flash drive - I'm hoping these might help you figure out why it said the preclear was unsuccessful preclear_finish__WD-WCASJ1297981_2014-12-21.txt preclear_rpt__WD-WCASJ1297981_2014-12-21.txt preclear_start__WD-WCASJ1297981_2014-12-21.txt

Great thanks, running it now and will let you know once it finishes

Thanks RobJ - will do, a couple of questions: 1 - Will I be able to use the array when the badblocks is running? 2- Should I run this in Screen so I can use the array? 3 - When you say it takes a very long time what are we talking? The preclear took approx 25 hours

Ok managed to get AHCI working now - as @RobJ said my BIOS was trying to be helpful and resetting the boot device. About the syslog - I didn't realise it reset on reboot. I assume there's no way of getting the logs from when I did the preclear over the last 24 hours or so? All I have is the report text file which I posted earlier. I copied this information from telnet when the preclear had completed. For the preclear I followed the instructions on the configuration tutorial and cleared using screen and the following command: ./preclear_disk.sh -A /dev/hdd I've precleared drives before doing exactly that so I'm pretty sure I have done that right. What would you recommend next? I can run preclear again on the drive, but as it will take over 24 hours to run again, I'd rather go down other routes if they are available now I've switched to AHCI

@trurl - I will double check but the only setting I changed was the sata configuration to AHCI rather than IDE - nothing about the boot device. As soon as I changed it back to IDE it booted fine without any other changes

@Rob Syslog attached. When I switched it to AHCI and it tried to boot it just remaining on a black terminal screen and never loaded anything, the cursor was refreshing so hasn't crashed. I left it for 20 mins or so but nothing happened. I then turned the machine off and switched it back to IDE and it loaded fine to the unraid boot screen first time. syslog-21-12-14.zip