January 28, 20179 yr Hi, I did a clean install of latest stable 6.2. After that I observed several things and want to make sure everything this is normal and not an error I should solve. 1) I did inmediatly a parity-check and it showed 9 errors (I attach my syslog). I installed fix common problems and it did show no errors. Can anyone tell me if there is anything to worry about? 2) After that I run a SMART extended self-test on Disk 4 because I got a pop up showing a warning (reallocated sector ct is 42). It completed with no errors (I attach the result). Is there anything to worry about? 3) When I start Unraid I get this message: default via 192.168.0.1 dev br0 linkdown 192.168.0.1/24 dev br0 proto kernel scope link src 192.168.0.106 linkdown I am able to connect to unraid´s gui from another computer. Is this normal? 4) This device is a pci ethernet adapter. What is wrong with it? Error: Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 0: error updating (0x001001 != 0x000021) Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 1: error updating (0xc0800800 != 0x0000fc) Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 1: error updating (0xc0900800 != 0x0000fc) Warning: Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 4: [mem 0x82b00000816910c0-0x82b00001816910bf 64bit pref] conflicts with PCI mem [mem 0x00000000-0xffffffffffff] Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 4: failed to assign [mem size 0x100000000 64bit pref] Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 4: [mem 0x82b00000816910c0-0x82b00001816910bf 64bit pref] conflicts with PCI mem [mem 0x00000000-0xffffffffffff] Jan 27 18:07:40 Tower kernel: pci 0000:05:05.0: BAR 4: failed to assign [mem size 0x100000000 64bit pref] 5) fix common problems reports: Disk disk7 has an HPA partition enabled on it It is a data disk, anything I should do? Rgds tower-smart-20170128-1133.zip
January 28, 20179 yr 2. A few reallocated blocks are not a problem in themselves so keep an eye on the number and if it holds steady you can keep using the disk. If the number increases over time you'll need to replace the disk. If it's under warranty you may want to RMA it anyway. 3. The Ethernet link is down or intermittent so check your cable and switch port. 5. As it's a data disk it doesn't really matter. An HPA reserves a small part of the disk capacity, making it slightly smaller than standard. It's only an issue if you want to use it as a parity disk, which can't be smaller than the largest data disk. For the rest please post your complete diagnostics zip, not just fragments.
January 28, 20179 yr 1) I did inmediatly a parity-check and it showed 9 errors (I attach my syslog). 1) The only correct number of parity errors is exactly zero. You should do another parity check. And you didn't attach your syslog, you only attached SMART for one disk. And we don't want either. We want your complete diagnostics. Always go to Tools - Diagnostics and post your complete diagnostics zip. 2) After that I run a SMART extended self-test on Disk 4 because I got a pop up showing a warning (reallocated sector ct is 42). It completed with no errors (I attach the result). Is there anything to worry about? 42 is a little high but just keep an eye on it and if it starts to increase you should replace. ... 5) fix common problems reports: Disk disk7 has an HPA partition enabled on it It is a data disk, anything I should do? Search the forum for HPA. See How to Search sticky linked in my sig. HPA isn't much to worry about unless you try to use the disk as parity since it will not be as large as similar drives and parity must be at least as large as your largest data disk.
January 28, 20179 yr Author Here is the full diagnostics zip. Regarding "3. The Ethernet link is down or intermittent so check your cable and switch port" I just changed tha cable and tried a new one, and I still get the same message. What other things should I check? Thx for support.
January 28, 20179 yr Assuming that this Jan 27 15:26:20 Tower kernel: r8169 0000:08:00.0 eth0: link down Jan 27 15:26:20 Tower kernel: br0: port 1(eth0) entered disabled state Jan 27 15:26:23 Tower ntpd[1623]: Deleting interface #2 br0, 192.168.0.106#123, interface stats: received=0, sent=162, dropped=0, active_time=60078 secs Jan 27 15:26:23 Tower ntpd[1623]: 193.145.15.15 local addr 192.168.0.106 -> <null> Jan 27 15:26:29 Tower kernel: r8169 0000:08:00.0 eth0: link up Jan 27 15:26:29 Tower kernel: br0: port 1(eth0) entered forwarding state Jan 27 15:26:29 Tower kernel: br0: port 1(eth0) entered forwarding state Jan 27 15:26:30 Tower ntpd[1623]: Listen normally on 3 br0 192.168.0.106:123 Jan 27 15:26:30 Tower ntpd[1623]: new interface(s) found: waking up resolver Jan 27 15:26:32 Tower kernel: r8169 0000:08:00.0 eth0: link down Jan 27 15:26:32 Tower kernel: br0: port 1(eth0) entered disabled state Jan 27 15:26:34 Tower ntpd[1623]: Deleting interface #3 br0, 192.168.0.106#123, interface stats: received=0, sent=1, dropped=0, active_time=4 secs Jan 27 15:26:34 Tower ntpd[1623]: 193.145.15.15 local addr 192.168.0.106 -> <null> Jan 27 15:26:34 Tower kernel: r8169 0000:08:00.0 eth0: link up Jan 27 15:26:34 Tower kernel: br0: port 1(eth0) entered forwarding state Jan 27 15:26:34 Tower kernel: br0: port 1(eth0) entered forwarding state Jan 27 15:26:36 Tower ntpd[1623]: Listen normally on 4 br0 192.168.0.106:123 Jan 27 15:26:36 Tower ntpd[1623]: new interface(s) found: waking up resolver wasn't a result of you replacing the cable (maybe not, as it's dated yesterday), I'd try a different switch port.
January 28, 20179 yr 4. What Ethernet adapter is this? The only one I see that's recognised by your system is the onboard Realtek. Are you trying to use an unsupported one?
January 28, 20179 yr Author I have been using before a pci ethernet adapter. When I did the clean install I tried the realtek onboard one. Because I got the mentioned linkdown error, I tried the previous pci ethernet adapter, BUT I got no connection at all. I got this error: "Device "eth0" does not exist". So I went back to the onboard one.
January 28, 20179 yr You may need to disable the motherboard ethernet in the BIOS to get unRAID to use the other one.
January 28, 20179 yr Tell me more about it - make/model number. Did it work with a previous version of unRAID? It's either faulty or unsupported. I don't see the error messages you pasted into your original post so have you removed it now?
January 28, 20179 yr Author When i get back home i try both adapters and will post proper diagnostics for each one. sent from Tapatalk
January 28, 20179 yr Author 4. What Ethernet adapter is this? The only one I see that's recognised by your system is the onboard Realtek. Are you trying to use an unsupported one? The only one working (I mean not showing this error: Device "eth0" does not exist) is the onboard realtek one. My MB is M5A99FX PRO R2.0, so the ethernet adapter is Realtek 8111F. It don´t understand why it is working but unraid is showing: default via 192.168.0.1 dev br0 linkdown 192.168.0.1/24 dev br0 proto kernel scope link src 192.168.0.106 linkdown ? I can´t really tell if this was already happening before, since I did not experience any problems. I will keep an eye on it in case I get any network problems. Regarding the errors shown in my last parity check I will run a new one and post the results.
January 29, 20179 yr Author After running a parity check no errors were found now. Good news. One more question I have is why the user folder appears twice user and user0: root@Tower:~# cd /mnt/ root@Tower:/mnt# ls cache/ disk2/ disk4/ disk6/ disk8/ disks/ user0/ disk1/ disk3/ disk5/ disk7/ disk9/ user/ root@Tower:/mnt# cd /mnt/user root@Tower:/mnt/user# ls conciertos/ documentales/ media\ personal/ series/ data/ downloads/ movies/ root@Tower:/mnt/user# cd /mnt/user0 root@Tower:/mnt/user0# ls conciertos/ documentales/ media\ personal/ series/ data/ downloads/ movies/ root@Tower:~# df -T Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 3969148 403788 3565360 11% / tmpfs tmpfs 4005036 316 4004720 1% /run devtmpfs devtmpfs 3969160 0 3969160 0% /dev cgroup_root tmpfs 4005036 0 4005036 0% /sys/fs/cgroup tmpfs tmpfs 131072 2196 128876 2% /var/log /dev/sda1 vfat 7811056 154176 7656880 2% /boot /dev/md1 xfs 1952560688 1243548496 709012192 64% /mnt/disk1 /dev/md2 xfs 2928835740 2815392048 113443692 97% /mnt/disk2 /dev/md3 xfs 1952560688 1870990696 81569992 96% /mnt/disk3 /dev/md4 xfs 1952560688 1895337768 57222920 98% /mnt/disk4 /dev/md5 xfs 1952560688 1875259800 77300888 97% /mnt/disk5 /dev/md6 xfs 1952560688 1738179204 214381484 90% /mnt/disk6 /dev/md7 xfs 1952559628 1647614884 304944744 85% /mnt/disk7 /dev/md8 xfs 1952560688 881985116 1070575572 46% /mnt/disk8 /dev/md9 xfs 1952560688 406608880 1545951808 21% /mnt/disk9 /dev/sdn1 xfs 117162564 32960 117129604 1% /mnt/cache shfs fuse.shfs 18549320184 14374916892 4174403292 78% /mnt/user0 shfs fuse.shfs 18666482748 14374949852 4291532896 78% /mnt/user /dev/loop0 btrfs 20971520 1482380 17617108 8% /var/lib/docker Anyone can point me out why this is happening?
January 29, 20179 yr After running a parity check no errors were found now. Good news. One more question I have is why the user folder appears twice user and user0: root@Tower:~# cd /mnt/ root@Tower:/mnt# ls cache/ disk2/ disk4/ disk6/ disk8/ disks/ user0/ disk1/ disk3/ disk5/ disk7/ disk9/ user/ root@Tower:/mnt# cd /mnt/user root@Tower:/mnt/user# ls conciertos/ documentales/ media\ personal/ series/ data/ downloads/ movies/ root@Tower:/mnt/user# cd /mnt/user0 root@Tower:/mnt/user0# ls conciertos/ documentales/ media\ personal/ series/ data/ downloads/ movies/ root@Tower:~# df -T Filesystem Type 1K-blocks Used Available Use% Mounted on rootfs rootfs 3969148 403788 3565360 11% / tmpfs tmpfs 4005036 316 4004720 1% /run devtmpfs devtmpfs 3969160 0 3969160 0% /dev cgroup_root tmpfs 4005036 0 4005036 0% /sys/fs/cgroup tmpfs tmpfs 131072 2196 128876 2% /var/log /dev/sda1 vfat 7811056 154176 7656880 2% /boot /dev/md1 xfs 1952560688 1243548496 709012192 64% /mnt/disk1 /dev/md2 xfs 2928835740 2815392048 113443692 97% /mnt/disk2 /dev/md3 xfs 1952560688 1870990696 81569992 96% /mnt/disk3 /dev/md4 xfs 1952560688 1895337768 57222920 98% /mnt/disk4 /dev/md5 xfs 1952560688 1875259800 77300888 97% /mnt/disk5 /dev/md6 xfs 1952560688 1738179204 214381484 90% /mnt/disk6 /dev/md7 xfs 1952559628 1647614884 304944744 85% /mnt/disk7 /dev/md8 xfs 1952560688 881985116 1070575572 46% /mnt/disk8 /dev/md9 xfs 1952560688 406608880 1545951808 21% /mnt/disk9 /dev/sdn1 xfs 117162564 32960 117129604 1% /mnt/cache shfs fuse.shfs 18549320184 14374916892 4174403292 78% /mnt/user0 shfs fuse.shfs 18666482748 14374949852 4291532896 78% /mnt/user /dev/loop0 btrfs 20971520 1482380 17617108 8% /var/lib/docker Anyone can point me out why this is happening? /mnt/user is the contents of the array including the cache drive /mnt/user0 is the contents of the array excluding the cache drive. Its utilized by mover to move stuff back and forth to the cache drive depending upon your share settings.
January 29, 20179 yr Author Thx squid! So if I have data stored in my cache drive when I type /mnt/user my cache disk should show up and show the data stored, but I only get: root@Tower:/mnt/user# ls conciertos/ documentales/ media\ personal/ series/ data/ downloads/ movies/ system/ I can only access the cache disk typing /mnt/cache. What should I take into account to see the contents of my cache drive when I type /mnt/user?
January 29, 20179 yr Thx squid! So if I have data stored in my cache drive when I type /mnt/user my cache disk should show up and show the data stored, but I only get: root@Tower:/mnt/user# ls conciertos/ documentales/ media\ personal/ series/ data/ downloads/ movies/ system/ I can only access the cache disk typing /mnt/cache. What should I take into account to see the contents of my cache drive when I type /mnt/user? Which folders on the cache drive aren't in /mnt/user?
January 29, 20179 yr Author root@Tower:/mnt/user0# cd /mnt/cache/ root@Tower:/mnt/cache# ls system/ Sorry my fault, it is actually there!
February 2, 20179 yr Author The disk4 errors grow non stop: unRAID Disk 4 SMART health [5]: 02-02-2017 20:06 Warning [TOWER] - reallocated sector ct is 110 ST32000542AS_9XW07WDC (sdb) Last friday it showed "reallocated sector 85"! I guess I need to change the disk, right? Rgds.
February 2, 20179 yr The disk4 errors grow non stop: unRAID Disk 4 SMART health [5]: 02-02-2017 20:06 Warning [TOWER] - reallocated sector ct is 110 ST32000542AS_9XW07WDC (sdb) Last friday it showed "reallocated sector 85"! I guess I need to change the disk, right? Rgds. Yes. Have you ever replaced a disk before? Please let us know if you are unsure what to do.
February 2, 20179 yr Author Hi, I think is this one, right?: The procedure If you are running a very old version of unRAID, such as v4.7 or older, skip down to the next section. Stop the array Unassign the old drive if still assigned (to unassign, set it to No Device) Power down [ Optional ] Pull the old drive (you may want to leave it installed for Preclearing or testing) Install the new drive Power on Assign the new drive in the slot of the old drive Go to the Main -> Array Operation section Put a check in the Yes, I'm sure checkbox (next to the information indicating the drive will be rebuilt), and click the Start button The rebuild will begin, with hefty disk activity on all drives, lots of writes on the new drive and lots of reads on all other drives All of the contents of the old drive will be copied onto the new drive, making it an exact replacement, except possibly with more capacity than the old drive.
Archived
This topic is now archived and is closed to further replies.