jbuszkie
-
Posts
693 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by jbuszkie
-
-
Hello! I'm finally going to probably update to V6.x from V5. Along with that I want to maybe do some link aggregation.
I currently just have one network port built in. So I need to get a plugin card to get a second gig port.
What are folks using/recommending? My on board uses the r8168 driver. do I need to get another realtek? or can I get an intel?
Is teaming helpful if you have gig already? I also just got a nice switch that supports teaming.
Thanks,
Jim
-
out of stock!
-
jbuszkie, please consider upgrading to UnRAID v6.
I'm too scared!!! Everything just (mostly) works right now! But....I've probably put it off too long now.
The upgrade guide is very thorough.. kudos to whomever wrote it.
*sigh* You're probably right, Rob. It's time to upgrade!
Thanks,
Jim
-
I'm using the unmenu method and I don't think it calls for the powerdown plugin... I'll have to double check unless someone knows off the top of their head..
Thanks again!
Jim
-
Is the the plg method? (installed in the plugins directory?) Should I abandon the unmenu method then?
and I have some version of apcupsd installed through unmenu.. is there anything special I have to do with that?
Thanks!
Jim
-
Ok.. please excuse my ignorance here.. I'm running a really old powerdown (1.02)!
I'd like to use the latest.. I'm still running V5. From unmenu it says there is a 2.06.. But the link, I think, is broken.
I found a 2.18 version, but don't remember how to manually install it! It's been a while since I've had to do any manual install.
I know V6 does things differently.. but I'm still on V5 with tgz file in the packages directory.
-
I'm trying to get dropbox working. It installed ok and the web gui says "Waiting to be linked to a dropbox account.."
I click the link and it opens a new page where I enter my info. When I click "Sign in" it responds with there was a problem completing your request.
Anyone run into this? (on V5)
Thanks,
Jim
Version Information
Dropbox Application v2.6.20
Dropbox CLI Script v2015.02.12
Plugin v2015.03.25
-
Where did this go?? I'm looking for a dropbox sync for unraid....
Edit: For Version 5 of unraid
Edit2: Nevermind.. found it here: http://lime-technology.com/forum/index.php?topic=39169.0
-
Does the resierFS have anything like that?I wonder if some of the files could be recoverable with a filesystem level scan for deleted files.
for the windows machine, I looked in the recycle bin and there was nothing.
-
Agree this is a scary issue. It's the first time I can recall that somebody had a virus like this propagate to the UnRAID server from the infected PC. I'm convinced it's because of the mapped drive -- so that's the first thing I'd eliminate.
This should also be a wake-up call for anyone who doesn't have a robust backup strategy !!
It wasn't just the mapped drives.. it was any drive it could see and write to on the LAN.
-
What do you mean use the URL?
What I have done is to make all the user shares world RO. And most of them export hidden. Then I have a user (me) setup for write access.
I'll make the two shares she uses (pictures and docs) open as in the past.. because these should be backed up offsite weekly.
So, at most, I'll lose a weeks worth.
I may even take me off the share I use for backups and create a new user with write privs that only acronis will keep. This way if, for some reason, I forget to logout or I somehow manage to get something similar, I should be protected. luckily the acronis backups were not targeted.
I also did lose about 5 months of stuff that I thought was being backed up. but it wasn't. It turns out the network drives on my windows PC that has the offsite backup wasn't backing them up because they weren't connected unless I touch them. I wasn't using that computer much anymore and wasn't accessing the shares on it. The regular drive was being backed up and I would get the e-mail saying stuff backed up successfully... but it didn't complain that it couldn't see the network drives that I told it to back up! grrr...
Now I'm going to see it I can get idrive working on the unraid box.. I'll have to investigate that!.
-
That website doesn't work any longer.. bummer..
CryptoLocker, unfortunately, has inspired criminals all over the world. We have seen more than 20 copycat ransomware attacks since the original CryptoLocker, some of which use the same name, modus operandi and layout as the original CryptoLocker. We believe that our Decryptolocker site has served its purpose, and we have decommissioned it given that the threat landscape has evolved. -
These encryption malware are better known as ransomware.
Your misfortune points out the importance of making sure that everything we store that is important to us (financials, work docs, photo and music collections, family videos, etc) MUST also be backed up to a normally inaccessible location, at least inaccessible to modification. Options include -
* Removable drives, only attached for the periodic backup
* Encrypted volumes, only accessible while open
* Read only remote storage, not a local read only flag(!), but truly read only by the current logged in user
* CD's, DVD's, etc, basically the same as removable drives, but also essentially read only
* Storage in multiple locations, one of which is only available by controlled access, briefly
* probably other methods too, that maintain an additional copy of everything that's important to us, but are inaccessible to modification by their nature or without something secret (reasonably unbreakable)
This is also a reason why inexpert users should be set up with only limited user rights, not administrator rights. This has been shown to limit the damage at times. And of course, keep anti-malware tools updated.
One more thing.. Don't marry a non tech savvy woman!! grrr...
I am vary fortunate that my pictures and docs will all be recoverable. But I am defiantly going to change the access to the shared drives to privileges and passwords. No more "no password" admin accounts on the windows machines.
The wife and kids will have guest accounts with limited privs!
-
I'd heard about these things but never realised they were still doing the rounds. Didn't know it affected everything on your LAN..
Sorry for your troubles mate.
I never heard of this before! I should have just quarantined the computer when she did it! I figured Norton would take care of anything! Guess not! Now I need a new strategy for all the shared drives! Luckily all our pictures and main docs are stored offsite online.
It hit any drive it could find on the LAN... Not just the mounted ones! Also I was lucky it didn't target the acronis files or my MP3s and MP4s and TS files!
-
does unmenu or any of the packages use any .txt files for config?
-
All the files that were touched have an ".abc" extension. and the modification date changed.
-
Hey! The wife clicked on a "Fed Ex" e-mail attachment! It apparently launched a encryption virus.
It got pretty much everything on my unraid machine that was doc or pdf or zip or jpg and several others..
It also hit the flash drive as well..
My concern is more about the flash drive. It got all the txt files and zip and jpg/png files. Now most are just old log which I don't care about..
but I do care about any unraid config and unmenu config or package config.
I'm trying to remember how it all worked. Does unraid create a ramdisk copy of the flash drive stuff?
Unmenu is mostly working (the pics/icons are gone) but I can still see all my usage notes and purchase dates and stuff.
Where are those stored? Is there anything I have to worry about before restarting unraid? Right now it's been
running since the wife opened the virus. I haven't restarted it yet.
Is there anything I want/need to do before I would do a restart?
bzimage,bzroot,ldlinux.sys *.cfg do not appear to have been touched.
Time to make inside my house more secure! I'm still deciding if I'm going to let the wife live or not!
Thanks,
Jim
-
That's what I figured... I assume there's enough ammunition to merit a RMA?
Sigh! looks like my other drive will have to be a parity drive for a couple weeks! grr...
Thanks for the input.
Jim
-
There were more errors like that..
Here are the results of the preclear..
========================================================================1.15 == ST4000VN000-1H4168 Z3013V86 == Disk /dev/sda has been successfully precleared == with a starting sector of 1 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 112 6 ok 161315704 Spin_Retry_Count = 100 100 97 near_thresh 0 Unknown_Attribute = 100 100 99 near_thresh 0 Reported_Uncorrect = 18 69 0 near_thresh 82 High_Fly_Writes = 1 1 0 near_thresh 129 Airflow_Temperature_Cel = 74 78 45 ok 26 Temperature_Celsius = 26 22 0 ok 26 No SMART attributes are FAILING_NOW 64 sectors were pending re-allocation before the start of the preclear. 56 sectors were pending re-allocation after pre-read in cycle 1 of 1. 48 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 32 sectors are pending re-allocation at the end of the preclear, a change of -32 in the number of sectors pending re-allocation. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change.
1/2 cleared themselves out.
Attached is the full preclear report with the smart results.
I wish it was cut and dry.. none of the pending got reallocated. Should I try to RMA the drive anyway? should I run another preclear?
-
I'm getting errors on the old parity drive...
Apr 30 09:06:12 Tower kernel: ata1.00: error: { UNC } (Errors)
Apr 30 09:06:12 Tower kernel: ata1.00: configured for UDMA/133 (Drive related)
Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] Unhandled sense code (Drive related)
Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] (Drive related)
Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] (Drive related)
Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] (Drive related)
Apr 30 09:06:12 Tower kernel: sd 1:0:0:0: [sda] CDB: (Drive related)
Apr 30 09:06:12 Tower kernel: end_request: I/O error, dev sda, sector 2551149104 (Errors)
Apr 30 09:06:12 Tower kernel: Buffer I/O error on device sda, logical block 318893638 (Errors)
Apr 30 09:06:12 Tower kernel: ata1: EH complete (Drive related)
Apr 30 09:23:08 Tower kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 (Errors)
Apr 30 09:23:08 Tower kernel: ata1.00: irq_stat 0x40000001 (Drive related)
Apr 30 09:23:08 Tower kernel: ata1.00: failed command: READ DMA EXT (Minor Issues)
Apr 30 09:23:08 Tower kernel: ata1.00: cmd 25/00:00:00:b8:1d/00:01:9f:00:00/e0 tag 0 dma 131072 in (Drive related)
Apr 30 09:23:08 Tower kernel: ata1.00: status: { DRDY ERR } (Drive related)
Apr 30 09:23:08 Tower kernel: ata1.00: error: { UNC } (Errors)
Apr 30 09:23:08 Tower kernel: ata1.00: configured for UDMA/133 (Drive related)
Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] Unhandled sense code (Drive related)
Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] (Drive related)
Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] (Drive related)
Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] (Drive related)
Apr 30 09:23:08 Tower kernel: sd 1:0:0:0: [sda] CDB: (Drive related)
Apr 30 09:23:08 Tower kernel: end_request: I/O error, dev sda, sector 2669525192 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690649 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690650 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690651 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690652 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690653 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690654 (Errors)
Apr 30 09:23:08 Tower kernel: Buffer I/O error on device sda, logical block 333690655 (Errors)
Apr 30 09:23:08 Tower kernel: ata1: EH complete (Drive related)
It's in the post read part of the preclear.. Maybe by this evening it will be done. but probably tomorrow morning.
-
I killed the parity check before it finished. I'm about to preclear the drive and will report back it's status..
Jim
-
Yeah.. makes sense.. But I'll probably wait till the rebuild finished before I start the preclear on the old parity drive.Since you are about to trash that parity info, I can't think of any reason to do a parity check. I'd stop it, replace the drive, and start the rebuild now, save some hours.
-
Yeah.. That's what I figured. Doing a parity check now. That will be done tomorrow. Then another 26ish hours for the rebuild.Just my opinion, but #3 is clearly the best. #1 is not an option, sorry. With those pending sectors, it probably cannot be used to rebuild any other drive that failed, so you don't really have full parity protection now. #3 restores your parity protection the quickest. Once finished, the pressure is off, and you can do whatever you want when you want. But yes, it means a delay in your intended use for the 4TB drive.
Then another 36ish hours for the pre-clear... Yeah.. It's gonna be a while!
Thanks for the opinion!
Jim
-
Just a caution before you throw out the drive too quick, pending sectors may or may not be bad. The numbers you showed do indicate the drive needs some repair work, but do not mean the drive is bad, until after testing it. Technically, 'pending' means 'pending full testing', which happens once you tell the drive you don't care about the current data stored there. You do that by writing to it, so that the drive now knows you are OK'ing overwriting the current data. It then can thoroughly test the sector to see how safely it saves test patterns, and if good, saves the data you requested to be saved there and unmarks it as pending. If it decides the sector cannot be trusted, then it is remapped to a good spare sector.
A sector is marked as a 'current pending sector' when it fails to be read correctly, even after applying the error correction info. That can happen either because of weak or damaged magnetic media under the sector, or because of electrical activity (spikes and outages while writing) that have scrambled too many bits in the sector. I tend to call the latter ones 'soft errors', because the physical sector is completely fine, and testing will prove that.
If you have had a power outage or sparking or other serious power issues, then the 64 sectors may just be soft errors, and the drive be perfectly fine, once tested and rebuilt.
So how many of you would risk running without parity for a couple days while I re-preclear the parity drive to check for more errors?
I have 3 options..
1. Do nothing and see if it clears itself out.
2. Take the parity out and run preclear on it. and run unprotected for like 36h (plus rebuild time if the disk checks out)
3. Take my new (green) 4T disk and let it rebuild parity on that. when that's done then run preclear on the old parity. If all good swap parity out again with the old disk or replace with the returned drive when it eventually arrives. This means my new drive (slated for something else) will have to not go into its new home for a week or so..
What would you guys do?
What Gigabit adapter to buy?
in General Support
Posted
The reason is I want to play with link aggregation (teaming/ bonding) whatever you want to call it. So the two NIC have to play nice together... Hence my question.