unRAID Server Release 6.0-beta12-x86_64 Available


limetech

Recommended Posts

  • Replies 504
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

First I rebooted the server. That actually seemed to clear it up until I started watching things on my plex docker. Then things started to go all wonky. So I've nailed it down to one of my btrfs cache drives failing.

 

ATA Error Count: 6 (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 6 occurred at disk power-on lifetime: 15035 hours (626 days + 11 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 a0 b0 62 00  Error: UNC at LBA = 0x0062b0a0 = 6467744

  Commands leading to the command that caused the error were:
  CR FR SC SN CL CH DH DC   Powered_Up_Time  Command/Feature_Name
  -- -- -- -- -- -- -- --  ----------------  --------------------
  c8 00 08 a0 b0 62 e0 00  44d+01:19:42.222  READ DMA
  25 00 00 20 95 64 e0 00  44d+01:19:42.216  READ DMA EXT
  25 00 00 20 91 64 e0 00  44d+01:19:42.210  READ DMA EXT
  c8 00 80 98 90 64 e0 00  44d+01:19:42.209  READ DMA
  25 00 00 08 63 64 e0 00  44d+01:19:42.141  READ DMA EXT

Error 5 occurred at disk power-on lifetime: 15035 hours (626 days + 11 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 a0 b0 62 00  Error: UNC at LBA = 0x0062b0a0 = 6467744

  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 68 ac 62 e0 00  44d+01:19:39.838  READ DMA EXT
  25 00 00 68 a8 62 e0 00  44d+01:19:39.814  READ DMA EXT
  25 00 20 ff ff ff ef 00  44d+01:19:39.803  READ DMA EXT
  25 00 00 68 a4 62 e0 00  44d+01:19:39.790  READ DMA EXT
  25 00 00 68 7c 62 e0 00  44d+01:19:39.731  READ DMA EXT

 

ID#	ATTRIBUTE NAME	FLAG	VALUE	WORST	THRESH	TYPE	UPDATED	FAILED	RAW VALUE
1	Raw Read Error Rate	0x000f	110	099	006	Pre-fail	Always	Never	176792433
3	Spin Up Time	0x0003	096	095	000	Pre-fail	Always	Never	0
4	Start Stop Count	0x0032	100	100	020	Old age	Always	Never	80
5	Reallocated Sector Ct	0x0033	089	089	036	Pre-fail	Always	Never	455
7	Seek Error Rate	0x000f	069	060	030	Pre-fail	Always	Never	167775926782
9	Power On Hours	0x0032	083	083	000	Old age	Always	Never	15035
10	Spin Retry Count	0x0013	100	100	097	Pre-fail	Always	Never	0
12	Power Cycle Count	0x0032	100	100	020	Old age	Always	Never	40
184	End-to-End Error	0x0032	100	100	099	Old age	Always	Never	0
187	Reported Uncorrect	0x0032	094	094	000	Old age	Always	Never	6
188	Command Timeout	0x0032	100	098	000	Old age	Always	Never	12885098502
189	High Fly Writes	0x003a	001	001	000	Old age	Always	Never	149
190	Airflow Temperature Cel	0x0022	070	052	045	Old age	Always	Never	30 (Min/Max 21/32)
194	Temperature Celsius	0x0022	030	048	000	Old age	Always	Never	30 (0 20 0 0 0)
195	Hardware ECC Recovered	0x001a	049	035	000	Old age	Always	Never	176792433
197	Current Pending Sector	0x0012	095	095	000	Old age	Always	Never	220
198	Offline Uncorrectable	0x0010	095	095	000	Old age	Offline	Never	220
199	UDMA CRC Error Count	0x003e	200	200	000	Old age	Always	Never	0

 

So I am in the process of offloading what I can from the cache drive and replacing it.

Link to comment

After shutting down unraid to upgrade a datastore on my esxi, the webgui no longer load properly.  The formatting is off and images missing. Does anyone have a solution?

 

Update: Problem solved by deleting all dynamix in the plugins folder. After restart, Dynamix was re-downloaded and web gui is back to normal.

Link to comment

I'm having a problem starting my array.  I just upgraded from 5 to 6b12.  It says "Stopped. Unclean shutdown detected." but even after clean restarts from the GUI it persists.  How can I troubleshoot this?

 

Dec 13 18:10:53 Tower emhttp: too many devices
Dec 13 18:10:53 Tower emhttp: shcmd (302): :>/etc/samba/smb-shares.conf
Dec 13 18:10:53 Tower emhttp: Restart SMB...
Dec 13 18:10:53 Tower avahi-daemon[1504]: Files changed, reloading.
Dec 13 18:10:53 Tower emhttp: shcmd (303): killall -HUP smbd
Dec 13 18:10:53 Tower emhttp: shcmd (304): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service
Dec 13 18:10:53 Tower avahi-daemon[1504]: Files changed, reloading.
Dec 13 18:10:53 Tower avahi-daemon[1504]: Service group file /services/smb.service changed, reloading.
Dec 13 18:10:53 Tower emhttp: shcmd (305): pidof rpc.mountd &> /dev/null
Dec 13 18:10:53 Tower emhttp: shcmd (306): /etc/rc.d/rc.atalk status
Dec 13 18:10:53 Tower emhttp: shcmd (308): rmmod md-mod |& logger
Dec 13 18:10:53 Tower kernel: md: unRAID driver removed
Dec 13 18:10:53 Tower emhttp: wrong GUID: /boot/config/Plus.key (0781-5571-2000-020807108110)
Dec 13 18:10:53 Tower emhttp: Unregistered
Dec 13 18:10:53 Tower emhttp: array slots: 24
Dec 13 18:10:53 Tower emhttp: cache slots: 1
Dec 13 18:10:53 Tower emhttp: shcmd (309): udevadm settle
Dec 13 18:10:53 Tower emhttp: shcmd (310): /sbin/btrfs device scan |& logger
Dec 13 18:10:53 Tower logger: Scanning for Btrfs filesystems
Dec 13 18:10:53 Tower emhttp: Device inventory:
Dec 13 18:10:53 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WMC4M1156591 (sdb) 1953514584
Dec 13 18:10:53 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WCC4M0055425 (sdc) 1953514584
Dec 13 18:10:53 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WCAZA8304971 (sdd) 1953514584
Dec 13 18:10:53 Tower emhttp: WDC_WD10EADS-00L5B1_WD-WCAU48538889 (sde) 976762584
Dec 13 18:10:53 Tower emhttp: SAMSUNG_HD103SI_S1VSJ90Z345691 (sdf) 976762584
Dec 13 18:10:53 Tower emhttp: WDC_WD5000AAKS-00TMA0_WD-WMAPW1213536 (sdg) 488385527
Dec 13 18:10:53 Tower emhttp: shcmd (311): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Dec 13 18:10:53 Tower kernel: md: unRAID driver 2.3.1 installed
Dec 13 18:10:53 Tower kernel: mdcmd (1): import 0 8,16 1953514552 WDC_WD20EFRX-68EUZN0_WD-WMC4M1156591
Dec 13 18:10:53 Tower kernel: md: import disk0: [8,16] (sdb) WDC_WD20EFRX-68EUZN0_WD-WMC4M1156591 size: 1953514552
Dec 13 18:10:53 Tower kernel: mdcmd (2): import 1 8,32 1953514552 WDC_WD20EFRX-68EUZN0_WD-WCC4M0055425
Dec 13 18:10:53 Tower kernel: md: import disk1: [8,32] (sdc) WDC_WD20EFRX-68EUZN0_WD-WCC4M0055425 size: 1953514552
Dec 13 18:10:53 Tower kernel: mdcmd (3): import 2 8,80 976762552 SAMSUNG_HD103SI_S1VSJ90Z345691
Dec 13 18:10:53 Tower kernel: md: import disk2: [8,80] (sdf) SAMSUNG_HD103SI_S1VSJ90Z345691 size: 976762552
Dec 13 18:10:53 Tower emhttp: import 24 cache device: sdg
Dec 13 18:10:53 Tower emhttp: import flash device: sda
Dec 13 18:10:53 Tower kernel: mdcmd (4): import 3 8,64 976762552 WDC_WD10EADS-00L5B1_WD-WCAU48538889
Dec 13 18:10:53 Tower kernel: md: import disk3: [8,64] (sde) WDC_WD10EADS-00L5B1_WD-WCAU48538889 size: 976762552
Dec 13 18:10:53 Tower kernel: mdcmd (5): import 4 8,48 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZA8304971
Dec 13 18:10:53 Tower kernel: md: import disk4: [8,48] (sdd) WDC_WD20EARX-00PASB0_WD-WCAZA8304971 size: 1953514552
Dec 13 18:10:53 Tower kernel: mdcmd (6): import 5 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (7): import 6 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (: import 7 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (9): import 8 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (10): import 9 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (11): import 10 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (12): import 11 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (13): import 12 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (14): import 13 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (15): import 14 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (16): import 15 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (17): import 16 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (18): import 17 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (19): import 18 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (20): import 19 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (21): import 20 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (22): import 21 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (23): import 22 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (24): import 23 0,0
Dec 13 18:10:54 Tower avahi-daemon[1504]: Service "Tower" (/services/smb.service) successfully established.

Link to comment

Here is your problem:

Dec 13 18:10:53 Tower emhttp: wrong GUID: /boot/config/Plus.key (0781-5571-2000-020807108110)

Dec 13 18:10:53 Tower emhttp: Unregistered

 

The GUID of the memory device registered according to your .key file is not the same as the GUID of the device you are booting from.  This means that your system is being treated as a license-free, three disk, system, and you have too many drives configured.

Link to comment
I am using a new flash drive.

The unRAID license is tied to the flash drive by means of its 'electronic' ID (GUID).  If you change the flash drive, you need a new .key file.  If you can justify having to change the flash drive, Limetech will, generally, give you a new .key file without charge.

Link to comment

I am using a new flash drive.

The unRAID license is tied to the flash drive by means of its 'electronic' ID (GUID).  If you change the flash drive, you need a new .key file.  If you can justify having to change the flash drive, Limetech will, generally, give you a new .key file without charge.

 

There is also the offer of a second key for only $30.00.  See here:

 

    http://lime-technology.com/second-key/

Link to comment

I'm having a problem starting my array.  I just upgraded from 5 to 6b12.  It says "Stopped. Unclean shutdown detected." but even after clean restarts from the GUI it persists.  How can I troubleshoot this?

 

Dec 13 18:10:53 Tower emhttp: too many devices
Dec 13 18:10:53 Tower emhttp: shcmd (302): :>/etc/samba/smb-shares.conf
Dec 13 18:10:53 Tower emhttp: Restart SMB...
Dec 13 18:10:53 Tower avahi-daemon[1504]: Files changed, reloading.
Dec 13 18:10:53 Tower emhttp: shcmd (303): killall -HUP smbd
Dec 13 18:10:53 Tower emhttp: shcmd (304): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service
Dec 13 18:10:53 Tower avahi-daemon[1504]: Files changed, reloading.
Dec 13 18:10:53 Tower avahi-daemon[1504]: Service group file /services/smb.service changed, reloading.
Dec 13 18:10:53 Tower emhttp: shcmd (305): pidof rpc.mountd &> /dev/null
Dec 13 18:10:53 Tower emhttp: shcmd (306): /etc/rc.d/rc.atalk status
Dec 13 18:10:53 Tower emhttp: shcmd (308): rmmod md-mod |& logger
Dec 13 18:10:53 Tower kernel: md: unRAID driver removed
Dec 13 18:10:53 Tower emhttp: wrong GUID: /boot/config/Plus.key (0781-5571-2000-020807108110)
Dec 13 18:10:53 Tower emhttp: Unregistered
Dec 13 18:10:53 Tower emhttp: array slots: 24
Dec 13 18:10:53 Tower emhttp: cache slots: 1
Dec 13 18:10:53 Tower emhttp: shcmd (309): udevadm settle
Dec 13 18:10:53 Tower emhttp: shcmd (310): /sbin/btrfs device scan |& logger
Dec 13 18:10:53 Tower logger: Scanning for Btrfs filesystems
Dec 13 18:10:53 Tower emhttp: Device inventory:
Dec 13 18:10:53 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WMC4M1156591 (sdb) 1953514584
Dec 13 18:10:53 Tower emhttp: WDC_WD20EFRX-68EUZN0_WD-WCC4M0055425 (sdc) 1953514584
Dec 13 18:10:53 Tower emhttp: WDC_WD20EARX-00PASB0_WD-WCAZA8304971 (sdd) 1953514584
Dec 13 18:10:53 Tower emhttp: WDC_WD10EADS-00L5B1_WD-WCAU48538889 (sde) 976762584
Dec 13 18:10:53 Tower emhttp: SAMSUNG_HD103SI_S1VSJ90Z345691 (sdf) 976762584
Dec 13 18:10:53 Tower emhttp: WDC_WD5000AAKS-00TMA0_WD-WMAPW1213536 (sdg) 488385527
Dec 13 18:10:53 Tower emhttp: shcmd (311): modprobe md-mod super=/boot/config/super.dat slots=24 |& logger
Dec 13 18:10:53 Tower kernel: md: unRAID driver 2.3.1 installed
Dec 13 18:10:53 Tower kernel: mdcmd (1): import 0 8,16 1953514552 WDC_WD20EFRX-68EUZN0_WD-WMC4M1156591
Dec 13 18:10:53 Tower kernel: md: import disk0: [8,16] (sdb) WDC_WD20EFRX-68EUZN0_WD-WMC4M1156591 size: 1953514552
Dec 13 18:10:53 Tower kernel: mdcmd (2): import 1 8,32 1953514552 WDC_WD20EFRX-68EUZN0_WD-WCC4M0055425
Dec 13 18:10:53 Tower kernel: md: import disk1: [8,32] (sdc) WDC_WD20EFRX-68EUZN0_WD-WCC4M0055425 size: 1953514552
Dec 13 18:10:53 Tower kernel: mdcmd (3): import 2 8,80 976762552 SAMSUNG_HD103SI_S1VSJ90Z345691
Dec 13 18:10:53 Tower kernel: md: import disk2: [8,80] (sdf) SAMSUNG_HD103SI_S1VSJ90Z345691 size: 976762552
Dec 13 18:10:53 Tower emhttp: import 24 cache device: sdg
Dec 13 18:10:53 Tower emhttp: import flash device: sda
Dec 13 18:10:53 Tower kernel: mdcmd (4): import 3 8,64 976762552 WDC_WD10EADS-00L5B1_WD-WCAU48538889
Dec 13 18:10:53 Tower kernel: md: import disk3: [8,64] (sde) WDC_WD10EADS-00L5B1_WD-WCAU48538889 size: 976762552
Dec 13 18:10:53 Tower kernel: mdcmd (5): import 4 8,48 1953514552 WDC_WD20EARX-00PASB0_WD-WCAZA8304971
Dec 13 18:10:53 Tower kernel: md: import disk4: [8,48] (sdd) WDC_WD20EARX-00PASB0_WD-WCAZA8304971 size: 1953514552
Dec 13 18:10:53 Tower kernel: mdcmd (6): import 5 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (7): import 6 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (: import 7 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (9): import 8 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (10): import 9 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (11): import 10 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (12): import 11 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (13): import 12 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (14): import 13 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (15): import 14 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (16): import 15 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (17): import 16 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (18): import 17 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (19): import 18 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (20): import 19 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (21): import 20 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (22): import 21 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (23): import 22 0,0
Dec 13 18:10:53 Tower kernel: mdcmd (24): import 23 0,0
Dec 13 18:10:54 Tower avahi-daemon[1504]: Service "Tower" (/services/smb.service) successfully established.

 

Did you do  this

 

Starting in -beta7, if your Plus or Pro key is located in the root of

your USB Flash device you must move it to the 'config' directory in

order for it to be recognized.

Link to comment

I'm having a problem starting my array.  I just upgraded from 5 to 6b12.  It says "Stopped. Unclean shutdown detected." but even after clean restarts from the GUI it persists.  How can I troubleshoot this?

 

Dec 13 18:10:53 Tower emhttp: shcmd (308): rmmod md-mod |& logger

Dec 13 18:10:53 Tower kernel: md: unRAID driver removed

Dec 13 18:10:53 Tower emhttp: wrong GUID: /boot/config/Plus.key (0781-5571-2000-020807108110)

Dec 13 18:10:53 Tower emhttp: Unregistered

 

Did you do  this

 

Starting in -beta7, if your Plus or Pro key is located in the root of

your USB Flash device you must move it to the 'config' directory in

order for it to be recognized.

 

It would seem so!

Link to comment

Had a hard crash today, not sure what caused it, server was completely unresponsive.  Took a hard reset to get it back up and going again.  I'll keep a closer eye on it to see if I can figure out what caused it.

 

Only thing that I can think of that's different on the system than prior to the crash is that I did have 2 dockers running that I normally don't cAdvisor and MediaBrowser.  cAdvisor has been running for about 3 days, where MediaBrowser was started about 1am last night.

 

Link to comment
Did you do  this

 

Starting in -beta7, if your Plus or Pro key is located in the root of

your USB Flash device you must move it to the 'config' directory in

order for it to be recognized.

Nope, wasn't aware of that.  It might be nice if UnRaid built a better error notification in for this-- a big OS upgrade is a pretty good time to do a bit of a hardware refresh, and I wouldn't be surprised if others decided to put it on a new flash drive.

 

That said: This is finally the UnRaid I have always wanted.  Docker integration is stupendously awesome, and I was able to get all of my applications up and running easily.  And I have always wanted a way to do cloud backup for my server, and the Crashplan Docker container is brilliant and easy.  My 1.5TB of photos is now on its way to Crashplan's servers, and my MBP laptop is doing just fine with an AFP target on my UnRaid box.  I am very impressed with where the system is right now, and it all feels like a big step up over 5.0.

 

I and others are often very critical about the folks behind UnRaid, and not without good reason.  But right now I am overlooking the complaints and loving my new server.  Thanks everyone.

Link to comment

Quote from: thestewman on December 13, 2014, 07:51:08 PM

Quote from: CUclimber on December 13, 2014, 06:13:29 PM

I'm having a problem starting my array.  I just upgraded from 5 to 6b12.  It says "Stopped. Unclean shutdown detected." but even after clean restarts from the GUI it persists.  How can I troubleshoot this?

 

Dec 13 18:10:53 Tower emhttp: shcmd (308): rmmod md-mod |& logger

Dec 13 18:10:53 Tower kernel: md: unRAID driver removed

Dec 13 18:10:53 Tower emhttp: wrong GUID: /boot/config/Plus.key (0781-5571-2000-020807108110)

Dec 13 18:10:53 Tower emhttp: Unregistered

 

Did you do  this

 

Starting in -beta7, if your Plus or Pro key is located in the root of

your USB Flash device you must move it to the 'config' directory in

order for it to be recognized.

 

It would seem so!

« Last Edit: Today at 03:19:55 AM by PeterB »

 

Did you do  this

 

Starting in -beta7, if your Plus or Pro key is located in the root of

your USB Flash device you must move it to the 'config' directory in

order for it to be recognized.

Nope, wasn't aware of that.  It might be nice if UnRaid built a better error notification in for this-- a big OS upgrade is a pretty good time to do a bit of a hardware refresh, and I wouldn't be surprised if others decided to put it on a new flash drive.

 

That said: This is finally the UnRaid I have always wanted.  Docker integration is stupendously awesome, and I was able to get all of my applications up and running easily.  And I have always wanted a way to do cloud backup for my server, and the Crashplan Docker container is brilliant and easy.  My 1.5TB of photos is now on its way to Crashplan's servers, and my MBP laptop is doing just fine with an AFP target on my UnRaid box.  I am very impressed with where the system is right now, and it all feels like a big step up over 5.0.

 

I and others are often very critical about the folks behind UnRaid, and not without good reason.  But right now I am overlooking the complaints and loving my new server.  Thanks everyone.

 

Looks like the error message of Wrong GUID is incorrect and misleading

Link to comment

Looks like the error message of Wrong GUID is incorrect and misleading

 

I'm not so sure::

 

I am using a new flash drive.  I'll try the old one and see if that fixes things.

 

Good catch. I  missed that.

I am glad he got it corrected

Now we will never know what corrected the error unless he returns and tells us.

Link to comment

Had a hard crash today, not sure what caused it, server was completely unresponsive.  Took a hard reset to get it back up and going again.  I'll keep a closer eye on it to see if I can figure out what caused it.

 

Only thing that I can think of that's different on the system than prior to the crash is that I did have 2 dockers running that I normally don't cAdvisor and MediaBrowser.  cAdvisor has been running for about 3 days, where MediaBrowser was started about 1am last night.

In checking over my server, I noticed I was way behind on the bios updates (1708 where the new is 2501), so I went ahead and updated it.  It looks like my CPU speeds are being reported correctly on the Dashboard page now (I had the max speed always shown here before).  It shows each CPU at 1400, with occasionally bumps up to the normal clock speed of 3500 now.  May not be 100% correct (not sure how slow mine throttles, will look into it though), but it's showing something different than it was pre-2501 bios at any rate.

 

*EDIT*  Checked with this command:

 

watch -n .5 grep \"cpu MHz\" /proc/cpuinfo

 

And it appears to be updating the same as what that shows.  Could be the old bios had issues reporting CPU speeds before?

 

Link to comment

I don't think the bar graph to the right of 'Tools' is in the new release.

 

Remember the old Dynamix was installed from /boot/plugins. Remove that directory.

 

It's hard to see your screen capture with the black theme.  Can you turn it off and get a new screen capture?

here you go...

 

on a side note, if i stop the array, then the dashboard populates! then i start the array and the dashboard is empty.

 

 

I'm having the exact same issues.  Brand new install last night, xfs file system.  SMx10sl7-f with a Xeon e3-1246.  No dashboard when I start my array.

Link to comment

Without a parity drive assigned, the dashboard has a red box on the "faulty" line in the array status table and displays "parity is invalid" in the parity status area. There should be a box or dot (grey maybe?) beside the unassigned line and the parity status should say not assigned.

 

The main display also lists array of 2 disks even though I only have disk1 and a cache disk assigned. I don't believe the cache should be considered an array disk so it should say an array of 1 disk.

 

And no, The parity drive is not missing or red-balled. It is "not installed".

Link to comment

For what it is worth I just upgraded to b12.

 

Stopped docker.

Removed addon

Upgraded using addon method.

rebooted

 

and my parity drive was unassigned and it is now running a complete parity sync :(

 

Not clue how that happened and its not end of the world but far from ideal.

 

Putting it down to a UI gremlin

 

Update: parity seems to be 40-50MB slower as well

Update2: after a couple of hours parity speed back to where i expect. I dont know what gremlin caused all this but as of now other that the parity drive was dropped and needed readded all looks ok

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.