Brucey7
-
Posts
304 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Brucey7
-
-
Do a risk assessment for flooding, as a generalisation, computer kit in basements isn't always a good idea. Even the large corporates sometimes get that wrong.
-
Until I pull it out of it's cupboard, I can't see what the power supply is, but the system was built be greenleaf so it should be adequate.
It turned out Parity2 is faulty (WD 6TB Red), in warranty so going back, it's currently rebuidig Parity 2 onto a spare, should finish in an hour or so.
It's so long since I swapped cables, I can't remember what I did, so I'll go through the process again and try and rule out the cable and disk enclosure.
attached are the diagnostics. 99% of the time it performs flawessly, it usually only fails on a warm reboot when either 1 or 8 drives don't appear.
-
This system has always had the same error that appears as a bad SATA cable, even from when it was new, but it isn't a cable issue. It normally resets and runs just fine.
It completed the disk upgrade but failed on rebuilding Parity 2 onto the same disk, so it is just possible that Parity 2 disk is faulty, ii've put it in another server and i'm preclearing it now, so we'll see.
I would like to tie down this isue, I'm worried if it's a mobo issue I just can't face all the work in changing it.
-
One of my servers is temperamental. Sometimes the first 8 disks aren't recognised at reboot, a hard boot usually fixes the problem, sometimes I get what appears to be disk cabling issues, but I'm fairly sure the cables are ok, they've been swapped around and some replaced (the first 8 disks are on a separate controller card).
I'm upgrading a disk (disk1) to a larger one at the moment and Parity 2 just dropped out, there are the usual sporadic errors I see in the logfile, but now it's saying disk29 write error as it dropped out Parity 2. AFAIK, it shouldn't be writing to Parity 2 and in any event, I only have 17 data and 2 parity drives in this server
Does anyone have any idea what's wrong?
Many thanks in anticipation
Bruce
6.20 rc5, Dynamix cache directories, Dynamix webGui, nerd tools & PreClear disks, all latest versions
No SMART reports, but I'm sure the disks are ok
-
WinRAR has the ability to store a file in chunks of user defined size, with or without compression
-
Including 2 parity drives, I have 9 of these in one of my servers and the rest are 6TB's, I'm gradually replacing the 6TB's with these Shingled drives, they are a solid performer.
There's just one thing you shouldn't do with them, and that's two simultaneous writes, e.g. parity rebuild AND write new data, other than that, I love them. I should add, some of my media files are over 100GB each and no issues.
-
I've just started toggling Read-Only/Read-Write myself, it's just a bit tedious.
I wasn't in the least bit worried about ransomware (until someone mentioned it, ignorance was bliss).
-
I often thought how useful it would be to have a preclear on a Windows machine. One of my Windows systems has a cageless removeable 3.5" drive bay.
To preclear safely on an unRAID server, you shouldn't start the array. There are several disk errors that will hang your server necessitating a reboot.
-
You can always use the Krusader docker instead.
It seems to be, a huge number of requests for assistance are around docker, I don't really want to start learning that either.
I think my brain is already full.
I'm a firm believer in the KISS methodolgy.
-
Since you have to take manual action anyway, a separate button seems a much cleaner solution. Also if it is a separate button, you do not need to spin up the drives to change the access, and conversely one can still spin up the drives without changing the access. I think trying to combine such a function with the spin up/down buttons would just lead to confusion for most users.Because I write to my array once or twice a day only, the rest of the time I only read from it.
Ransomware would spin it up Read-Only, if I want to write to the array, I need it spun-up anyway, so it makes sense to include it on the spin up button.
Two spin-up buttons if the file system is locked, one for Spin-Up R/O and one for Spin-Up R/W. Reverting to R/O after spin-down.
I don't like the mc solution as it's too fiddly and too many extra steps.
-
Because I write to my array once or twice a day only, the rest of the time I only read from it.
Ransomware would spin it up Read-Only, if I want to write to the array, I need it spun-up anyway, so it makes sense to include it on the spin up button.
-
To avoid problems like ransomware, I would like to see an option on Global Share Settings to Lock the entire array Read-Only, until the Spin-Up all disks button is manually pressed and until such time as the disks spin-down at which time the entire array reverts to Read-Only again.
In other words, the array can only be Write Enabled by doing a manual spin-up, after it spins down again it's Read-Only. Auo spin-up's keep it Read-Only.
-
Another relatively easy way to provide resistance is to have another field on the "Global Share Settings" page (or per share) which says
"Lock File System Read-Only Y/N"
Then if locked, have another option appear with a drop down menu
"Temporarily Unlock File System for.......1/2/4/8/16/32/64/128 minutes"
If you use mover, it could unlock it temporarily
-
Reseated the cable, same problem.
Fitted new cable, same problem.
Used a spare SATA socket on the Mobo - problem fixed.
Disappointing on a fairly new SuperMicro X10
Too difficult to return it from Thailand for a warranty replacement
-
Thanks very much, I will replace the cable and try it again. I appreciate the help.
-
Well that's weird, becaue it's disk 1 that keeps failing
-
I am getting repeated problems with disk errors, I've orered some new cables but I'm not sure whether I need to order a new controller, can anyone advise please?
-
Thanks guys, that is what I was looking for
-
The question is..
When I insert a disk that unRAID thinks has failed, is there some way I can tell it to forget that it was used before, so it offers it as a new disk, instead of (incorrectly) saying it is faulty, and thus rebuild the data onto it?
-
I have 2 parity disks so I have already rebuilt one disk with a spare and the other is nearly finished with another spare - but there is nothing wrong with the 2 disks that e server won't let me reuse until this process is complete (I have no data loss).
I try to avoid doing NewConfig wherever possible.
-
For example, to make it think the disk is new and attempt to rebuild it?
I had some cabling issues (now fixed) that resulted in 2 drives being marked as "Faulty" drive disabled. unRAID will no longer allow me to use them in that server, but they are fine and just completing preclear in my second server.
-
I didn't know that, I set each disk to use default and they immediately spun down, thank you
-
Thanks, I will check the cables
I do have a problem in so far as this server's disks never automatically spin down, I assumed it was a problem with a mobo or controller as it's a fairly new server
-
any ideas what's wrong?
unRAID Tower 1 Status: Alert [TOWER1] - USB drive is not read-write
in General Support
Posted
Is my flash drive failing/failed? I got the following email
Event: USB flash drive failure
Subject: Alert [TOWER1] - USB drive is not read-write
Description: Store_n_Go_Drive (sda)
Importance: alert
Many thanks in anticipation
Bruce
tower1-diagnostics-20161031-0618.zip