LeGreatMaxiking Posted January 28, 2020 Share Posted January 28, 2020 Hey Guys. I have a problem: I can´t reboot my NAS. I´m tried to passthrough my 1660 super to the windows vm. After one reboot the VM Tab was blank and stuck, and I just wanted to reboot again to check if something repairs by itself. I tried to kill all open processes but can´t find the problem and also can´t get to the NAS in the next 2 days, so I have to reboot it from command line - which is still working. Web GUI isn´t working at all. Thanks in advance Max Quote Link to comment
Frank1940 Posted January 28, 2020 Share Posted January 28, 2020 Try typing diagnostics from the command line. diagnostics That should write the Diagnostics file to the /boot/logs directory on the server's Linux file system (and the logs folder/directory on the flash drive if you are looking for it from the outside world.). Upload that file with your next post. 1 Quote Link to comment
LeGreatMaxiking Posted January 28, 2020 Author Share Posted January 28, 2020 Hi! Thanks in advance. maxisnas-diagnostics-20200128-2229.zip Quote Link to comment
JorgeB Posted January 29, 2020 Share Posted January 29, 2020 Cache1 SSD has issues, and looks like an actual SSD problem: Jan 28 19:00:49 MaxisNAS kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 866, flush 0, corrupt 0, gen 0 Jan 28 19:00:49 MaxisNAS kernel: BTRFS error (device sdk1): bdev /dev/sdk1 errs: wr 0, rd 867, flush 0, corrupt 0, gen 0 Jan 28 19:00:49 MaxisNAS kernel: ata5: EH complete Jan 28 19:00:49 MaxisNAS kernel: ata5.00: exception Emask 0x0 SAct 0x1fff0 SErr 0x0 action 0x0 Jan 28 19:00:49 MaxisNAS kernel: ata5.00: irq_stat 0x40000008 Jan 28 19:00:49 MaxisNAS kernel: ata5.00: failed command: READ FPDMA QUEUED Jan 28 19:00:49 MaxisNAS kernel: ata5.00: cmd 60/08:30:80:ae:1c/00:00:1a:00:00/40 tag 6 ncq dma 4096 in Jan 28 19:00:49 MaxisNAS kernel: res 41/40:08:80:ae:1c/00:00:1a:00:00/00 Emask 0x409 (media error) <F> Jan 28 19:00:49 MaxisNAS kernel: ata5.00: status: { DRDY ERR } Jan 28 19:00:49 MaxisNAS kernel: ata5.00: error: { UNC } Jan 28 19:00:49 MaxisNAS kernel: ata5.00: supports DRM functions and may not be fully accessible 1 Quote Link to comment
LeGreatMaxiking Posted January 29, 2020 Author Share Posted January 29, 2020 ah ok. I have an old SSD inside as cache and also 2 2TB SSDs i wanted to copy the data from the old ssd to the new one, but i can´t find any option for that. Can I just remove the OLD SSD (its just a 250 GB) and Unraid will rebbuild the cache? Or do I have to do someting manually? Do i have to manually poweroff the device, or is there any way for me to remote reboot ? Quote Link to comment
JorgeB Posted January 29, 2020 Share Posted January 29, 2020 Current cache pool is a mess: Data Data Metadata System System Id Path single RAID1 RAID1 single RAID1 Unallocated -- --------- -------- --------- -------- -------- --------- ----------- 1 missing - 91.97GiB 1.00GiB - 32.00MiB -93.00GiB 3 /dev/sdk1 45.06GiB 181.76GiB 1.00GiB 32.00MiB 32.00MiB 5.00GiB 4 missing - 85.00GiB - - - -85.00GiB 5 /dev/sdj1 - 688.79GiB 1.00GiB - - 1.15TiB 6 /dev/sdi1 - 684.00GiB 1.00GiB - - 1.15TiB -- --------- -------- --------- -------- -------- --------- ----------- Total 45.06GiB 865.76GiB 2.00GiB 32.00MiB 32.00MiB 2.13TiB Used 29.10GiB 783.93GiB 1.19GiB 0.00B 160.00KiB You have one failing device, two missing devices, part of the data is raid1, another part is single profile, best bet would be to try and backup any important data still on cache and re-format the pool with remaining good devices. 1 Quote Link to comment
LeGreatMaxiking Posted January 29, 2020 Author Share Posted January 29, 2020 Yea i thought of this. So im gonna reboot manually and ginna copy all my important media off my cache. So still no reboot from terminal possuble? Quote Link to comment
JorgeB Posted January 29, 2020 Share Posted January 29, 2020 Type reboot if it doesn't work after a few minutes you'll need to force it. Quote Link to comment
itimpi Posted January 29, 2020 Share Posted January 29, 2020 4 minutes ago, LeGreatMaxiking said: So still no reboot from terminal possuble? Are you saying the 'reboot' command from terminal is now not working? 1 Quote Link to comment
LeGreatMaxiking Posted January 29, 2020 Author Share Posted January 29, 2020 Yes tried it via putty. I can do diagnostics, but not reboot. Quote Link to comment
LeGreatMaxiking Posted January 29, 2020 Author Share Posted January 29, 2020 Its stuck like this since yesterday. I tried to kill some processes, didnt help at all Quote Link to comment
LeGreatMaxiking Posted January 29, 2020 Author Share Posted January 29, 2020 One more questions guys: Mover is working, but quite slow. Just abput 5MB/s. I wanted to use UnBalance. But the option "Dry Run" is ticked and i cant untick that, as it is greyed out. Quote Link to comment
JorgeB Posted January 29, 2020 Share Posted January 29, 2020 28 minutes ago, LeGreatMaxiking said: I wanted to use UnBalance. But the option "Dry Run" is ticked and i cant untick that, as it is greyed out. Best to post in the Unbalance support thread. 1 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.