Jump to content

jensrobot

Members
  • Posts

    34
  • Joined

  • Last visited

Posts posted by jensrobot

  1. 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?

  2. 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

  3. 1 hour ago, JorgeB said:

    One full disk write (not read) is usually enough to get rid of pending sectors, but they could or not comeback again soon.

    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

  4. 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

  5. On 3/22/2021 at 7:48 PM, JorgeB said:

    Depends if your board has one or not, you can find more info it with Google, for example:

    https://superuser.com/questions/1057446/how-do-i-boot-to-uefi-shell

    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

×
×
  • Create New...