Jump to content

Nitesh

Members
 View Profile  See their activity

  • Posts

    28

  • Joined

  • Last visited

 Content Type 

Posts posted by Nitesh

    emhttpd: error: hotplug_devices

    in General Support

    Posted

    4 hours ago, itimpi said:

    Looking at the diagnostics disk1 dropped offline (which resulted in write errors and thus it got disabled) and then reconnected with a different device Id which is why it then appeared under Unassigned Devices.  It is highly likely the drive is fine and it is an external factor that caused this (e.g sata or power cabling) as the SMART information for the drive looks fine.

     

    You also have an aggressive spindown timeout (15 minutes).   Thought it was worth mentioning this in case there are issues with spinning up the drive as the syslog contains regular occurrences of sequences of the form 

    Apr 18 05:52:33 MegaAtlantis kernel: mpt2sas_cm0: log_info(0x31120500): originator(PL), code(0x12), sub_code(0x0500)
Apr 18 05:52:33 MegaAtlantis kernel: sd 7:0:3:0: [sde] tag#2836 UNKNOWN(0x2003) Result: hostbyte=0x0b driverbyte=DRIVER_OK cmd_age=8s
Apr 18 05:52:33 MegaAtlantis kernel: sd 7:0:3:0: [sde] tag#2836 CDB: opcode=0x85 85 06 20 00 00 00 00 00 00 00 00 00 00 40 e5 00
Apr 18 05:52:33 MegaAtlantis  emhttpd: read SMART /dev/sde

    where the read SMART indicates that Unraid thinks the drive has just been spun up.

    Thanks for checking this for me.

    I shut down the server and checked each disk cable by unplugging and plugging back in and when I restarted. Got a message 0 Errors.
    But still there is a X next to the disk. Whats the best way to solve this one ? Screen shot attached.
    1719462806_ScreenShot2023-05-07at10_35_37pm.thumb.png.55474837da982a1fa610c75630745f55.png

    Also thanks for pointing out the aggressive spin down. I did that for a test and never reverted back.
    I have reverted it back to 1 hour. Hoping that 1 hour is not considered aggressive.

    emhttpd: error: hotplug_devices

    in General Support

    Posted

    Hi Guys,

    I had this error come up with one of my data drives (disk 1) and I am not sure if its drive failure or something to do with cables.

    Once the error came up for the drive in question. that drive showed up in unassigned devices for some reason. Never have I had a drive fail and it show up in unassigned devices.

    Attached are some of the screenshots and diagnostics attached.
    214077112_ScreenShot2023-05-07at2_17_27pm.thumb.png.13cb639d43fd3e58dfd9acea01375e27.png991173255_ScreenShot2023-05-07at2_17_47pm.thumb.png.0fbbdde4df4f41a3f04608ae10cfdc01.png
    I always have spare drives on hand so can swap it immediately if its a drive issue.

    Any help would be awesome!

    Cheers

    megaatlantis-diagnostics-20230507-1411.zip

    Replacing old parity drive with error and adding a second parity drive

    in General Support

    Posted

    1 minute ago, JorgeB said:

    Yep, some corruption is expected, unless by luck the failed blocks did not contain any data on the rebuilt disk.

     

    Disk is failing and needs to be replaced.

     

    Yep I knew that was happening. I just wanted to check two things

     

    1) Anyway to check what the corrupt data was. As I still have the old disk3 from which I am hoping to replace this from. That is if it is possible.

    2) that it would be safe for me to go ahead and rebuild the parity from scratch after the newly rebuilt disk3 had errors while rebuilding.

    Replacing old parity drive with error and adding a second parity drive

    in General Support

    Posted

    On 9/23/2020 at 9:50 PM, JorgeB said:

    Not if the disk is really failing, it can't correct any read errors, best to just do a standard rebuild.

    I didn't do a dd and thought to go straight for a standard rebuild as suggested.

    But I received 256 errors. These errors come from the Parity drive I believe.  I have never done a rebuild before. If anyone can shed a light if these 256 errors is considered huge in number and if there is anyway to check which data was corrupted?

     

    I still have the old Disk 3 from the list above which I unassigned and have not yet erased the data from.

     

    I have attached the recent diagnostics

     

    Any help would Be appreciated @JorgeB @trurl

    megaatlantis-diagnostics-20201022-2113.zip

    Replacing old parity drive with error and adding a second parity drive

    in General Support

    Posted

    Thanks for the recommendation @JorgeB & @trurl.

     

    The wiki link gave me an idea.

    What I might do is actually swap the Disk3 4TB with a new 4TB that I am getting as an advance replacement from WD for the Parity drive.

    Following https://wiki.unraid.net/Replacing_a_Data_Drive

    Is there a better way to just copy the data from disk 3 to the new disk 3 without having to rebuild from parity? Just so i don't strain other drives in the process.

     

     

    Once that is done I will proceed with the just removing the current parity drive and adding two new 8TB ones and rebuilding the parity.

     

    Do let me know if I am not going the right way :)

     

    Cheers

    Replacing old parity drive with error and adding a second parity drive

    in General Support

    Posted

    Hey Guys,

     

    Have been searching this for a while so wanted to know what is the best way of doing this.

     

    What I want to do is replace the Parity drive from one 4TB to two 8TB drives. Whats the best way to do this.

    I am expanding the parity now to 2x8TB so I can then replace the 4TB data drives to 8TB when and if they start failing at a later stage and this will give me an option to add larger drives later.

     

    Below is my current structure.

    Parity Drive - 4TB (Reported uncorrect 1)

    Disk 1 - 4TB

    Disk 2 - 4TB (UDMA CRC error count 1)

    Disk 3 - 4TB (Raw read error rate 125) So i suspect this is failing.

    Disk 4 - 2TB

    Disk 5 - 2TB

    Disk 6 - 4TB

    Disk 7 - 4TB

     

    Also confused about the Disk 2 and 3 errors as some forums suggest that it might just be a loose cable. 

    If I replace and expand the parity 1st and if the errors in Disk 2 and Disk 3 are serious. I worry I might loose that data.

     

    Attached is the diagnostics report in case anyone wants to look at it.

     

    Cheers

    megaatlantis-diagnostics-20200922-1958.zip

    Drive Read Error

    in General Support

    Posted

    19 hours ago, johnnie.black said:

    It looks like an actual disk error, but these can sometimes be intermittent, run an extended SMART test.

    Thanks for this. I ran extended SMART test and it came back with no errors. So hoping that is OK for now. 

    Issue with Cache & Krusader

    in General Support

    Posted

    1 hour ago, jonathanm said:

    Please list the docker mappings for krusader, and the relative paths you are moving from and to inside krusader.

    As soon as i was looking for the relative paths to post the screenshot here, i realised my mistake.

     

    I was moving from Root > Unraid > Cache > Downloads

    which should have been

    Root > Unraid > user > Downlaods.

     

    Hence it was actually using the disk share to transfer, rather than using the user share which triggers the cache functionality of the server. 

     

    My mistake. But thanks for making me look for the right thing :)

     

    Cheers,

     

×
×
  • Create New...