October 26, 20169 yr Hi As per the above subject header, I'm currently running 6.2.1 but I'm at my wits end. The array is not booting and I can't access the GUI (please see appended photo taken of screen). It was working up until recently. I rebooted because the cache drive was showing as unmountable and it wouldn't work when trying to format. http://i3.photobucket.com/albums/y78/dvdzuk/439CC502-AD0F-4E82-816D-BA206607A529_zpsjemlzgfg.jpg Hopefully someone can help? My setup is: Build Hardware CPU: Intel® Xeon® Processor E3-1241v3 (8M Cache, 3.50 GHz) Motherboard: Supermicro X10SL7-F Memory: 2 x Crucial 16GB Kit (8GBx2) DDR3/DDR3L-1600MT/s (PC3-12800) DR x8 ECC UDIMM Server Memory CT2KIT102472BD160B/CT2CP102472BD160B PSU: Corsair HX850i 80 Plus Platinum 850W Power Supply Case: Fractal Design Define R5 Mid Tower Black Cables: 16 x SATA III 90degree Down Angle Cable 26AWG 50cm - Black(2), Red(4), Light Blue(2), Blue(8 ) Thanks in advance
October 29, 20169 yr First thing I would try is: - power off unraid - remove flash drive - plug flash drive into PC - right click flash drive, select properties, tools, error checking, check - eject USB flash drive - remove flash drive from PC and insert back in unraid system - power on unraid system
October 29, 20169 yr And after that, pull the cache drive from the system and see if it makes any difference. If it does, then on the flash drive, edit the file config/disk.cfg and change startArray from "yes" to "no"
October 30, 20169 yr Author Thanks for the input guys, I'll have a go when i get five miuntes next week
November 1, 20169 yr First thing I do when I don't get the webgui is plug in a monitor and keyboard into the server and see what happens at boot. E.g. is it going into bios, failing to load the usb, trying to boot unraid but failing somewhere, etc. I diagnosed bad RAM this way for example, it would partially boot unraid then crash every time before loading the webgui, so I loaded memtest and found the bad RAM. Lots of reasons, sometimes a monitor helps.
November 2, 20169 yr Author Resolved, it was a faulty sata cable to the sdd. thanks for your help guys!!
Archived
This topic is now archived and is closed to further replies.