PartialVolume
Ventoy boots to menu but on selecting ShredOS .img file on a legacy only system you end up at the grub prompt. Works on UEFI & .iso
Hello! Every time I attempt to use the 0.34 shredos .iso file on the latest version of Ventoy, I get kernel errors on boot. And every time I try to use the latest shredOS .img file on Ventoy, it drops me into the Grub command line; it doesn't even boot. I have tried Ventoy with Secureboot enabled and disabled, and Ventoy on GPT and MBR. The same error still occurs. The .img file will drop me into the Grub cli, and the .iso will have kernel errors on boot, which causes it to freeze and never boot. I've tried this on multiple different USB sticks, one 64GB and another 128GB one. The same error happens on different USB sticks. I have also tried different computers to boot it on; the same errors appear on all computers. I've also tried older versions of both ventory and shredos. No luck.
ShredOS is advertised on both the Ventoy and ShredOS repo to be compatible with each other. I couldn't find anyone else having the same issue as me.
This is what happens when using the latest ShredOS img file on Ventoy:
This is what happens when using 0.34 ShredOS iso file Ventory:
Can you try booting an alternate Linux live usb or iso and assuming it boots successfully run the command lspci. Take a photo on your phone and post here. .this will display a list of hardware on your system.
Please check my issue also. https://github.com/Master-Koy/-Boot-Error-Stuck-at-Boot-in-Kali-Linux-in-Vmware
This isn't a ShredOS issue... You should ask in a Kali forum. But having said that recovering from a aborted apt upgrade I would use sudo dpkg --configure -a to restart the upgrade. But like I say this place is for ShredOS issues not general Linux issues.
I get exactly the same as juncture6825's pictures when I try to boot v2023.08.2_25.0_x86-64_0.35
Can you try booting an alternate Linux live usb or iso and assuming it boots successfully run the command lspci. Take a photo on your phone and post here. .this will display a list of hardware on your system.
I have attached a screenshot of lspci running Finnix on Ventoy. It's important to note that, ShredOS works fine on a usb drive written with rufus (same computer). And all other operating systems work fine on Ventoy.
@Binary-Bear To diagnose the issue I need you to produce the output of lspci just as @juncture6825 has done above so I can compared the two.
Please check my issue also. https://github.com/Master-Koy/-Boot-Error-Stuck-at-Boot-in-Kali-Linux-in-Vmware
This isn't a ShredOS issue... You should ask in a Kali forum. But having said that recovering from a aborted apt upgrade I would use
sudo dpkg --configure -ato restart the upgrade. But like I say this place is for ShredOS issues not general Linux issues.I understand what you mean to say. Really appreciate you. Can you please tell a few things before I leave.
I'm unable to login so how can I use the command which you mentioned....?
Normally, if you're lucky the Linux virtual terminals would be available ALT F2, ALT F3 etc and you would login via a terminal then run the command but you are running in vmware so whether that works depends on whether the ALT F2 keys are mapped and therefore work. I don't use or know anything about vmware so you are better off asking in the vmware forums. Sorry.
Sorry this is taking me a long time I am trying to find a Linux.iso so I can do lspci.
Just tried tinycore but when I type lspci in terminal it says "command not found"
I have got stuck when trying to mount a flash drive to save the output to.
My flash drive is sdc
sudo mount /dev/sdc /store
I get an error.
mount.nilfs2: Error while mounting /dev/sdc on /store: Invalid argument
Before anyone suggests it I don't have a smart phone or a digital camera
Done it! ... I am going for a rest after this LOL.
00:00.0 RAM memory: NVIDIA Corporation MCP78S [GeForce 8200] Memory Controller (rev a2) 00:01.0 ISA bridge: NVIDIA Corporation MCP78S [GeForce 8200] LPC Bridge (rev a2) 00:01.1 SMBus: NVIDIA Corporation MCP78S [GeForce 8200] SMBus (rev a1) 00:01.2 RAM memory: NVIDIA Corporation MCP78S [GeForce 8200] Memory Controller (rev a1) 00:01.4 RAM memory: NVIDIA Corporation MCP78S [GeForce 8200] Memory Controller (rev a1) 00:02.0 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1) 00:02.1 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1) 00:04.0 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] OHCI USB 1.1 Controller (rev a1) 00:04.1 USB controller: NVIDIA Corporation MCP78S [GeForce 8200] EHCI USB 2.0 Controller (rev a1) 00:06.0 IDE interface: NVIDIA Corporation MCP78S [GeForce 8200] IDE (rev a1) 00:07.0 Audio device: NVIDIA Corporation MCP72XE/MCP72P/MCP78U/MCP78S High Definition Audio (rev a1) 00:08.0 PCI bridge: NVIDIA Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1) 00:09.0 IDE interface: NVIDIA Corporation MCP78S [GeForce 8200] SATA Controller (non-AHCI mode) (rev a2) 00:10.0 PCI bridge: NVIDIA Corporation MCP78S [GeForce 8200] PCI Express Bridge (rev a1) 00:14.0 PCI bridge: NVIDIA Corporation MCP78S [GeForce 8200] PCI Bridge (rev a1) 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor HyperTransport Configuration 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Address Map 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor DRAM Controller 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Miscellaneous Control 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 10h Processor Link Control 01:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 IEEE-1394a-2000 Controller (PHY/Link) 02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Cypress XT [Radeon HD 5870] 02:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Cypress HDMI Audio [Radeon HD 5830/5850/5870 / 6850/6870 Rebrand] 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 02)
I have got stuck when trying to mount a flash drive to save the output >to. My flash drive is sdc
sudo mount /dev/sdc /store
I get an error.
mount.nilfs2: Error while mounting /dev/sdc on /store: Invalid >argument
Just for reference, that command failed because the partition number is missing.
It should've been sudo mount /dev/sdc1 /store
@Binary-Bear Your system appears to have an Nvidia embedded graphics co processor chipset as well as a AMD graphics system on a card. Can you confirm whether this the case. Is there a plug in graphics card and also a VGA connector that's mounted on the motherboard?
@Binary-Bear Your system appears to have an Nvidia embedded graphics co processor chipset as well as a AMD graphics system on a card. Can you confirm whether this the case. Is there a plug in graphics card and also a VGA connector that's mounted on the motherboard?
Forget the comment above, I just checked the motherboard spec and it doesn't provide a on board video graphics just the Nvidia co processor. You do both run a similar graphics card though AMD Cedar and Cypress. I wonder if there is something wrong with the driver for those graphics.
Just for reference, that command failed because the partition number is missing.
LOL Yes thank you, I learned the hard way!
I hope you can solve the problems we are having, I feel left out not having the latest version of shredos.
@Binary-Bear I'm just double checking a couple of things, I'm not sure whether we discussed this.
- I believe you are connecting your monitor via VGA. Is that correct? Or is it DVI or display port?
- When you edited grub.cfg did you edit both grub files or only one. Do you know whether your system boots legacy & UEFI or just one or the other.
I believe you are connecting your monitor via VGA. Is that correct? Or is it DVI or display port?
I connect to DVI via an adaptor to VGA cable.
This is a picture of the connector (one of the two red sockets)
When you edited grub.cfg did you edit both grub files or only one.
For the purpose of testing I am only using default .iso and .img with no modifications.
Do you know whether your system boots legacy & UEFI or just one or the other.
Legacy BIOS only the main-board is about 12 years old I think.
I thought 0.35 was working if you used Rufus to create the stick, apart from it being slow to load eventually it got there. Is that correct?
Yes 0.35 does work using Rufus albeit slow booting. Sorry, my comment about not having the latest version of shredos is referring to it not being on my boot (Ventoy/Yumi) flash drive.
I thought 0.35 was working if you used Rufus to create the stick, apart from it being slow to load eventually it got there. Is that correct?
0.35 and 0.34 both work completely fine when using Rufus. Neither work on Ventory even though they are advertised to work on Ventory. I don't understand why...?
@Binary-Bear Just to clarify a few more things so I understand it better. You mention Ventoy/Yumi which is basically a yumi front end that pulls in Ventoy. Have you tried using Ventoy 1.0.97 direct from the Ventoy page rather than using yumi. Just wondered if that worked. I use Ventoy Linux download direct from Ventoy
@juncture6825 Similar question, I assume Ventory is a typo. Are you using Ventoy direct from the Ventoy website. And are you using the Linux Ventoy download or the Windows Ventoy download?
@Binary-Bear Just to clarify a few more things so I understand it better. You mention Ventoy/Yumi which is basically a yumi front end that pulls in Ventoy. Have you tried using Ventoy 1.0.97 direct from the Ventoy page rather than using yumi. Just wondered if that worked. I use Ventoy Linux download direct from Ventoy
I normally use Ventoy/Yumi but since the release of ventoy-1.0.97-windows.zip yesterday I have just used Ventoy with the same results.
ventoy-1.0.97-windows.zip SHA256 = 44fb53f26872c6304e1cb3d47b65d0613665666100c48deeee4cd87901fb500f
@Binary-Bear When you copy the shredos .img file onto the Ventoy stick do you copy it into the root directory or do you copy it into a sub folder that you create?
@Binary-Bear When you copy the shredos .img file onto the Ventoy stick do you copy it into the root directory or do you copy it into a sub folder that you create?
Ignore that last question, I just tested Ventoy and ShredOS works even if I put the .img file in a sub folder off root. It still appears in the Ventoy boot menu and it works without any problems, at least on my system
@juncture6825 Similar question, I assume Ventory is a typo. Are you using Ventoy direct from the Ventoy website. And are you using the Linux Ventoy download or the Windows Ventoy download?
Hello! Yes sorry, Ventory was a typo. I mean Ventoy. I installed Ventoy from the official website that you linked, no forks no nothing. I set my Ventoy USB stick up on a Windows 11 22H2 computer, so yes the Windows version of Ventoy.
ShredOS worked in Ventoy for me
Did you use Ventoy Windows 10, 11 or Linux? What ISO/IMG file of ShredOS? Did you do anything specifically?
Same issue.
Tried some version from 2021 august and it failed, updated to latest shredOS, issue still persists. Im going to do as others said and put it on its own drive but this sucks. Please fix
