Gico

Members
  • Content Count

    210
  • Joined

  • Last visited

Community Reputation

9 Neutral

About Gico

  • Rank
    Member

Converted

  • Gender
    Undisclosed
  • Location
    Israel

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. OK - No New Config. As for both parity at once - I wanted to have one valid parity while synching.
  2. Done, parity2 replaced. This procedure can be done with parity1 too, right? New Config, un-assign parity1, check the parity is valid box and start the array. Then stop the array, assign new parity1 disk, start the array to begin rebuild of parity1.
  3. OK, so it's parity 2. Do I need new config? I thought to do all this changes in one array stop: Data disks assignment changes (only sequence changes, no additions/removals/replaces), add new empty slot, un-assign parity 2, assign the new disk as parity 2, and start the array to rebuild parity 2. Parity 1 should remain valid.
  4. Thanks. I hoped that plugins would check if disk is mounted before addressing it.
  5. Thanks. For Preclear I will ask in Preclear forum, but what about UD and unmounted disks? Following an example with sdp and sdq which are not mounted. Jan 12 10:56:33 Juno unassigned.devices: Error: shell_exec(/usr/sbin/hdparm -C /dev/sdp 2>/dev/null | /bin/grep -c standby) took longer than 10s! Jan 12 10:57:20 Juno unassigned.devices: Error: shell_exec(/usr/sbin/hdparm -C /dev/sdq 2>/dev/null | /bin/grep -c standby) took longer than 10s! Jan 12 10:57:20 Juno unassigned.devices: Error: shell_exec(/usr/sbin/hdparm -C /dev/sdq 2>/dev/null | /bin/grep -c standby) took lon
  6. How is it that all these disks has an issue around on the same time? Seems there is another root cause for these errors at that time. All these disks sdq, sdq, sdz, sdae etc. are backup drives that 95% of the time are not mounted, and most of them are quite new and have not been used other than being backup drives. Anyway please look at January 11th issues when all these drives were not mounted. Is there a reason for any plugin to access an unmounted drive? Yes disk 9 has read errors, but SMART report seems OK other than stable 13 UDMA CRC error count.
  7. I have a repeating error, multiple times a day: Jan 11 16:12:01 Juno unassigned.devices: Error: shell_exec(/usr/sbin/hdparm -C /dev/sdp 2>/dev/null | /bin/grep -c standby) took longer than 10s! It happens very frequently to this device (sdq) and to sdp, which are both unmounted, and less frequently to others.
  8. Background: Current server has 20 disk slots that are fully utilized, although not all disks are 12TB yet. (Tried so far to leave 2 backup disks with 3.3v pin issue permanently installed because of the tape I used to cover that pin). I want to begin changing the server to 16TB or 18 TB disks. and a new server (planned to be built this year) would have 24 slots so I can use the "smaller" 12TB disks. I would like to avoid adding 12TB disks to the current server, so I though I can expand (add a new drive, not replace) my array now with the 16TB disk that I already have,
  9. I have two 12TB parity disks, and I want to add to the array a 16TB disk, so only 12 TB of the data disk would be available. When I will replace the parity disks, would the extra 4TB on the data disk be available immediately, after restart, or any other action would be needed?
  10. Looking through IPMI in Maintenance --> System Event Log, and in Server Health --> Event Log and nothing relevant in both. I have only one memory stick so I know which slot. I guess I can disable the ECC for the memtest, and enable it afterwards.
  11. Hi, Can anyone advice what to do? This issue began yesterday, I rebooted the server hoping this is a one-time thing, and got the same error. Should I memcheck? For how long? juno-diagnostics-20201021-0551.zip
  12. What about Unassigned Devices? Any limit on their number?
  13. Thanks. That narrows the issue to the docker daemon running in debug mode. I'll create a thread at the Bug Report after upgrading to v6.8 and checking that the problem continues. Hopefully this is not considered as crosspost.
  14. After deleting and recreating the docker image, the docker service would not start. I had to restart the server and that solved this issue. However even without any container, the docker is in debug mode: root@Juno:~# docker info | grep -i debug.*server Debug Mode (server): true Can anyone check his docker service whether he gets Debug Mode true or false?