TheBlueKingLP Posted February 12, 2019 Share Posted February 12, 2019 My array health report will say it has 0 disk after the server has been on for some time. Diagnostic is not working Quote Link to comment
TheBlueKingLP Posted March 3, 2019 Author Share Posted March 3, 2019 My unRAID Server running on 6.7.0-rc5 will report “*Notice [] - array health report [PASS]* Array has 0 disks” after around 26 hours of uptime. At this time: Web UI sometimes stopped working Dockers and VMs stays running fine with no issue. Server info is blank Smb stopped working No raid card, 6x1TB consumer hdd Cable known good and not loosen MB: Asus rampage v edition 10 P.s. If you need more info please ask for it Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 26 minutes ago, TheBlueKingLP said: If you need more info please ask for it We always need more information. Please don't make us ask for it (yet another time). Might be worthwhile to consult the "Need Help?" topic pinned near the top of this same subforum. You should always go to Tools - Diagnostics (before rebooting if possible) and attach the complete diagnostics zip file to your next post. Quote Link to comment
TheBlueKingLP Posted March 3, 2019 Author Share Posted March 3, 2019 We always need more information. Please don't make us ask for it (yet another time). Might be worthwhile to consult the "Need Help?" topic pinned near the top of this same subforum. You should always go to Tools - Diagnostics (before rebooting if possible) and attach the complete diagnostics zip file to your next post.I was going to upload the diagnostic if I could, but after it started to report 0 disk, the diagnostic button stopped working. I haven’t restarted the server yet, what could I do to get diagnostic working again? Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 Also, I noticed you had already posted about this on another thread. Please don't post on multiple threads for the same issue. This is known as crossposting and has been considered a bad thing on message boards since long before the world wide web. How are we supposed to coordinate our responses if you have a discussion going on multiple threads? I know it seems a moot point since you hadn't gotten a reply on that other thread. If it seems like you haven't gotten a response after a reasonable time, instead of starting another thread, just make a new post to that same thread. This is known as "bumping" the thread. Often people will "bump" a thread by simply making a new post to the thread with only the word "bump". I have merged your threads. Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 2 minutes ago, TheBlueKingLP said: what could I do to get diagnostic working again? Here is a link to that "Need Help?" sticky I referred to in my first reply. It explains other ways to get us the diagnostics or other information: Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 From your symptoms, I would guess your flash drive disconnected or is corrupt. Put it in your PC and let it checkdisk. Use a USB2 port on your server for your flash drive. USB3 has been known to cause issues for some. Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 On 2/12/2019 at 2:33 AM, TheBlueKingLP said: Diagnostic is not working 10 minutes ago, TheBlueKingLP said: the diagnostic button stopped working In fact, if you had just bumped your original thread I would have already seen that point you had already made. See how it wastes time and effort when you crosspost? Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 I apologize for playing the bad cop and hitting you with all this advice about how to correctly use the forum. It just happened to be a "perfect storm". Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 Since you may be having problems with flash, you should make sure you have a good backup of flash. While you have it in your PC be sure to make a copy of it. And, you can always download a zipped copy of flash in the Unraid webUI at Main - Boot Device - Flash - Flash Backup. Quote Link to comment
TheBlueKingLP Posted March 3, 2019 Author Share Posted March 3, 2019 From your symptoms, I would guess your flash drive disconnected or is corrupt. Put it in your PC and let it checkdisk. Use a USB2 port on your server for your flash drive. USB3 has been known to cause issues for some.Chkdsk report no error, I am already using a usb2 port.Here is the syslog file: https://pastebin.com/TK5SJw1K Quote Link to comment
trurl Posted March 3, 2019 Share Posted March 3, 2019 3 hours ago, TheBlueKingLP said: Chkdsk report no error, I am already using a usb2 port. Here is the syslog file: https://pastebin.com/TK5SJw1K Were you not able to get the complete diagnostics zip from the command line as instructed in that link I gave? I would much rather have complete diagnostics zip if possible and attached in this forum, not linked on an external site. If syslog is all you can get, zip it up and attach it to your next post. Quote Link to comment
TheBlueKingLP Posted March 5, 2019 Author Share Posted March 5, 2019 On 3/4/2019 at 12:27 AM, trurl said: Were you not able to get the complete diagnostics zip from the command line as instructed in that link I gave? I would much rather have complete diagnostics zip if possible and attached in this forum, not linked on an external site. If syslog is all you can get, zip it up and attach it to your next post. Here is the syslog.txt Also, I noticed the rootfs is full, I think this is what caused it,but why was it full in the first place?(It will go back to normal once I reboot.) Quote Link to comment
trurl Posted March 5, 2019 Share Posted March 5, 2019 5 hours ago, TheBlueKingLP said: I noticed the rootfs is full Yes this is definitely going to cause lots of problems. My guess is you have some docker volume mapping misconfigured so it is writing to the OS (which is in RAM) instead of to mounted storage. Why didn't you zip that syslog as asked? Did you try to get the complete diagnostics using the command line? You didn't say. Quote Link to comment
TheBlueKingLP Posted March 5, 2019 Author Share Posted March 5, 2019 47 minutes ago, trurl said: Yes this is definitely going to cause lots of problems. My guess is you have some docker volume mapping misconfigured so it is writing to the OS (which is in RAM) instead of to mounted storage. Why didn't you zip that syslog as asked? Did you try to get the complete diagnostics using the command line? You didn't say. Sorry for not zipping it, I was using my iPhone to post that. Also, after the system rootfs if full, I couldn't get the diagnostic. I will post the diagnostic file of "when the rootfs is not full" tomorrow as it is now passed midnight for me Quote Link to comment
trurl Posted March 10, 2019 Share Posted March 10, 2019 On 3/5/2019 at 12:17 PM, TheBlueKingLP said: I will post the diagnostic file of "when the rootfs is not full" tomorrow as it is now passed midnight for me Quote Link to comment
TheBlueKingLP Posted March 10, 2019 Author Share Posted March 10, 2019 (edited) 1 hour ago, trurl said: Ah, sorry about that. I’ve forgotten to post it. pegasus-diagnostics-20190310-1407.zip edit: I downloaded it when it is around 73% full Edited March 10, 2019 by TheBlueKingLP Quote Link to comment
trurl Posted March 10, 2019 Share Posted March 10, 2019 How long does it take to get to this point after booting? On 3/5/2019 at 11:26 AM, trurl said: My guess is you have some docker volume mapping misconfigured so it is writing to the OS (which is in RAM) instead of to mounted storage. Does it happen if you run for a while without dockers? Quote Link to comment
trurl Posted March 10, 2019 Share Posted March 10, 2019 Just now, trurl said: How long does it take to get to this point after booting? According to your syslog it was about 10 hours. Quote Link to comment
trurl Posted March 10, 2019 Share Posted March 10, 2019 Also, your syslog is filling up with these: Mar 10 20:54:43 Pegasus kernel: Buffer I/O error on dev sdh3, logical block 75038677, async page read This is an Unassigned Device. If you have anything trying to write to an Unassigned Device, such as a docker, but the Unassigned Device isn't mounted for some reason, then the path to that should reference that Unassigned Device would no longer be to a mounted device, but would instead be in rootfs. And I don't see any SMART for that disk so I assume it has disconnected. Quote Link to comment
TheBlueKingLP Posted March 10, 2019 Author Share Posted March 10, 2019 (edited) 10 minutes ago, trurl said: How long does it take to get to this point after booting? Does it happen if you run for a while without dockers? It happens even I’ve disabled docked entirely. also disabled vm manager Edited March 10, 2019 by TheBlueKingLP Quote Link to comment
trurl Posted March 10, 2019 Share Posted March 10, 2019 What about that Unassigned Device? Quote Link to comment
TheBlueKingLP Posted March 10, 2019 Author Share Posted March 10, 2019 What about that Unassigned Device?Is there a way to check what is using it or what is the mount point? Quote Link to comment
trurl Posted March 10, 2019 Share Posted March 10, 2019 Mar 10 20:39:03 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'UNTITLED' is not set to auto mount and will not be mounted... Mar 10 20:39:03 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'Local_Disk' is not set to auto mount and will not be mounted... Mar 10 20:39:03 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'WD_My_Passport_259F-part4' is not set to auto mount and will not be mounted... Mar 10 20:39:03 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'WD_My_Passport_259F-part1' is not set to auto mount and will not be mounted... Mar 10 20:39:52 Pegasus unassigned.devices: Adding disk '/dev/sdh1'... Mar 10 20:39:52 Pegasus unassigned.devices: No filesystem detected on '/dev/sdh1'. Mar 10 20:39:52 Pegasus unassigned.devices: Partition 'WD My_Passport_259F-part1' could not be mounted... Mar 10 20:39:52 Pegasus unassigned.devices: Adding disk '/dev/sdh2'... Mar 10 20:39:52 Pegasus unassigned.devices: Mount drive command: /sbin/mount -t ntfs -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh2' '/mnt/disks/Local_Disk' Mar 10 20:39:53 Pegasus ntfs-3g[28898]: Version 2017.3.23 integrated FUSE 27 Mar 10 20:39:53 Pegasus ntfs-3g[28898]: Mounted /dev/sdh2 (Read-Write, label "Local Disk", NTFS 3.1) Mar 10 20:39:53 Pegasus ntfs-3g[28898]: Cmdline options: rw,noatime,nodiratime,nodev,nosuid,umask=000 Mar 10 20:39:53 Pegasus ntfs-3g[28898]: Mount options: rw,nodiratime,nodev,nosuid,allow_other,nonempty,noatime,default_permissions,fsname=/dev/sdh2,blkdev,blksize=4096 Mar 10 20:39:53 Pegasus ntfs-3g[28898]: Global ownership and permissions enforced, configuration type 1 Mar 10 20:39:53 Pegasus unassigned.devices: Successfully mounted '/dev/sdh2' on '/mnt/disks/Local_Disk'. Mar 10 20:39:53 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'Local_Disk' is not set as sharable and will not be shared... Mar 10 20:39:53 Pegasus unassigned.devices: Adding disk '/dev/sdh3'... Mar 10 20:39:53 Pegasus unassigned.devices: Mount drive command: /sbin/mount -t hfsplus -o force,rw,users,async,umask=000 '/dev/sdh3' '/mnt/disks/UNTITLED' Mar 10 20:39:53 Pegasus unassigned.devices: Successfully mounted '/dev/sdh3' on '/mnt/disks/UNTITLED'. Mar 10 20:39:53 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'UNTITLED' is not set as sharable and will not be shared... Mar 10 20:39:53 Pegasus unassigned.devices: Adding disk '/dev/sdh4'... Mar 10 20:39:53 Pegasus unassigned.devices: Mount drive command: /sbin/mount -t vfat -o auto,async,noatime,nodiratime,nodev,nosuid,umask=000 '/dev/sdh4' '/mnt/disks/WD_My_Passport_259F-part4' Mar 10 20:39:53 Pegasus unassigned.devices: Successfully mounted '/dev/sdh4' on '/mnt/disks/WD_My_Passport_259F-part4'. Mar 10 20:39:53 Pegasus unassigned.devices: Disk with serial 'My_Passport_259F_57584D31414335335A454E43', mountpoint 'WD_My_Passport_259F-part4' is not set as sharable and will not be shared... Mar 10 20:44:10 Pegasus dhcpcd[2581]: br0: adding address 2404:c805:40e8:d300:e5c1:3a9e:4160:1e0d/62 Mar 10 20:44:10 Pegasus dhcpcd[2581]: ipv6_addaddr1: Invalid argument Mar 10 20:53:00 Pegasus dhcpcd[2581]: br0: adding address 2404:c805:40e8:d300:e5c1:3a9e:4160:1e0d/62 Mar 10 20:53:00 Pegasus dhcpcd[2581]: ipv6_addaddr1: Invalid argument Mar 10 20:54:24 Pegasus sshd[32596]: Connection closed by 197.231.193.114 port 38409 [preauth] Mar 10 20:54:38 Pegasus kernel: usb 3-11: USB disconnect, device number 53 Mar 10 20:54:38 Pegasus kernel: sd 11:0:0:0: [sdh] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 Mar 10 20:54:38 Pegasus kernel: sd 11:0:0:0: [sdh] tag#0 CDB: opcode=0x28 28 00 33 aa 15 a8 00 00 f0 00 Mar 10 20:54:38 Pegasus kernel: print_req_error: I/O error, dev sdh, sector 866784680 Mar 10 20:54:38 Pegasus kernel: Buffer I/O error on dev sdh3, logical block 74760373, async page read 1st partition doesn't mount, partitions 2,3,4 do, but then after that the rest of syslog is that error from the 3rd partition. Do you have any dockers using any of those mounts? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.