Orange triangle next to appdata folder under shares


Recommended Posts

  • 2 years later...

Hello .. Sorry to ask here but i could not find a better Place to ask.. 

\

I am new to UnRaid running 6.5.3-rc2  i have 1 Parity drive and 5 Drives i am seeing 

Orange triangle next to all folders under shares ( all Shares ) my Parity drive is good and running

I am running unRAID Server Plus.   i do not know how to fix this.. 

 

Thanks John

Link to comment
Hello .. Sorry to ask here but i could not find a better Place to ask.. 
\
I am new to UnRaid running 6.5.3-rc2  i have 1 Parity drive and 5 Drives i am seeing 
Orange triangle next to all folders under shares ( all Shares ) my Parity drive is good and running
I am running unRAID Server Plus.   i do not know how to fix this.. 
 
Thanks John
It means some of the files in that share are on your cache drive
Link to comment
  • 3 weeks later...

Hello ... Sorry Have played around with the server and still can not find WHY 

1)  Version 6.5.3 

2) I have no Cache

3) I have 1 of 8GB new RED (Parity drive)

                2 of 8GB new RED drives

                2 of 6GB one new one used 

                1 of 2 GB used (another 2GB to ADD)

I just 2 ( Check .....    Check will start Read-Check of all array disks.) 

and it found no errors take a look at the STATUS 

 

I know there is something wrong i just dont know now or what to fix. I have tryed Fix Common Problems and no errors there.. ANY Help 

 

Thanks John G.

**********************************************************************************1187702980_Screenshotfrom2018-07-1721-25-56.thumb.png.364abe8ae8b833b1cc1b8c9c3235f44c.png

Event: unRAID Status
Subject: Notice [TOWER] - array health report [PASS]
Description: Array has 6 disks (including parity)
Importance: normal

Parity - WDC_WD80EZAZ-11TDBA0_7SH1UHUD (sdd) - active 37 C [OK]
Disk 1 - WDC_WD80EZAZ-11TDBA0_1SH494VZ (sde) - active 37 C [OK]
Disk 2 - WDC_WD80EZAZ-11TDBA0_7SH21VND (sdf) - active 36 C [OK]
Disk 3 - WDC_WD60EZRX-00MVLB1_WD-WXL1H844U3D7 (sdg) - active 35 C [OK]
Disk 4 - WL6000GSA12872E_WOL240343358 (sdc) - active 36 C [OK]
Disk 5 - TOSHIBA_DT01ACA200_23HM2MZGS (sdb) - active 35 C [OK]

Parity is valid
Last checked on Fri 13 Jul 2018 09:14:43 AM EDT (4 days ago), finding 0 errors.
Duration: 1 day, 17 hours, 41 minutes, 58 seconds. Average speed: 53.3 MB/s

 

************************************************************************

unRAID Status: Notice [TOWER] - Read check finished (0 errors)
Inbox
x

[email protected]
Fri, Jul 13, 9:15 AM (4 days ago)
to me

Event: unRAID Read check
Subject: Notice [TOWER] - Read check finished (0 errors)
Description: Duration: 1 day, 17 hours, 41 minutes, 58 seconds. Average speed: 53.3 MB/s
Importance: normal

 

****************************************************************************

 

 

Link to comment

It's all because you have Disk 7 not installed, but the array is expecting that.  Since you only have a single parity drive, what this means is that should any drive decide to give up the biscuit, you will not be able to rebuild it at all.

 

Why is disk 7 not installed?

Link to comment

Ah, now it becomes clear. You at one point assigned a drive to Disk 7, and it has since failed or been removed. It is being emulated by the parity drive and the rest of your data drives, so you are unprotected from another drive failing, since you only have a single parity and a failed drive.

 

Unprotected shares = orange triangle.

Link to comment
On 7/17/2018 at 9:28 PM, John Graham said:

Event: unRAID Read check
Subject: Notice [TOWER] - Read check finished (0 errors)

I glossed over this at first, but now it makes sense. When a drive is in the failed state, trying to do a parity check won't work, because there is nothing to verify against, so instead unraid does a read check to see if the remaining drives give any read errors.

Link to comment
1 minute ago, John Graham said:

Thanks .. I See ... the drive went bad and i  pulled it out. Have not found a way to remove it from the list ... Guest i now need help with that

 

how to remove drive 7

 

John G,

 

Replace it with another drive, or move any data off of the emulated drive and rebuild parity with the remaining drives by setting a new config.

Link to comment
1 minute ago, John Graham said:

Thanks .. I See ... the drive went bad and i  pulled it out. Have not found a way to remove it from the list ... Guest i now need help with that

 

Since it appears that you emptied the drive before removing it, what you need to do is Tools - New Config.  Reassign all the drives (make a note of which one was your parity drive first), then when you start the array, it will rebuild the parity and you'll be back in business.

Link to comment
3 minutes ago, jonathanm said:

As long as you don't assign a data drive to a parity slot, it won't get erased. Just be very careful to note which serial number goes in each slot and you will be fine.

 

That is why i went with unraid ... so cool to get help this way ... thanks everyone ... 

John G

 

Edited by John Graham
Link to comment
7 hours ago, jonathanm said:

As long as you don't assign a data drive to a parity slot, it won't get erased.

 

With "New Config" you can choose to retain the parity disk assignment. This will keep the current parity disk assigned as is, while data disks can be newly assigned.

 

As mentioned before, new assignments of data disks will not cause data loss.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.