I found the following pages helpful:
https://superuser.com/questions/1031283/how-to-get-the-data-off-of-a-readynas-drive
https://jim-st.blogspot.com/2012/07/mouning-readynas-drives-on-x86-systems.html
https://technostuff.blogspot.com/2012/06/how-to-mount-disk-used-by-readynas.html
I found that the right-hand drive was mountable, but required installation of some packages on a Fedora 29 desktop system:
git clone https://github.com/alperakcan/fuse-ext2.git
dnf install autoconf automake libtool
dnf install libfuse-dev e2fsprogs comerr-dev e2fslibs-dev
dnf install fuse-libs fuse3-libs
dnf install fuse-devel fuse3-devel
https://fedora.pkgs.org/29/fedora-x86_64/libcom_err-devel-1.44.3-1.fc29.x86_64.rpm.html
dnf install Downloads/libcom_err-devel-1.44.3-1.fc29.x86_64.rpm
dnf install e2fsprogs-libs e2fsprogs-devel
Next steps:
vgchange -ay c
lvscan
fuse-ext2 -o sync_read,allow_other,rw+ /dev/c/c /mnt/tmp
Data now accessible in /mnt/tmp
2019-04-15
2014-07-23
Installing Win7 guest on KVM with CentOS 7
Installation with virt-manager is fairly straightforward. However, unfortunately, this results in a guest that uses the very slow IDE disk driver. Changing to use virtio is a little tricky - this blog post was very helpful: http://setdosa.blogspot.com/2013/09/moving-your-windows-guest-from-ide-to.html
This is a general handy guide:
https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:os:win-guest
This is a general handy guide:
https://support.opennodecloud.com/wiki/doku.php?id=usrdoc:os:win-guest
2013-08-29
Installing Win7 guest in Virtualbox from a USB stick image
- Use dd to make an image file of the entire stick - e.g. dd if=/dev/sdg of=usb_stick.img
- Copy to target machine.
- Convert to .vmdk file using: "VBoxManage internalcommands createrawvmdk -filename output_usb.vmdk -rawdisk usb_stick.img (thanks to: http://www.dallagnese.fr/en/computers-it/boot-on-your-usb-drive-in-virtualbox-4/ ).
- Add the image file to the SATA controller as a hard drive. Make sure it has lowest SATA port number.
2013-02-16
SSH via intermediate host
In terminal on local machine:
$ ssh -f -N -L6969:localhost:6969 intermeduser@intermedhost
$ ssh intermeduser@intermed
intermedhost$ ssh -f -N -L6969:localhost:22 destuser@desthost
Then, in other local terminals:
$ ssh -p 6969 destuser@localhost
$ ssh -f -N -L6969:localhost:6969 intermeduser@intermedhost
$ ssh intermeduser@intermed
intermedhost$ ssh -f -N -L6969:localhost:22 destuser@desthost
Then, in other local terminals:
$ ssh -p 6969 destuser@localhost
2013-01-14
Updating Seagate Barracuda 7200.11 drive firmware on a Dell Optiplex 960
This was a real head-scratcher, because Seagate's ISO image would NOT boot on this machine, whether burnt to a CD or written to a flash drive with unetbootin.
I eventually succeeded by extracting the El Torito floppy image from the ISO using http://freecode.com/projects/geteltorito and then putting the files on a FreeDOS bootable flash drive using unetbootin.
I also found that unetbootin/FreeDOS requires a FAT16 formatted primary partition on the flash drive to work properly.
I eventually succeeded by extracting the El Torito floppy image from the ISO using http://freecode.com/projects/geteltorito and then putting the files on a FreeDOS bootable flash drive using unetbootin.
I also found that unetbootin/FreeDOS requires a FAT16 formatted primary partition on the flash drive to work properly.
2012-04-27
Obscure xinetd tip
If you have a "wait=yes" server bound to 127.0.0.1, you can get a syslog full of messages like this:
xinetd[25741]: warning: can't get client address: Transport endpoint is not connected
The trick is to add "flags=NOLIBWRAP".
THis bug report gives a clue as to the underlying cause: https://bugzilla.redhat.com/show_bug.cgi?id=108583
xinetd[25741]: warning: can't get client address: Transport endpoint is not connected
The trick is to add "flags=NOLIBWRAP".
THis bug report gives a clue as to the underlying cause: https://bugzilla.redhat.com/show_bug.cgi?id=108583
2012-04-05
Migrating a guest VM with Xen 3.2
'xen migrate' didn't work - it hung, as others have reported.
It turned out to be as simple as:
It turned out to be as simple as:
- Stop the original guest.
- Copy the disk image and the config files ( in /etc/xen/vm) to the new host.
- Execute 'xm create guest-name' on the new host.
- Done!
Subscribe to:
Posts (Atom)