crazynight
-
Posts
15 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by crazynight
-
-
well the backup finally finished after several days, and the upgrade to v6.1.6 took a whole 5 minutes just running a parity check but all is looking good.
-
Unraid V5.0-rc8a (Source server)
HP Microserver - AMD Turion II Neo N40L Dual-Core Processor
8GB Ram
Using the onboard SATA bays
WDC_WD30EFRX - 3TB - Parity
WDC_WD20EARX - 2TB - Data 1
WDC_WD20EZRX - 2TB - Data 3
WDC_WD30EFRX - 3TB - Data 3
Unraid 6.1.6 (Destination)
A8N-SLI Premium
AMD Athlon 64 X2 Dual Core 3800+ @ 2000
2gb Ram
Using the onboard SATA ports.
Hitachi_HDS721010CLA332 - 1TB - Data 1
Hitachi_HDT721010SLA360 - 1TB - Data 2
Hitachi_HDT721010SLA360 - 1TB - Data 3
Hitachi_HDT721010SLA360 - 1TB - Data 4
Parity or Cache
-
I am currently backing up my V5 Beta to a fresh V6 build and am getting around 35Mb/sec transfer rate via rsync does this sound about right? No cache or parity on the V6 I plan to copy everything then introduce a parity.
Both servers are connected via 1gig to a dedicated 1gig switch.
Thanks
-
will let the backup finish and give it ago will probably be boxing day now several TB to backup.
-
J
Do you use any addons like unMenu or any plugins?
Just unmenu, am thinking a clean install reformatting the hard drives would be the best way forward start from scratch as it where.
-
Have been using unraid since 2012, my original box hp micro server still runs 5.0-rc8a never had a problem other than blowing a drive, which was simply replaced and rebuilt from the parity.
Is it time to upgrade? is it worth upgrading is V6 very stable?
I have thrown together a temporary second server to act as a backup (pic attached) while I carry out the upgrade but starting to second guess myself "If its not broken don't fix it" should I just leave my 5.0-rc8a alone?
should the 3 year old hp server be replaced? (no offers yet but am sure something will pop up in 2016)
-
I purchased a 5 twin pack Licence back in 2012 I am now looking to build a new system and upgrade to to v6 is it possible to upgrade my licences from v5 to v6? or will I have to purchase v6 a fresh?
Your licenses will still be valid...
Happy happy happy thanks
-
I purchased a 5 twin pack Licence back in 2012 I am now looking to build a new system and upgrade to to v6 is it possible to upgrade my licences from v5 to v6? or will I have to purchase v6 a fresh?
-
I am running 5.0-rc8a, not had any problems, is there any pressing need for me to upgrade to the latest stable version I have near 5tb of data and don't want to loose it all.
the upgrade steps seem straight forward...what could go wrong.
All previous 5.0-beta and 5.0-rc versions including 5.0-rc8a
Prepare the flash: either shutdown your server and plug the flash into your PC or Stop the array and perform the following actions referencing the flash share on your network:
Copy the files bzimage and bzroot from the zip file to the root of your flash device, overwriting the same-named files already there.
Reboot your server. Once boot-up has completed, you should see "Stopped. Configuration valid." array status with all disks assigned correctly.
Click on each disk link on the Main page and examine the Partition format field. If you see "MBR: error", or "MBR: unknown" for any disk, do not Start the array; instead post your finding in the Forum announcement thread for this release. If everything looks ok, click Start to bring the array on-line.
Go to Utils/New Permissions and execute that utility to change file ownership and permission settings. This is necessary for proper operation of the 5.0 security model.
-
as its just 2 months old will download their testing tool and test the drive and do a return. off shopping for a replacement to get the array back up and running and fully protected again.
-
forgot to say the drive is making a buzz....clicking sound from time to time
-
could someone take a look at this report and give me some idea of whats going on the drive has failed but not sure why can I just format it and put it back or do I need to send it back?
smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build)
Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: ST1500DL003-9VT16L
Serial Number: (removed)
Firmware Version: CC98
User Capacity: 1,500,301,910,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 8
ATA Standard is: ATA-8-ACS revision 4
Local Time is: Fri Jan 18 20:14:45 2013 Local time zone must be set--see zic m
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED
General SMART Values:
Offline data collection status: (0x82) Offline data collection activity
was completed without error.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: ( 612) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 1) minutes.
Extended self-test routine
recommended polling time: ( 254) minutes.
Conveyance self-test routine
recommended polling time: ( 2) minutes.
SCT capabilities: (0x1033) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.
SMART Attributes Data Structure revision number: 10
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x000f 113 099 006 Pre-fail Always - 52128656
3 Spin_Up_Time 0x0003 093 092 000 Pre-fail Always - 0
4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 525
5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
7 Seek_Error_Rate 0x000f 068 060 030 Pre-fail Always - 7015628
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 869
10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0
12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 22
183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0
184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
187 Reported_Uncorrect 0x0032 071 071 000 Old_age Always - 29
188 Command_Timeout 0x0032 100 099 000 Old_age Always - 4295032833
189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
190 Airflow_Temperature_Cel 0x0022 074 068 045 Old_age Always - 26 (Min/Max 23/26)
191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0
192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 9
193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 546
194 Temperature_Celsius 0x0022 026 040 000 Old_age Always - 26 (0 21 0 0)
195 Hardware_ECC_Recovered 0x001a 035 019 000 Old_age Always - 52128656
197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 109878148333943
241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 1191269549
242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 2479323320
SMART Error Log Version: 1
ATA Error Count: 29 (device log contains only the most recent five errors)
CR = Command Register [HEX]
FR = Features Register [HEX]
SC = Sector Count Register [HEX]
SN = Sector Number Register [HEX]
CL = Cylinder Low Register [HEX]
CH = Cylinder High Register [HEX]
DH = Device/Head Register [HEX]
DC = Device Command Register [HEX]
ER = Error register [HEX]
ST = Status register [HEX]
Powered_Up_Time is measured from power on, and printed as
DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 29 occurred at disk power-on lifetime: 188 hours (7 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+06:08:34.694 READ DMA EXT
27 00 00 00 00 00 e0 00 5d+06:08:34.693 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 5d+06:08:34.693 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 5d+06:08:34.692 SET FEATURES [set transfer mode]
27 00 00 00 00 00 e0 00 5d+06:08:34.662 READ NATIVE MAX ADDRESS EXT
Error 28 occurred at disk power-on lifetime: 188 hours (7 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+06:08:31.330 READ DMA EXT
27 00 00 00 00 00 e0 00 5d+06:08:31.329 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 5d+06:08:31.329 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 5d+06:08:31.298 SET FEATURES [set transfer mode]
27 00 00 00 00 00 e0 00 5d+06:08:31.201 READ NATIVE MAX ADDRESS EXT
Error 27 occurred at disk power-on lifetime: 188 hours (7 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+06:08:27.957 READ DMA EXT
27 00 00 00 00 00 e0 00 5d+06:08:27.956 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 5d+06:08:27.955 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 5d+06:08:27.955 SET FEATURES [set transfer mode]
27 00 00 00 00 00 e0 00 5d+06:08:27.925 READ NATIVE MAX ADDRESS EXT
Error 26 occurred at disk power-on lifetime: 188 hours (7 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+06:08:24.583 READ DMA EXT
27 00 00 00 00 00 e0 00 5d+06:08:24.582 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 5d+06:08:24.582 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 5d+06:08:24.581 SET FEATURES [set transfer mode]
27 00 00 00 00 00 e0 00 5d+06:08:24.550 READ NATIVE MAX ADDRESS EXT
Error 25 occurred at disk power-on lifetime: 188 hours (7 days + 20 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
25 00 00 ff ff ff ef 00 5d+06:08:21.219 READ DMA EXT
27 00 00 00 00 00 e0 00 5d+06:08:21.219 READ NATIVE MAX ADDRESS EXT
ec 00 00 00 00 00 a0 00 5d+06:08:21.218 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 00 5d+06:08:21.218 SET FEATURES [set transfer mode]
27 00 00 00 00 00 e0 00 5d+06:08:21.187 READ NATIVE MAX ADDRESS EXT
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.
-
Thanks neilt0, I will re-read your thread. I like your cache drive location might just have a spare 2.5" drive knocking about it will mean buying a lic...which is stating to seem inevitable.
-
I have been trying to sort my storage problems out for a while and the issue was pushed as a result of a portable drive failing and a friend recommended unraid. After a week of playing and getting my head around everything I am at the point where I am ready to start the build:
I have a HPN40L server which out the box can hold 4 drives and 6 with a little work and the following drives
3 x Seagate ST3400620AS 400GB (I known their history but used)
1 x Seagate ST2000DM001 2TB (brand new)
1 x WD WD20EARX 2TB (brand new)
1 x Seagate ST1500DL003 1.5TV (brand new)
1 X WD WDC_WD10EFRX 1TB (brand new)
1 x Seagate st320318as 250gb (brand new came with server)
My storage needs are not huge at the moment so was thinking of just starting out with the free version, using 2 x 2tb (1 as parity) and the 1.5tb giving me 3.5tb of storage.
I have several questions:
1. Is there anything special I should know about any of these types of drives?
2. Has anyone had any experience of the HP N40L's with unraid it seems really stable.
3. Would there be any advantage in building the array larger right from the start? rather than expanding it later? (I know I would need to buy a lic)
4. I know v5 is a RC version but is is stable enough to go live with or should I stick with 4.7?
Thanks in advance
UDP Broadcasts to a docker
in General Support
Posted
I have setup node-red as a docker and all with working good apart from the UDP packets I am trying to capture are not visible. The same flow works perfectly on a RPI running Node-Red so it looks like for what ever reason the UPD broadcasts are not getting forwarded to the docker, is there anything special I have to do to enable this? I did try adding the port 22600 but still no luck. I do know the broadcasts are always to 224.192.32.19 & port 22600.
Any help would be appriciated.