I have a Raspberry Pi sd card that I'd really hoping I can get files off. I the sd card mounts in my Mac and I have a boot0 and RECOVERY under in the Mac devices menu. I can navigate the sd content on my Mac.
When I try to boot up the RPi with the sd card I get part way through the boot process then a flood of not normal text. Then it ends with "Fixing recursive fault but reboot in needed!" I had this twice now and the first time i waited about 5 minutes before shutting down. This time I am leaving it for about 30 minutes in hopes that another message comes up and it says Fixed or something else.
If I can navigate the card on my Mac what should I do next assuming it is not going to boot? Can I get to files on my Desktop? It is one folder in particular I would love to recover.
The RPi is a 2 version B.
I am not sure why this is not more documented but I found a solution. I have Googled for a hour easy trying to find a solution and literally looked at 100 sites of what other did. Nothing worked for me.
Here is what I ended up doing. I have another RPi around so I booted that up. Inserted the sd can into a reader. plugged the reader into the other RPi and boom! I have full access to the file system. I accessed my Desktop folder and the www folder. Moved the files over for what I needed to recover.
This was crazy easy so I sure hope other find this post and try this first before all the crazy instructions out there.
Related
So I booted Parrot OS from an external drive (SanDisk 3.2Gen1) and I gave it 32GB of persistence (I don't know if it really does anything to help). Now I am trying to partition the drive. Everything goes well untill i try to install it to the drive. It just pops this error and I don't know what to do next.
Error image
I have tried to do it with the GParted program but that doesn't work either.
Looks like you are trying to partition the drive the live system runs on?
If so, try booting from another drive than the one you'd like to partition.
I've looked around a lot at many people's different questions and can't find one that is the same situation as the problem I'm having. Essentially a friend brought me an old PC of theirs with the request that there are some files they want taken off the hard drive. Unfortunately, their version of Windows had corrupted, so my solution was to boot Ubuntu from a USB drive without affecting the hard drive, to access the files and then the computer is going to scrap anyway. Unfortunately, as soon as the ubuntu software starts to load the lights on the keyboard and mouse turn off and when I eventually get to the option of 'Try Ubuntu', neither are responsive. I've tried restarting, I've tried different ports, I've tried unplugging and plugging back in, I've tried a different keyboard and mouse but I cannot find a solution. I installed the latest version of ubuntu from their website. I can use the keyboard in the BIOS settings etc. Anyone know what is happening? All help is greatly appreciated.
Long story short, windows 10 is utterly broken on my laptop after it automatically installed some updates. It's now stuck in a loop which always ends up saying "Undoing changes made to your computer"
I can't get into the BIOS.
I can't get into the Windows Recovery Environment.
Been talking to MS support for far too long so far, so I'm wondering if it's possible to add it as a secondary disk drive to another machine that does work, and manually remove any updates that were installed directly through the filesystem?
The only solution MS were willing to offer was to format the whole drive and re-install windows.
When I moved the HDD into a working windows 7 machine it actually prompted a chkdsk to run over the disk.
It found a whole load of orphaned files, not sure if that was really the cause, but after backing up as many files as I had access to, I put the drive back into the other machine and now it boots.
tl;dr, chkdsk fixed it.
I was stuck in this loop last night
machine configuration : Dell Inspiron
windows 10 (original)
What the one thing you can do is to use an application name Dell usb recovery tool. You will have to format you whole computer be it c:// or any other. You will need an extra hard drive to make a backup.
the process goes like this.
You will have to install the above application on other computer and open it and fill your service tag and make that pen drive bootable with that application.
Now plug in that pen drive to the laptop.
Go for troubleshoot.
Repair.
Install new original os.
It will ask for backup make a backup to other HDD.
Install and recover your backup.
I want to replicate a feature that exists on Windows To Go solution into Ubuntu Linux (https://technet.microsoft.com/en-us/library/jj592680.aspx#wtg_faq_surprise)
If the Windows To Go drive is removed, the computer will freeze and the user will have 60 seconds to reinsert the Windows To Go drive. If the Windows To Go drive is reinserted into the same port it was removed from, Windows will resume at the point where the drive was removed. If the USB drive is not reinserted, or is reinserted into a different port, the host computer will turn off after 60 seconds.
This means: I run Linux on an USB Stick, and I want it to freeze if I accidentally unplug the USB. And if I reconnect it, Linux will detect it and return to work. Can anyone point some directions to perform that?
Thanks in advance!
I am guessing thats going to be more difficult then you think, the linux kernel and other systems need to know to not panic when it happens. Windows is probably set up better for boot drive failure.
I'd like to find a way to make my BeagleBone (white) Rev A6a autologin after being powered up. I'm using Angstrom with kernel 3.2.34, which uses systemd instead of innitab.
I've already seen some topics (like this question) with reference to modifications on some service files (like /etc/systemd/system/getty.target.wants/getty#tty1.service), but that only helped me partly: If I power/reset my BBone while keeping it connected via USB to my computer, it autologs as expected. But, if I just power the BBone with a wallwart (without any other connections), it doesn't seem to log in. At least I believe that's what is happening, as I have a program prepared to autorun after login and it only starts on the first case (with USB on).
I'd appreciate any help. Thanks.
Turned out that a RF module attached to my beaglebone was being powered via USB, and this module should be activated by my test program mentioned in the question. So, when I unplugged my BBone USB cable, I was actually separating its GND from the RF Module's ground.
In short, I just had to use the same source in the entire circuit and keep the autologin configuration explained in the topic I also mentioned in my question.
You could make your program a service and run after user instance of systemd.
Lets say you have a graphical.target in your /usr/lib/systemd/system then just put symlink to ../systemd-user#.target to /usr/lib/systemd/system/graphical.target.wants/system named like systemd-user#<your-user-name>.service.
This systemd-user#.service should containe ExecStart line like /usr/bin/systemd --user.
Then you'll have to add your application's service-file to /usr/lib/systemd/user.
More info is at http://www.freedesktop.org/software/systemd/man/systemd.html and http://www.freedesktop.org/software/systemd/man/systemd.unit.html