Tag Info

New answers tagged

0

There is no way to convert in place a non ZFS file system to a ZFS one. You need to backup the former, create the pool and restore your data. It is also unclear how you want to create a RAIDZ pool with only two 4TB disks. You can only create a mirror or a stripe with two devices.


0

It is not possible to reformat your drive without losing all the data stored on it.


0

This is just a hint! Because I came to this question and found an answer by myself. Sometimes you can use ls -lha /dev/mapper/ or similar to see the mapped devices and you can use mount to resolve it.


0

Boot your system from live DVD or live USB, then install boot-repair and run it. The following pages help to install and run boot-repair. https://help.ubuntu.com/community/Boot-Repair How to install the Boot-Repair tool in an Ubuntu live disc?


0

It sounds like you are looking for snapraid.


0

This is a known issue: https://bugs.launchpad.net/ubuntu/+source/mdadm/+bug/1318351 Please post a followup to the bug


0

sudo -i (enter your password here) ldmtool scan ldmtool create all (the code above requires that you have already run "sudo apt-get install ldmtool") I created a little script I run every time I login called mount.sh in my root directory so that after I login to my root terminal I just run the mount.sh script. If someone knows how to not require the input ...


1

If you have a disk image on a BTRFS volume, you might need to turn off the Copy on Write feature, at least for your VM disk image. CoW copies altered data to a new space (with its alterations) before modifying the file header data. On a VM this means shoving a HUGE file around for even the most basic change. You can disable CoW on a file (the disk image) ...


0

md126 looks like a randomly made up md number that the recovery had put there, it's usually not the one in /etc/mdadm/mdadm.conf When a kernel is updated. It runs update-initramfs, update-grub. They grab the md? numbers from /proc/mdstat /etc/mdadm/mdadm.conf The numbers there have to be the same for initrd to boot. Also, check in these files to see that ...


0

I had this problem yesterday. My fix is here... MDADM RAID1 Home Server System disk error: incrementally starting raid arrays mdadm: Create user root not found If you're running "update-grub" from the "recover from a broken system" you have to make sure that the currently mounted drives in /proc/mdstat are correct first. Double check the UUID=??? /dev/md? ...


0

I just had this problem too. I noticed that your md is numbered md126 which is usually a random number made up at boot time, not the number from mdadm.conf In /boot/grub/grub.cfg, various things refer to both /dev/md?? and UUID=..... Both are needed. If the machine is booting up with a random md??? number everytime, initrd will struggle to find the raid ...


0

Oh boy this is a fun one, I went through this more times than I Care to admit :) Disclaimer: I don't have RAID on the Windows Drives, so not sure if it will have any effect Install Windows (you already have it so skip) Boot to Ubuntu USB/CD and go to install When you get to the screen that asks you to automatically or manually partition, select ...


0

I haven't tried, but just came accross http://www.salamander-linux.com/. Salamander is a modified version of the default installer for Ubuntu Linux, Ubiquity. This modified installer allows users to easily install Ubuntu Linux onto a Software RAID array. No special hardware is required -- the Salamander installer can be used on any system with multiple hard ...


-1

I have exactly the same problem with grub. Could you please explain the steps to change the grub location from /dev/md126p1 to /dev/md126 and boot the system properly?



Top 50 recent answers are included