jonathanblim

I got a new drive, copied the files from the old flash to the new and did a hardboot but still no network connectivity and hence no GUI. Any help ?

It seems like the USB drive has failed ? Found this at the start of the errors... Nov 28 07:43:00 Candyshoppe kernel: usb 2-1: USB disconnect, device number 2 Nov 28 07:43:00 Candyshoppe kernel: blk_update_request: I/O error, dev sda, sector 1344480 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Nov 28 07:43:00 Candyshoppe kernel: blk_update_request: I/O error, dev sda, sector 2049 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Nov 28 07:43:00 Candyshoppe kernel: Buffer I/O error on dev sda1, logical block 1, lost async page write Nov 28 07:43:00 Candyshoppe kernel: blk_update_request: I/O error, dev sda, sector 560656 op 0x1:(WRITE) flags 0x0 phys_seg 1 prio class 0 Nov 28 07:43:00 Candyshoppe kernel: Buffer I/O error on dev sda1, logical block 558608, lost async page write Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30768) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30769) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30770) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30771) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30772) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30773) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30774) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30775) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30776) failed Nov 28 07:43:01 Candyshoppe kernel: FAT-fs (sda1): Directory bread(block 30777) failed Recommendations on how to proceed ? I have lost webgui now

OK so even with the sleep disabled the problem still presists candyshoppe-syslog-20211129-0105.zip

While this is not optimal I will try disabling S3 sleep all together to see if it makes any difference. thanks!

OK for some reason it seems the only way to get it uploaded is to zip the file. Attached is the log file, thanks in advance! syslog.7z

So apparently I already had the mirror to flash option enabled, but when I try to upload the log file I get following error now ?

Hello Squid, thanks for the feedback I will enable to mirror to flash function and post the sys log as soon as it happens again. that said I just encountered another issue. this has only been a few hours since I did the hard reboot this morning, but just now when I checked I now get the following error as if I do not have a license but I do ? Could it be my flash drive got killed during the power outage ?

Hello I am running Unraid 6.9.2 Plus and have 6 drives installed, 4 connected directly to the motherboard and 2 connected to a SAS to SATA card. A while back I had an unfortunate power outage when I wasn't home and box was not connected to a UPS. I mention this as this is the only odd event I recall happening, rest of the time everything was smooth with Unraid. Now randomly (sometimes in as little as a day upto 10 days) the server will become unresponsive, I am unable to do a normal shutdown/reboot or take the array offline, the only way is to force a reboot but powering down the machine by holding down the power button. When I look at my dashboard I notice that several cores/threads are stuck at 100% Thanks, Jon

No CPU in mind so open to suggestions. It will be 90% just as a media server to feed Kodi running on my Shield TV.

Hello, I have a Lian-Li PC-Q26 case which I'm trying to build a new unraid setup. This thing can take up to 10 drives but only a mitx board. I don't mind added in expansion card to increase the number of supported SATA drives. I would however prefer to stay away from ASROCK boards as I've had compatibility issues with them and RAM choices in the past. Could anyone please recommend a motherboard or share your setup. thanks

let me confirm. So I can go ahead, replace the motherboard, cpu, ram, etc... but plug in the existing hdds and usb flash. get the system running, then do a separate upgrade to unraid 6, new usb stick, new license and extra hdds. Do I have this right? The new motherboard I intend to purchase is the Asrock E3C224D4I-14S with theLSI 2308 SAS controller. My current setup is unraid 5.x would I need to add any extra files to the existing usb key to have it recognize the SAS controller since I'm only using SATA2 right now?

Hello, I am not 100% certain where to post this since the questions span between Unraid 5 & 6 and also hardware. Not sure how it happened, but safe to say something on my motherboard went having to do with memory. So I am going to take this opportunity to upgrade the system. As apart of the hardware upgrade I will be switching USB Sticks and upgrading from my plus to a pro license. Also I read that unraid 6 has a new filesystem and I would like to take advantage of that. Since I cannot get the current system online, how can I transfer the data to the new system? Can I pull each drive out and pop it into a external HD dock or case and transfer the data over to the new system? Please let me know if i can provide more information, I'm a little confused and overwhelmed at the moment, not liking the idea that I might lose 12TB of data. Don't know if this is relevant, but in case I posted what happened below. Background Several weeks ago, I noticed that my video would be pixelated randomly. I doubled checked different versions when I could and they were fine. Thinking maybe the file was messed up somehow during the transfer I didn't think much of it. A few days later the system locked up. Had to power button shutdown and reboot. It started doing the parity check, left it to run, the system locked again. I am not sure when exactly, and only realized it was locked when both the GUI and attempts at telnet login failed. I rebooted again, and this time noticed that it wouldn't even show up on my router. So booted into the BIOS made sure everything was OK, was fine. Then rebooted and ran a mem test. Sat through about 10 mins of screens of errors before calling it quits. Pulled memory out, replaced with only a single stick of memory (had two in originally, tried two sticks) and tested both slots, but now boot loop. I basically get to the BIOS screen then blinking cursor and then start over. Now this took place over the course of several weeks as I didn't have time to go troubleshoot the problem.

I'm on RC16 and have a similar situation and would like to give this a try, what are the steps to downgrading? Also running simple features, will the downgrade process cause any problems? thanks.

Thanks again Pauven. Testing out the new version 2.0 now. The countdown timer in v2 looks slicker than the progression number of version 1. Now I know how long before I need to look at the terminal for the next value to appear

Thanks for the info Pauven, makes sense that the numbers would be mostly affected by major hardware changes. What what what?? Down from 1.5x Parity time to only 2.1 hours? For me parity is about 8 hours so with version 2 I'd save about 10 hours... Any loss in samples taken or just a much more efficient routine?