Advertising
Welcome to SparkyLinux forums
Zapraszamy również na polsko-języczne Forum https://forum.linuxiarze.pl
Quote from: duststuff on March 25, 2024, 03:47:31 AMDoes the drive itself and/or your BIOS have any sort of security / passwords set / active? I think TPM (Trusted Platform Module) can also be an issue. And perhaps whether you are booting the UFD in legacy or UEFI mode. Disabling the fast startup in Windows may also help. Have you confirmed that the live Sparky UFD you're trying to use is bootable? That would also be worth confirming. A lot of these ideas I've just gotten from a quick online search on some key words related to this topic. Dual-booting Linux and Windows can be pretty tricky as there are multiple variables / settings and not all systems are the same, so sometimes you have to do some trial-and-error to figure things out. But I'm guessing it's highly likely this is not something specific to Sparky Linux. I think your specific target for trouble-shooting at this point is trying to figure out what is blocking access to your hard drive -- if you can figure that out, then that should help you figure out next steps. That's about all the ideas I can think of. Hope you'll be able to figure something out.
Quote from: duststuff on March 25, 2024, 01:17:18 AMIt looks like the I/O errors are for device 'sda', so you'll probably first want to confirm what device that is referring to. I'm assuming it's likely that it is the drive where you are attempting to do the dual-boot. Also, you didn't mention this, but I'm assuming the errors you're getting are during the process of trying to boot a live Sparky USB flash drive (UFD) so that you can install Sparky from there. I don't know a lot about Windows 10 and Bitlocker, but I'm assuming you're getting the errors because Bitlocker is enabled as you mentioned. If it is set up to encrypt your drive and require a password to get access to the drive, then it would make perfect sense to me that it's not going to allow anything / anyone else to access the drive, thus giving you the READ / I/O errors. If all of the above is true, then probably the next thing I would look at if I were you is how to disable Bitlocker and see if that helps. I'm not sure if it's possible to have a Linux / Windows dual-boot setup if someone wants to use Bitlocker with Windows, but I'm guessing one or more online searches on these topics would provide some helpful information. Hope some of these thoughts help and you'll figure out something that works for you.
No installable version of the k3b package was found, although an entry exists in the database.
This usually indicates that the package was mentioned as a dependency but was never uploaded, that it is out of date, or that the corresponding repository is missing from Settings → Repositories.
deb http://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian/ trixie main contrib non-free non-free-firmware
deb http://security.debian.org/debian-security/ trixie-security/updates main contrib non-free non-free-firmware
deb-src http://security.debian.org/debian-security/ trixie-security/updates main contrib non-free non-free-firmware
deb http://deb.debian.org/debian/ trixie-updates main contrib non-free non-free-firmware
deb-src http://deb.debian.org/debian/ trixie-updates main contrib non-free non-free-firmware
deb http://deb-multimedia.org/ trixie main non-free