oncdoc Posted September 20, 2023 Share Posted September 20, 2023 I have 2 same size nvme's I was thinking of putting in zfs for cache. I get an unmountable: unsupported or no file system error. Steps I took: I have formatted the disk that appear unmountable. Removed disk from cachepool. Configured the cachepool for ZFS mirror. Placed the disk back in the cachepool. But keep getting the same error. thanks for your help tower-diagnostics-20230920-1346.zip Quote Link to comment
JorgeB Posted September 21, 2023 Share Posted September 21, 2023 Sep 20 11:44:00 Tower emhttpd: error: put_disk_settings, 4896: Read-only file system (30): fopen: /boot/config/disk.cfg Flash drive is read-only, run chkdsk on it. Quote Link to comment
oncdoc Posted September 21, 2023 Author Share Posted September 21, 2023 (edited) chkdisk below. This USB stick is new 128 gb samsung bar. I had the help of support to transfer the pro key from what I though was a faulty usb. Having said that on first boot I did get a USB read only error. But now its gone. Googling the USB drive I see that Im not the first to have this problem with this particular usb drive. I suspect the mountable drive issues are unrelated. First things first what should I do about the usb drive problem. Should I transfer to a smaller usb stick? Can I still do that. I have used the two quota limit for transfers. Edited September 21, 2023 by oncdoc Quote Link to comment
oncdoc Posted September 21, 2023 Author Share Posted September 21, 2023 (edited) Problems galore: Now Im getting the issue that I had that made me even change the USB stick to the Samsung ! I cannot connect to unraid via the GUI and/or the internet. I tried phone and pc. This is intermittent. I could not have posted the diagnostics above unless I was connected. Its odd. Sometimes the boot sequence works. I see the IP address on the monitor connected to my server. I can ping it. I can see it via the Unifi console. But I get the problem loading page error. When I connect to the GUI, it goes to a blinking cursor on the monitor on the left top. I have deleted the two network files in config then rerun. I have set a fixed ip on the Unifi router. Ive reset the router. Ive changed the port the server is connected to. Im still getting this issue. I think we need to sort this problem out first before the other two ... Edited September 21, 2023 by oncdoc Quote Link to comment
JorgeB Posted September 21, 2023 Share Posted September 21, 2023 Try redoing the flash drive, back up first, re-format and then restore the config folder. Quote Link to comment
oncdoc Posted September 21, 2023 Author Share Posted September 21, 2023 I did as you asked and it has booted and I am able to connect to unraid via windows browser. IP is static address on Unifi. Ive attached diagnostics. My concern is that this successful boot may not be repeatable. Ill wait to hear advice before proceeding. tower-diagnostics-20230921-0828.zip Quote Link to comment
JorgeB Posted September 21, 2023 Share Posted September 21, 2023 Looks OK for now, and the pool mounted. Quote Link to comment
oncdoc Posted September 21, 2023 Author Share Posted September 21, 2023 Unfortunately: Upon reboot ( from the unraid main page) I have the re-connection problem. On the monitor connected to the server there is a blank screen. However, the server is on my network and pingable. Just cant reach it via phone or pc browser. Now I forced a hard shutdown and repowered and Im back in. This cant be healthy. Obviously something is wrong. Im going to need the system to work predictably if Im using it for long term. Here are the diagnostics. Also the NVME drive pair dont mount. tower-diagnostics-20230921-1048.zip Quote Link to comment
Mainfrezzer Posted September 21, 2023 Share Posted September 21, 2023 12 minutes ago, oncdoc said: On the monitor connected to the server there is a blank screen. Youre probably trying to use the Titan X, you need the Nvidia drivers(from the community apps) for the UEFI boot method. Quote Link to comment
JorgeB Posted September 21, 2023 Share Posted September 21, 2023 30 minutes ago, oncdoc said: Also the NVME drive pair dont mount. Yeah, saw wrong before, you have multiple pools, but since the flash drive is no longer read-only it should format now. Regarding the boot problem you can try a new flash drive with a stock install, no key needed, to see if it's a config problem. Quote Link to comment
oncdoc Posted September 21, 2023 Author Share Posted September 21, 2023 the drives did format and mount. I made a new usb stick. Initially, I was able to connect to the server and a got read only USB error again! either way I rebooted via the PC browser and now Unraid is not registering nor pinging. I could try to put the original USB back but Im beginning to suspect its a motherboard NIC problem or USB boot problem? I did install the latest firmware onto the ASUS motherboard but have not updated the drivers. Would it be worth installing windows on the Server and updating all the drivers? I dont know how to update hardware drivers in any other way. Wish I did since installing windows etc is a pain in the you know what. Quote Link to comment
oncdoc Posted September 21, 2023 Author Share Posted September 21, 2023 Alas, I did all that above and still getting intermittent network issues. Everything seemed fine, I rebooted and now cant even ping the server. Although it shows up in the network. Dont know what to do at this point. Quote Link to comment
JorgeB Posted September 22, 2023 Share Posted September 22, 2023 Post new diags when you are not able to ping it. Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 On 9/22/2023 at 2:27 AM, JorgeB said: Post new diags when you are not able to ping it. How do I do that if I can't access the gui to download the diagnostics. Can't even access the gui from monitor connected to the server. I choose the option to boot to gui on start up and screen goes to a blank. Quote Link to comment
Mainfrezzer Posted September 23, 2023 Share Posted September 23, 2023 (edited) 11 minutes ago, oncdoc said: How do I do that if I can't access the gui to download the diagnostics. Can't even access the gui from monitor connected to the server. I choose the option to boot to gui on start up and screen goes to a blank. type "slim" into the console and the gui starts. i miss read that, you probably have no driver installed for your gpu. Try to boot via legacy/bios boot instead of uefi. otherwise always handy to have on hand: you can copy the syslog via commandline via "cp /var/log/syslog /boot/syslog" "diagnostics" places the diagnostic on your flash drive aswell. Edited September 23, 2023 by Mainfrezzer Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 (edited) Hi there. I tried switching boot mode to legacy. There's also an option on the motherboard for legacy or UEFI. I think I'm going to try UEFI only. Weird thing is this is intermittent. How can it be that everything works fine sometimes and then when I reboot I see it rebooting on the monitor and all that stuff comes on the screen. Then I get a blank screen. If I opt to have GUI locally on the monitor, it will also go to the blank screen. Furthermore, I can't access the server via a browser on the PC or phone even with the blank screen. So I think it's more to it than the GPU driver. But hey, you guys are more experienced than me. Edited September 23, 2023 by oncdoc Quote Link to comment
Mainfrezzer Posted September 23, 2023 Share Posted September 23, 2023 (edited) 27 minutes ago, oncdoc said: Hi there. I tried switching boot mode to legacy. There's also an option on the motherboard for legacy or UEFI. I think I'm going to try UEFI only. Weird thing is this is intermittent. How can it be that everything works fine sometimes and then when I reboot I see it rebooting on the monitor and all that stuff comes on the screen. Then I get a blank screen. If I opt to have GUI locally on the monitor, it will also go to the blank screen. Furthermore, I can't access the server via a browser on the PC or phone even with the blank screen. So I think it's more to it than the GPU driver. But hey, you guys are more experienced than me. the screen going blank after a certain time while booting is a nvidia thing and uefi boot. it probably just shows a blinking curser in the top left. For that, as stated, it needs the nvidia plugin. Although probably not the most recent version since im pretty sure the titan x only runs on older drivers. Edit: The recent drivers are fine. Bios/legacy boot should always work to produce an image. The only other reason the screen goes dark is screen saver mode which can be fixed by just typing on the keyboard. If the iGPU is the primary output, it should just work without any hassle, but i dont know how you set up your pc in that regard. But i cant see that the intel igpu would fail to provide an image by default. Edited September 23, 2023 by Mainfrezzer Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 My instinct is that it's not a GPU driver problem. Like I said, I can see on the screen, the startup of the server and sometimes, everything will work perfectly. I will get an IP address and connect to the unraid server. Upon rebooting I will see the system booting but then it will go to a blank screen. And, I cannot access the server via the PC browser or phone browser. It's definitely not a screensaver. I've been pounding on the keyboard trying to make this work!! Perhaps I'll virtualize unraid since even with a fresh USB flash unraid drive. I had the same problems. Proxmox? Quote Link to comment
Mainfrezzer Posted September 23, 2023 Share Posted September 23, 2023 The easy way to finding the culprit would be to switch back to the CMD line mode instead of GUI. Let the server run until the issues appears again and then just use the keyboard, no monitor needed, to log in and type "diagnostics" wait for a couple minutes just to make sure, type "poweroff" and get the diagnostic file from the usb drive. Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 2 hours ago, Mainfrezzer said: The easy way to finding the culprit would be to switch back to the CMD line mode instead of GUI. Let the server run until the issues appears again and then just use the keyboard, no monitor needed, to log in and type "diagnostics" wait for a couple minutes just to make sure, type "poweroff" and get the diagnostic file from the usb drive. How do I anonymize the diagnostics file with this method? Quote Link to comment
Mainfrezzer Posted September 23, 2023 Share Posted September 23, 2023 You can just do it afterwards on your pc. Just unzip it and remove the sensitive information and re-zip it. Its not different as getting it from the "Unraid Website" Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 I got it to work. I have been able to reboot twice in a row with access to the server. what I did. I dont know which one of these steps did the trick but I will list them in case it helps anyone in the future. messed around with boot menu and turned off secure boot. Boot to custom uefi I changed the RAM to xmp as opposed to auto. Turned off asus optimization of the ram. Finally, put the flash in the 2.0 USB slot. Thank you all above who helped. I always learn something from you kind folks. I will report back if problems re-occur. Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 sorry the problem with unmountable file system is back. See post one. Agghhh! I have 2 same size nvme's I was thinking of putting in zfs for cache. I get an unmountable: unsupported or no file system error. Steps I took: I have formatted the disk that appear unmountable. Removed disk from cachepool. Configured the cachepool for ZFS mirror. Placed the disk back in the cachepool. But keep getting the same error. Quote Link to comment
oncdoc Posted September 23, 2023 Author Share Posted September 23, 2023 I have inserted the diagnostics tower-diagnostics-20230923-1400.zip Quote Link to comment
Solution oncdoc Posted September 23, 2023 Author Solution Share Posted September 23, 2023 ok I figured it out. I was getting a pool on one of the drives that would not be formatted. I took out the drive formated it in windows and now everything is fine. 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.