January 4, 20215 yr Author FWIW - here’s the boot drive contents.... root@unRAID:/boot# ls -la total 321784 drwx------ 9 root root 4096 Dec 31 1969 ./ drwxr-xr-x 20 root root 420 Jan 3 13:22 ../ drwx------ 3 root root 4096 Jan 29 2019 EFI-/ -rw------- 1 root root 4096 Jan 1 1980 FSCK0000.REC -rw------- 1 root root 4096 Jan 1 1980 FSCK0001.REC drwx------ 2 root root 4096 Jan 29 2019 System\ Volume\ Information/ -rw------- 1 root root 7491584 May 10 2020 bzfirmware -rw------- 1 root root 65 Mar 5 2020 bzfirmware.sha256 -rw------- 1 root root 4686496 May 10 2020 bzimage -rw------- 1 root root 65 Mar 5 2020 bzimage.sha256 -rw------- 1 root root 23744512 May 10 2020 bzmodules -rw------- 1 root root 65 Mar 5 2020 bzmodules.sha256 -rw------- 1 root root 221877160 May 10 2020 bzroot -rw------- 1 root root 71225996 May 10 2020 bzroot-gui -rw------- 1 root root 65 Mar 5 2020 bzroot-gui.sha256 -rw------- 1 root root 65 Mar 5 2020 bzroot.sha256 -rw------- 1 root root 18747 Mar 5 2020 changes.txt drwx------ 9 root root 4096 Jan 3 15:09 config/ -r-------- 1 root root 122308 Jan 29 2019 ldlinux.c32 -r-------- 1 root root 69632 Jan 29 2019 ldlinux.sys -rw------- 1 root root 7975 Mar 5 2020 license.txt drwx------ 2 root root 8192 Jan 3 09:49 logs/ -rw------- 1 root root 1760 Mar 5 2020 make_bootable.bat -rw------- 1 root root 3291 Mar 5 2020 make_bootable_linux -rw------- 1 root root 2428 Mar 5 2020 make_bootable_mac -rw------- 1 root root 150024 Mar 5 2020 memtest drwx------ 2 root root 4096 Feb 4 2019 preclear_reports/ drwx------ 2 root root 4096 Mar 16 2020 previous/ -rw------- 1 root root 14322 Jan 29 2019 readvz drwx------ 2 root root 4096 Dec 16 2019 syslinux/ -rw------- 1 root root 492 Mar 5 2020 syslinux.cfg- root@unRAID:/boot#
January 4, 20215 yr Community Expert It's not really clear to me that sr0 is the flash drive, but it shows up in smart folder of your diagnostics with the same identifier as flash. Is there something else in your hardware that might correspond to, such as a DOM? What else can you tell us about your hardware?
January 4, 20215 yr Author I'm not sure what DOM is but this is from /dev folder. I have a DVD drive which was connected long ago but is currently only connected by power cable as I'm out of SATA cables so I can't imagine it could detect that? brw-rw---- 1 root cdrom 11, 0 Jan 3 13:03 sr0 root@unRAID:/dev#
January 4, 20215 yr Community Expert 12 hours ago, trurl said: What else can you tell us about your hardware? 1 hour ago, bugsysiegals said: I'm not sure what DOM is For example, some other NAS systems use DOM (disk on module) similar to the way Unraid uses flash, to boot the OS from. If you have converted some other NAS to Unraid you might have a DOM. Probably sr0 showing up in diagnostics smart folder with the same id as your flash drive isn't really the issue and may just be an artifact of collecting diagnostics. That device does have errors in syslog but from what I saw earlier not enough to fill logs. How is your log space now?
January 4, 20215 yr Author My computer was brand new and is as follows below. The log is still at 1% so maybe xfs_repair on the cache resolved but I also stopped running my W10 Gaming VM because I get ~100 FPS whereas I get 300+ on bare metal. I dislike having to shut down unRAID to dual boot since I loose my security cams but it is what is ... MB - Rog Strix B450F Gaming CPU - Ryzen 2600X RAM - 2x 16GB @ 2133Mhz PSU - SeaSonic X-850 Gold GPU - EVGA GeForce 1650 Super CD/DVD - N/A USB 1 - Atolla USB 3.0 Hub HDD's Array Parity - Western Digital EasyStore 8TB (sdg) Disk 1 - Western Digital EasyStore 8TB (sdb) Disk 2 - Western Digital EasyStore 8TB (sdc) Cache Drives Samsung SSD 860 EVO 500GB (sde) Boot Device SanDisk Cruzer 4 GB (sda) Unassigned Devices Samsung SSD 840 EVO 250GB (was passed through to Windows Gaming VM but FPS is 30% of bare metal, even though it shows PCIe x16, so is now used to dual boot W10 unfortunately) WD Purple 4TB Surveillance Hard Disk Drive WD40PURZ (passed through to Windows VM for recording security cameras) Edited January 4, 20215 yr by bugsysiegals
January 4, 20215 yr Author I booted back into the BIOS so I could share what I see. I've attached the image showing the two bootable items from my flash drive, one of which matches closely to sr0 (95/96MB). I then seen only the 95MB item showing under CD / DVD ROM Drive BBS Priorities which was selected. I disabled it and then see it shows "disabled in BBS Order" for Boot Option #1. I'm not sure what all this is but I've selected the 3835MB item for Boot Option # 1 and disabled for all other Boot Options and BBS Priorities. I've also re-uploaded the diagnostics.zip for reference since I'm not sure where you seen all the sr0 errors. unraid-diagnostics-20210104-1312.zip Edited January 4, 20215 yr by bugsysiegals
January 5, 20215 yr Author 15 hours ago, jonathanm said: Google "remove U3 sandisk" Good catch!! I've removed the U3 software which removed the 95MB bootable item from the BIOS but unfortunately can no longer boot the drive. All the files are there but I receive a Boot Error message. I see there's a "make bootable.bat" but didn't want to run it as administrator before checking here ... please advise. Also, I've read I should avoid booting unRAID UEFI ... is this correct that I should avoid and will it have any affect on my Docker/VM performance? Edited January 5, 20215 yr by bugsysiegals
January 5, 20215 yr Community Expert Just backup the config folder from flash, prepare it as a new install, copy the config folder back. UEFI is preferred if it works for you otherwise legacy.
January 5, 20215 yr Author I read make bootable wouldn't hurt the configuration files so I tried it and it worked! I no longer see the sr0 drive showing up and log has been 1%. It seems it should be good to go other than my Gaming VM performance which I'll open a new thread for. Thanks guys! Diagnostic files again for reference ... unraid-diagnostics-20210105-1034.zip
Archived
This topic is now archived and is closed to further replies.