Channels
extensions
rancher-extensions
supermicro-sixsq
ozt
os
one-point-x
rio
onlinemeetup
v16-v21-migration
events
onlinetraining
training-1220
training-0110
training-0124
k3s-contributor
submariner
storage
k3os
windows
ci-cd
theranchcast
rfed_ara
nederlands
ukranian
danish
training-0131
masterclass
training-0207
training-0214
terraform-controller
epinio
phillydotnet
swarm
rancher-wrangler
deutsch
russian
chinese
mesos
français
japanese
arm
longhorn-dev
terraform-provider-rke
service-mesh
azure
gcp
academy
random
elemental
espanol
lima
harvester-dev
portugues
kubernetes
kim
hypper
kubewarden
opni
logging
neuvector-security
rancher-setup
developer
office-hours
mexico
cabpr
rke
vsphere
longhorn-storage
k3s
k3d
terraform-provider-rancher2
fleet
amazon
harvester
rke2
s3gw
hobbyfarm
rancher-desktop
general
Title
h
high-butcher-71851
09/20/2022, 10:35 PMWhere is the best place to find logs to figure out why a volume has entered “Faulted” state after attempting to “attach to host” ?
Thanks!
q
quick-sandwich-76600
09/21/2022, 2:29 PMThe OS level dmesg can give you some clues.
Also the even log may have information. You can run:
kubectl -n longhorn-system get event | grep <volume name>And finally the Longhorn manager logs:
kubectl -n longhorn-system logs <longhorn manager pod name> | grep <volume name>If you want to have all relevant info together (log, configs, ...) you can generate a support bundle following this procedure: https://www.suse.com/es-es/support/kb/doc/?id=000020145
That's just a zip file with all the info available that you can unzip and use grep/find with the volume id to find all the references.
Longhorn KB has several articles covering attach issues that can help you or at least give you clues about how to better debug your specific issue: https://longhorn.io/kb/
h
high-butcher-71851
09/21/2022, 4:17 PMThank you!
👍 1