jensrobot

I actually never heard of this brand, and I only found 1 retailer that has this in stock where i live (Denmark). It will cost me a whoppin' 158$, and that's probably because its a uncommon brand over here. We sure It's single rail? some searching seems to confirm that it is, but that's from 3rd party sites. The vendors site does not seem to mention it.

So I just had my unraid server crash and reboot during a full parity sync after I removed a disk from array Recently I've been having other problems I think are related to power, so I'm not taking any more chances and I'm replacing the old Corsair VS350 i have now. This one was never specifically bought for this server, it was just something I already had when I build the server. I tried looking up PSU's on the wiki and forum but all seems around a decade old, so I'm hoping someone here can give me a more specific and not so dated recommendation... I have 7 drives + 1 SSD installed at the moment, but my plan is to max the disk capacity in the case to 12 HDD's + 1 SSD. It's a mix of 7200 and 5400 rpm disks. I attach diagnostics so my specs should be in there. skabet-diagnostics-20210915-2130.zip

Rebuild done with no errors yay I'll probably remove disk 7 next so i have a spare disk. I attach log in case you wanna have a look. I learned some new things, and i will have to troubleshoot the bigger issue carefully. Since pre-clear and smart went fine on icydock+sas controller, i have to be smart about it. The errors happened after i already transferred multiple terabytes without error. I'm thinking about getting a new PSU (to get out of adapter/splitter hell), add some disks to the icydock (but don't add to array) and start some large test file transfers. If i transfer from array directly to an unassigned disk, and if an error like previous occurs, it will break the transfer since i wont have an emulated drive taking over right? If you have any suggestions on how to proceed i'm all ears. You've been a great help so far, so thanks again. skabet-diagnostics-20210902-1923.zip

thank you. I have now started the rebuild process, and will report back when it's done

Here is the diag. i did 2 boots because the first time i didnt remove the sas card, but then it didnt register the sata card, so i removed sas completely and now i see disks skabet-diagnostics-20210901-2313.zip

Model:SSU-SATA3-T2 - Chipset: ASM1061 I used it in my old unraid system for years with no trouble

I really appreciate your help and time, and you explain it well i just think im way in over my head here and right now im honestly super confused. I have a 2 port sata controller i can use to connect disk 6 and 7. This way I avoid the sas controller and icydock variables. Do i rebuild disk 6 like stated here?: https://wiki.unraid.net/Manual/Storage_Management#Rebuilding_a_drive_onto_itself I dont have a spare 6TB disk, and in hindsight i should maybe have kept disk 7 as a spare disk instead of adding it to array right away

I transferred all contents of disk 6 of to another pc. It's not super important data, just video files that can be replaced. I checked some of the files and the play fine. I guess there might be a defective file(s) somewhere, or did the emulated drive take over when the error occurred? (i was doing the transfer between parity disks in mc when error occurred, and mc didnt give me error and seemed to complete the transfer). I do have backups of irreplaceable data on other machines Aah yes makes sense since I only have the one parity drive. Is it ill advised to only have 1 parity drive? I expanded quite a bit since i first got unraid, so maybe it would be smart to add a 2nd parity drive? So just to be clear, if i remove disk7 from here it will re-activate disk6 and try to rebuild parity? Wouldn't the files from disk6 be ok since emulated drive took over? and if file corruption took place, would it not only be the one file it was transferring when error occurred thats corrupted?

Currently transferring off the emulated disk. Will take quite a while, but after that I will feel more secure dealing with this. can you elaborate what you mean with "new config" i'm a bit confused. I'm guessing you mean i stop array, remove disk7 from dropdownlist and start array?

I cant find the model of the icydock im using but its very similar to this one (mine seems to be and older version - no model number anywhere on product): https://www.icydock.com/goods.php?id=48 This one is advertised as 3 molex connectors power 5 drives. Mine is also a 5 drive dock, but only have 2 molex which i connected power to (only 2 drives in my bay atm)

thx for the reply, and yeah i'm beginning to suspect the 2 new variables. I've had some trouble with the sas controller hanging at the pre-bios screen, but that seemed to "fix itself" with a reboot or just waiting a couple of minutes. My case is a mess as it is now, and i use a lot of splitters for sata power (molex for icydock) and what not. I'm not too confident with this... I'm also using a 350W PSU, and i think im pushing its limits but i dont rly know for sure. I still have a spare sata port on mobo. I'm thinking if isolating this issue by connecting disk 6 directly into that. Disk 7 was only added to array but doesnt have data on it, so ill remove that. Do i need to rebuild/repair the array? i mean the disabled disk needs to be reformatet and re-added or?

Was copying files inside my array and i got errors and now it's disabled. The disk was just added to the array. It's old but passed smart and the preclear operations. Smart is still not reporting anything wrong but drive is disabled and array is unprotected. Can someone advise me what to do? i attach logs Error started at Aug 31 03:43:05 "SKABET kernel: md: disk6 write error, sector=885344016" I have these disks attached to a LSI sas controller I flashed to IT mode. I haven't used this before. I'm also using an old Icydock for this disk which is also a new addition to the machine. Might be relevant? Havent had array failures before so this is new territory for me... skabet-diagnostics-20210901-0316.zip

2nd zeroing and post-read went ok. Still not really trusting this disk. Meanwhile the other "good" disk i got has had errors and is now disabled. I'll make a new thread for that

Thanks for your reply. I'm currently zeroing the drive again, and smart already reports the current pending sector count is back to normal. Now I will wait and see if the post-read goes through ok

Recently got 3 old 6TB WDC_WD60EFRX-68MYMN1 disks. One of them got trashed immediately because it had alot of different smart errors. I started preclearing the other 2, but before I did that I noticed one of them had a UDMA_CRC_Error_Count value of 1. I read from different places that this was probably not something super alarming. This disk now returns a Current_Pending_Sector value of 1 when i hit step 5 (post read), and it did the 4 steps before just fine. I've read that some people say this could be fixed by several pre-clear runs. Can anyone here give me some recommendations on what to do next? I should mention it's been used in another server of some kind, and its power on hours is 52389 (5y, 11m, 21d, 21h) I attach preclear log preclear_disk_WD-WX21D84R1UUY_22324.txt

I tried flashing in windows first but it just reset or BSOD the pc when i tried, so i've taken the dos route instead, but now im in the same boat as folic86 with the pal error. I have booted to efi shell via a usbkey with the EDK2 binary but now im lost. How do i execute sas2flash.exe from EFI shell, is that even possible? i can navigate folders fine and see the files but dont know how to proceed Hope you or someone can help me i never used EFI shell before

Thx for telling us, i was waiting patiently for the update ready icon

"Wednesday March 24th 2021 - qBittorrent v4.3.4 release qBittorrent v4.3.4 was released. WEBUI: It is accidentally broken in this release. A new release will be posted quickly. If you use the WebUI skip v4.3.4 for now." Luckily the torrents are still running, it's only the WEBUI