ambly

Members
  • Posts

    18
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

ambly's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Still no one that is experiencing this? sh: 1: nmblookup: not found libnfs error: Invalid address:. Can not resolv into IPv4/v6 structure. libnfs error: Failed to start connection
  2. Hi, I get this error "libnfs error" and i cant access my NFS shares from Kodi. Is their a way to get around this problem?
  3. Case closed. Reformatted the Cache drive. It was empty except docker.img Can you run docker from XFS?
  4. Did miss that the entire cache disk was read-only. Will try and repair it.
  5. Thats what i'm thinking but the docker.img file can't be deleted thrugh thw GUI and when i try to delete it from SSH it say's "cannot remove ‘/mnt/cache/Docker/docker.img’: Read-only file system " sjulf i deletet it with a btrfs command?
  6. My Docker has suddenly stopped working and the menu "Docker" in the WebGUI is gone... Tried to create a new image under Settings -> Docker but still no menu. Any suggestions on what gone wrong?
  7. If it is "red" a "write" to that disk failed and it was marked as being invalid. You are now reading and writing to the "simulated" drive made possible by reading parity in combination with all the other data disks. Being able to browse the disk is not an indication of that disk's health. It is an indication your unRAID is protecting you from a single disk failure. Now, the "write" might have failed because the disk itself failed, or it might be because a cable to it is loose, or because the power supply used is inadequate for the combined set of disks used, and it just did not get enough power. Step one would be to get a SMART report on the drive. If it responds, it might give an indication of its health. Id it does not respond, time to power down and re-check the cabling. See here: http://lime-technology.com/wiki/index.php?title=FAQ#What_does_the_Red_Ball_mean.3F Found no SMART errors and no faulty cables. Disabled the disk and enabled it back and did a rebuild. Same red dot on the disk. Fond this in the log. Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] Unhandled error code Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] Result: hostbyte=0x04 driverbyte=0x00 Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] CDB: cdb[0]=0x2a: 2a 00 e5 fe 1a 07 00 03 68 00 Shal i replace the disk or can i fix it? If you are using hotswap bays, try a different one. If you are not, try hooking the drive up to a different SATA port. I believe you either have a faulty SATA port, or a faulty hotswap bay and you should try bypassing both ports. You should also try a 3rd SATA cable, and a new power cable. I've had 2 bad SATA cables in a row more than once... Seems like they come together. Some people on here will claim power cables tend to go bad more than SATA cables, so definitely try that too. It could also be that your PSU is on the way out and is struggling to power everything, but if it was fine before and you aren't using a budget PSU - thats probably not it. The HW setup has not changed for a year. Checked the cables but did't have any spares at home. Doing a data rebuild now, but it will take some time to run (2Tb disk) Does SATA ports and cables fail, all at a sudden? SATA ports can die suddenly or randomly start causing issues. SATA cables usually don't cause issues unless its faulty out of the box or someone bent it a little to much.. but i've had some cables go bad in my day. I think I had a similiar issues as you awhile back, where I could rebuild the data on the drive - but it'd still turn red after a little while. No smart errors or any log errors. After replacing the drive it went away. It could be many things though. I usually use a failing drive as an excuse to upgrade. I buy a new one and swap it out, if it fixes it - I RMA the bad drive, if it doesn't then you know it's something else. After my cable exercise wher i just felt that the cables was connecter i did a rebuild. And it completed without errors this time. Think i will replace the cables but now is everything ok!
  8. If it is "red" a "write" to that disk failed and it was marked as being invalid. You are now reading and writing to the "simulated" drive made possible by reading parity in combination with all the other data disks. Being able to browse the disk is not an indication of that disk's health. It is an indication your unRAID is protecting you from a single disk failure. Now, the "write" might have failed because the disk itself failed, or it might be because a cable to it is loose, or because the power supply used is inadequate for the combined set of disks used, and it just did not get enough power. Step one would be to get a SMART report on the drive. If it responds, it might give an indication of its health. Id it does not respond, time to power down and re-check the cabling. See here: http://lime-technology.com/wiki/index.php?title=FAQ#What_does_the_Red_Ball_mean.3F Found no SMART errors and no faulty cables. Disabled the disk and enabled it back and did a rebuild. Same red dot on the disk. Fond this in the log. Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] Unhandled error code Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] Result: hostbyte=0x04 driverbyte=0x00 Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] CDB: cdb[0]=0x2a: 2a 00 e5 fe 1a 07 00 03 68 00 Shal i replace the disk or can i fix it? If you are using hotswap bays, try a different one. If you are not, try hooking the drive up to a different SATA port. I believe you either have a faulty SATA port, or a faulty hotswap bay and you should try bypassing both ports. You should also try a 3rd SATA cable, and a new power cable. I've had 2 bad SATA cables in a row more than once... Seems like they come together. Some people on here will claim power cables tend to go bad more than SATA cables, so definitely try that too. It could also be that your PSU is on the way out and is struggling to power everything, but if it was fine before and you aren't using a budget PSU - thats probably not it. The HW setup has not changed for a year. Checked the cables but did't have any spares at home. Doing a data rebuild now, but it will take some time to run (2Tb disk) Does SATA ports and cables fail, all at a sudden?
  9. If it is "red" a "write" to that disk failed and it was marked as being invalid. You are now reading and writing to the "simulated" drive made possible by reading parity in combination with all the other data disks. Being able to browse the disk is not an indication of that disk's health. It is an indication your unRAID is protecting you from a single disk failure. Now, the "write" might have failed because the disk itself failed, or it might be because a cable to it is loose, or because the power supply used is inadequate for the combined set of disks used, and it just did not get enough power. Step one would be to get a SMART report on the drive. If it responds, it might give an indication of its health. Id it does not respond, time to power down and re-check the cabling. See here: http://lime-technology.com/wiki/index.php?title=FAQ#What_does_the_Red_Ball_mean.3F Found no SMART errors and no faulty cables. Disabled the disk and enabled it back and did a rebuild. Same red dot on the disk. Fond this in the log. Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] Unhandled error code Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] Result: hostbyte=0x04 driverbyte=0x00 Sep 29 14:59:23 HKSRV03 kernel: sd 2:0:0:0: [sdd] CDB: cdb[0]=0x2a: 2a 00 e5 fe 1a 07 00 03 68 00 Shal i replace the disk or can i fix it?
  10. Logged in to my Unraid today and saw that a disk was marked red. Can't see anything in the logg and i can browse the disk. Any idea?