9/25/2023 0 Comments Systemrescuecd fsckdev/sda1) and the LVM (where the root filesystem is). So assuming you have an old one, you'll want to check the filesystem of both the /boot partition (/dev/sdX1 e.g. Older ones have a separate boot partition (of type 'extN' - where 'N' is a number between 2 & 4), whereas newer ones have the boot directory inside the LVM. IIRC our VM builds are generally installed with LVM. If that shows too much info, you can look at a specific disk by appending it's name at the end. You can look at all available drives using this: fdisk -l The disk should be named something like /dev/sdX where X is a letter (i.e. Then you'll need to find what the drive is. If it asks if you want to mount drives/partitions (TurnKey won't but others might), select no. So boot from the ISO and run a live session. Keep in mind though that if not using TurnKey, then you likely won't be root, so many/most of these commands, may need to be prefixed with sudo. Although if you need to dig deeper, then perhaps something built for purpose may be better? E.g. Any relatively recent distro would do the job, even a TurnKey ISO would do. Next step would be to boot the machine with a live Linux ISO of some description. Especially without being able to look over your shoulder. Then after that, there are a ton of factors to consider and the process is a little hard to describe exactly from memory. Then it won't matter what you do as worst case, you can trash it and start again with a new copy (and you still have the untouched original). If you don't have a backup to restore from, what I would do first is take a copy of the VMDK and work with the copy from here on. Remember data loss due to hardware (or other) failure is a matter of when not if! Data that isn't backed up should be considered living on borrowed time! If you don't have a backup, read on, but please make sure you do set up automated backups once it's up and running. Bam, done! If you have that set up, then skip this post and just do that! :) So if you'd been using TKLBAM (or some other automated remote backup tool), you could start a new server of the same version and simply restore your most recent backup. Maybe there's a way I could back up the database and copy it over the LAN to extract on a newly deployed appliance? Maybe I need to deploy an older version and copy my VMDK in? I think I'm close, just don't know enough about the filesystem to know how to restore the data.įirst up, the easiest way to recover this would be restore from backup. So my question: what are my options now? The webui doesn't load up. Then several lines starting with and then BusyBox v1.22.1 (Debian 1:1.22.0-9+eb8u1) built-in shell (ash) mount: mounting /dev on /root/dev failed: No such file or directory done.īegin: Running /scripts/init-bottom. Target filesystem doesn't have requested /sbin/init.īegin: Running /scripts/local-bottom. So, I load it up and it comes to an error " /bin/sh: can't access tty: job control turned off" and dumps me off at the terminal prompt. I grabbed a VMX from a Turnkey Redmine appliance, changed the references in the VMX, added the VM to inventory, removed the VMDK and re-added it. It took awhile, but I finally got the server, and after a few months of being busy with other stuff, I got one disk mounted and found the VMDK file No clue what happened to the rest of the VM. Those who had physical access to the box concluded that the RAID1 array had completely died, or maybe the RAID controller card, or who knows what. Almost a year ago I had a mediawiki appliance on a server which got relocated to my company's corporate headquarters.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |