asheenlevrai Posted December 28, 2022 Share #1 Posted December 28, 2022 Hey I just made a USB launcher using TCRP (DS918, using the tutorial from @flyride) for a new machine (bare-metal). Upon 1st boot on the USB dongle, I get the following: Error: symbol 'grub_disk_native_sectors' not found. entering rescue mode... grub rescue > What does that mean? What went wrong? Should I just restart from scratch and try to remake the USB launcher? Thank you very much in advance for your help and advice. Best, -a- Quote Link to comment Share on other sites More sharing options...
rojoone2 Posted December 29, 2022 Share #2 Posted December 29, 2022 (edited) Can you give some information about your “new machine”? You can’t expect to get an answer with so little to go on… or did you solve the issue yourself? Edited December 29, 2022 by rojoone2 1 Quote Link to comment Share on other sites More sharing options...
asheenlevrai Posted December 29, 2022 Author Share #3 Posted December 29, 2022 (edited) 8 hours ago, rojoone2 said: Can you give some information about your “new machine”? You can’t expect to get an answer with so little to go on… or did you solve the issue yourself? Thanks a lot 🙏 Sorry for not having provided the necessary information. (I haven't solved this yet) Do you know what can cause this type of error message? The specs of the new machine are: - i7 3770 - 16GB DDR3 1333 (4x4GB) - Asus P8Z77-M uATX MB (z77 express chipset). BIOS v2203 - 7x 1TB sATA3 HDD (Seagate Barracuda). 2 on MB sATA3 ports (4 sATA2 ports free, unused), the 5 others are on a 5-ports sATA3 AIC (see below) - 5-ports sATA3 PCIe3.0 x4 controller (Chipset: JMicron JMB585) - 450W PSU (xilence) Please let me know if there is any information that I failed to provide. Thanks again 🙏 -a- Edited December 29, 2022 by asheenlevrai Quote Link to comment Share on other sites More sharing options...
rojoone2 Posted December 29, 2022 Share #4 Posted December 29, 2022 The only time I got a error like that was when I used the wrong image for my boot setting on an old board with an Atom CPU. I made a UEFI boot disk when I needed a BIOS/Legacy boot disk. But it looks like the BIOS on your board can be set either way. Make sure you are using the right image file for your boot setting. 1 Quote Link to comment Share on other sites More sharing options...
asheenlevrai Posted December 29, 2022 Author Share #5 Posted December 29, 2022 Thanks @rojoone2 🙏 I used this image file for TCRP: https://github.com/pocopico/tinycore-redpill/releases/download/v0.9.3.0/tinycore-redpill-uefi.v0.9.3.0.img.gz Quote Link to comment Share on other sites More sharing options...
asheenlevrai Posted December 30, 2022 Author Share #6 Posted December 30, 2022 (edited) 14 hours ago, asheenlevrai said: Thanks a lot 🙏 Sorry for not having provided the necessary information. (I haven't solved this yet) Do you know what can cause this type of error message? The specs of the new machine are: - i7 3770 - 16GB DDR3 1333 (4x4GB) - Asus P8Z77-M uATX MB (z77 express chipset). BIOS v2203 - 7x 1TB sATA3 HDD (Seagate Barracuda). 2 on MB sATA3 ports (4 sATA2 ports free, unused), the 5 others are on a 5-ports sATA3 AIC (see below) - 5-ports sATA3 PCIe3.0 x4 controller (Chipset: JMicron JMB585) - 450W PSU (xilence) Please let me know if there is any information that I failed to provide. Thanks again 🙏 -a- oh.... My CPU is not Haswell (4th gen). It's 3rd gen. I should chose DS3622xs+ instead of DS918+ 🤦♂️ Edited December 30, 2022 by asheenlevrai Quote Link to comment Share on other sites More sharing options...
asheenlevrai Posted December 30, 2022 Author Share #7 Posted December 30, 2022 21 minutes ago, asheenlevrai said: oh.... My CPU is not Haswell (4th gen). It's 3rd gen. I should chose DS3622xs+ instead of DS918+ 🤦♂️ nope... same issue when using DS3622xs+ Quote Link to comment Share on other sites More sharing options...
asheenlevrai Posted December 30, 2022 Author Share #8 Posted December 30, 2022 12 hours ago, rojoone2 said: (...) Make sure you are using the right image file for your boot setting. Thanks a lot @rojoone2! 🙏 For some reason the PC was booting in legacy mode instead of UEFI. Changing this setting in BIOS fixed the problem Quote Link to comment Share on other sites More sharing options...
asheenlevrai Posted December 30, 2022 Author Share #9 Posted December 30, 2022 Any way I could mark this thread as [solved]? Quote Link to comment Share on other sites More sharing options...
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.