• 0 Posts
  • 63 Comments
Joined 3 years ago
Cake day: July 4th, 2023
  • mvirts@lemmy.worldtoLinux@lemmy.ml•[SOLVED ]My Linux won't boot anymore because it can't find the boot drive?
    2·
    15 days ago

    Afaik, those by-* paths are symlinks created by udev during boot (before switching to the real root fs) The kernel creates the actual device files directly in /dev. My guess is that Windows left an NTFS volume in an unmountable state or something and udev got stuck processing this disk before processing rules for your boot disk. This probably requires you to have a fstab entry for mounting your windows disk, but I’m not sure.

    When you boot into a live distro again (I know you’re done, but maybe someone else has this problem) check if the disk has a block device file directly in /dev. Maybe check the other disk, see if you can mount it or remove references to it in fstab or unplug the device entirely.

  • mvirts@lemmy.worldtoLinux@lemmy.ml•Wiping Windows at last but how?
    1·
    1 month ago

    The easy thing is to just format them ext4 and use them as extra data storage.

    Edit 2: don’t delete the efi partition!!! Move that just like your system partition. Unless you want to learn how to rebuild it :) unless you’re using Windows boot manager you can remove the Microsoft folder from the efi partition as well

    The good news is your system partition is small so you can delete the first two partitions. Make a small boot partition if you want, make a new system partition second ( bigger than your current one), copy the existing system partition into the new one (without deleting the old one), boot into the new system partition, test that it works, then expand the fs to fill the partition. Then you can move your home partition if you want or just make your system partition huge to fill the space up to your existing home partition, then delete the last partitions an grow your home partition to fill the disk

    Edit: once you know the new system partition works you delete the old one.

  • mvirts@lemmy.worldtoLinux@lemmy.ml•How do I recover data from a BTRFS Fedora partition if live images do not "see" the disk?
    41·
    1 month ago

    I’m a btrfs noob, so I’m skipping any tools that may fix the disk, try those first.

    If the media isn’t dying, try a file carving tool like photorec. Idk if testdisk supports btrfs but it’s worth a try, it’s my go-to for undelete and finding lost partitions.

    Edit: missed most of your post. First you need to check the kernel logs using the dmesg command. Look for errors that may explain why the disk doesn’t show up, especially if it lists scsi or sata in the message.

    Edit again: you may want to check the disk’s self reported heath using “smart” data. Many bios menus show this info, and there are programs to get it on Linux. If there are too many read or write errors, you need to decide how important the data is. Professional recovery can probably get all of your data if you stop using the drive now and send it in. DIY recovery using a file carving tool would work best if you have another disk to make an image of the failing one with. ddrescue would be the tool for the job to create the image. If you don’t have another disk large enough, and the files aren’t super important, you can run file carving on the failing disk directly, but the more you use it the greater chance the disk will corrupt more data.

  • mvirts@lemmy.worldtoLinux@lemmy.ml•How to connect to local private network?
    5·
    5 months ago

    If you can see how the other machines on the network access the drives, like with net use in the windows command prompt, then you will know the protocol and address and share name to connect to.

    If it’s something like \\computername\a\path\here that’s a windows file share which you can connect to with samba. On modern Linux desktop systems you can sometimes get away with opening a file browser and typing in a location like smb://computername/a/path/here and it may just work

    Keep in mind computername could be an IP address instead, and some file browsers are sneaky about letting you type in a path (nautilus/gnome, which I think is Ctrl+L) if smb://… Doesn’t work smbfs:// may be worth a try

  • mvirts@lemmy.worldtoLinux@lemmy.ml•Looking for an OS that I can plug in to any (Android) phone and run it.
    1·
    5 months ago

    I don’t know of any project to do this, but it’s an interesting idea.

    For most/all phones, you would need to break the phone’s software security to boot another OS. To boot via USB the phone’s firmware would need to support that, or a sufficient USB vulnerability could be used to take over a running system and boot into a new OS. This would almost certainly be unreliable and only work on specific devices.

    Note that if part of your goal is to extract data from the phone, only old phones store data unencrypted these days. One advantage of using a vulnerability to hijack the current os would be the availability of the keys to decrypt the phone’s storage if the storage is already unlocked.

    Although it’s not as interesting, you certainly can load firmware on an android device that will boot from USB. Not sure if this already exists or would need to be built.