Charles Elliott
Dabbler
- Joined
- Oct 13, 2013
- Messages
- 37
FreeNAS is being used by Windows 8.
The first update (9.2.0) turned the daily emailed log into a couple of lines of gibberish. The second made the log disappear; now no log is emailed. The third did not fix the problem. How do I get the log back, i.e., emailed to me with Ethernet statistics (e.g., packets and bytes transferred by interface)? Also, how can I get the security log back, i.e., emailed?
During the install, the second update declared that one of the hard disks had an error, and that the system was now running in degraded mode. Indeed, it did not lie, about the degraded performance. Formerly, I regularly saw 340 Mbs from the NAS; now 40 Mbs is a triumph. It used to take seconds to transfer a 2 GB file, now it literally takes minutes. None of the NAS error messages tell what disk is thought to be bad (3 x 1 TB rotating drives, 1 x 128 GB SSD, and 1 x 40 GB Patriot USB drive). How do I find out what disk is deemed bad and how do I fix it if I do find it?
The third install not only caught the alleged error (4 of the 5 hard drives are less than a few months old), but now flashes a yellow light in the Alerts icon. When the icon is clicked, the message is displayed:
"
The first update (9.2.0) turned the daily emailed log into a couple of lines of gibberish. The second made the log disappear; now no log is emailed. The third did not fix the problem. How do I get the log back, i.e., emailed to me with Ethernet statistics (e.g., packets and bytes transferred by interface)? Also, how can I get the security log back, i.e., emailed?
During the install, the second update declared that one of the hard disks had an error, and that the system was now running in degraded mode. Indeed, it did not lie, about the degraded performance. Formerly, I regularly saw 340 Mbs from the NAS; now 40 Mbs is a triumph. It used to take seconds to transfer a 2 GB file, now it literally takes minutes. None of the NAS error messages tell what disk is thought to be bad (3 x 1 TB rotating drives, 1 x 128 GB SSD, and 1 x 40 GB Patriot USB drive). How do I find out what disk is deemed bad and how do I fix it if I do find it?
The third install not only caught the alleged error (4 of the 5 hard drives are less than a few months old), but now flashes a yellow light in the Alerts icon. When the icon is clicked, the message is displayed:
"
WARNING:
The volume Mark (ZFS) status is ONLINE: One or more devices has experienced an unrecoverable error. An attempt was made to correct the error. Applications are unaffected.Determine if the device needs to be replaced, and clear the errors using 'zpool clear' or replace the device with 'zpool replace'."
Note that no device is named; the system knows what device is ailing and probably what it thinks is wrong with it. Why can't it enunciate that information?
I fired up the shell and typed 'zpool clear', since I don't believe there truly is an error, but the shell says there is no command named zpool. Again, How do I find out what disk is deemed bad and how do I fix it if I do find it?
I could probably find the bad disk, if any, if I could just find reports of the S.M.A.R.T. tests. I set up the NAS to run one short test on each of the three 1 TB data storage disks each night, and one long test each month during the night. I can't find any of the test results or any way to find the test results. How do I find out if the S.M.A.R.T. tests are running, and where are the results if they are running?
I have a number of downloaded utility programs on the NAS to which I have installed shortcuts on the Office toolbar. After the first update, none of those programs would execute, and I had to transfer them to the C: drive. However, I just tried running several programs from the NAS, and that appears to be fixed.
The first update made it so I could not log in to the NAS. And of course I could not use any of the drive mappings in Windows Explorer to various parts of the NAS. I was finally able to log in to the NAS using the root account, and I was able to reestablish the drive mappings in Windows Explorer using root. But nothing I have tried (many, many times) will allow me to log in with my user name and password. How do I reestablish my user account on the NAS?
After the second of the three updates, every time I start the NAS, the following error messages appear at the end of the log:
"Mar 19 22:27:40 freenas mDNSResponder: mDNSResponder (Engineering Build) (Mar 1 2014 18:12:24) starting
Mar 19 22:27:40 freenas mDNSResponder: 11: Listening for incoming Unix Domain Socket client requests
Mar 19 22:27:40 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar 19 22:27:40 freenas last message repeated 2 times
Mar 19 22:27:41 freenas kernel: done.
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 1.1.168.192.in-addr.arpa. (PTR) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C31D60 freenas.local. (Addr) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C32180 1.0.168.192.in-addr.arpa. (PTR) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C33D60 freenas.local. (AAAA) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C34180 A.A.C.F.4.A.E.F.F.F.0.9.5.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C35D60 freenas.local. (AAAA) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C36180 B.A.C.F.4.A.E.F.F.F.0.9.5.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list"
Mar 19 22:27:40 freenas mDNSResponder: 11: Listening for incoming Unix Domain Socket client requests
Mar 19 22:27:40 freenas mDNSResponder: mDNS_AddDNSServer: Lock not held! mDNS_busy (0) mDNS_reentrancy (0)
Mar 19 22:27:40 freenas last message repeated 2 times
Mar 19 22:27:41 freenas kernel: done.
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C2FD60 freenas.local. (Addr) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C30180 1.1.168.192.in-addr.arpa. (PTR) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C31D60 freenas.local. (Addr) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C32180 1.0.168.192.in-addr.arpa. (PTR) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C33D60 freenas.local. (AAAA) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C34180 A.A.C.F.4.A.E.F.F.F.0.9.5.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C35D60 freenas.local. (AAAA) that's already in the list
Mar 19 22:27:41 freenas mDNSResponder: mDNS_Register_internal: ERROR!! Tried to register AuthRecord 0000000800C36180 B.A.C.F.4.A.E.F.F.F.0.9.5.2.2.0.0.0.0.0.0.0.0.0.0.0.0.0.0.8.E.F.ip6.arpa. (PTR) that's already in the list"
Do these messages really matter? How can I prevent them from being output?
On the main page of the FreeNAS browser window, in the left-hand pane, in the Volumes/View Volumes leaf, is the following information:
Name Used Available Size Compression Compression Ratio Status
Mark 885.0 GiB (48%) 940.2 GiB 1.8 TiB lz4 1.04x HEALTHY
Since the NAS data volume is deemed healthy, and the O/S and NAS is running on the USB drive, does that imply that the 128 GB SSD is probably the drive that is causing the system to be degraded?
Am I really getting 1.04x compression, that is, the data on the volume is larger than the sum of the file lengths?
While it is booting, the third (9.2.1.2) of the three updates outputs a large number of error messages. I ran it twice before I let the update proceed, but always saw the same messages. I am a Windows user, and all the messages are in FreeBSD jargon, so I can't decipher them, but in the future could you please test the install to avoid terrorizing the users? All my PhD research notes and all my documents are on this NAS. The terror is real.
