I just put those two files in a folder on my hard drive with Windows and I could later access that folder from Linux and mount it from terminal. If somebody is interested how to create one then you can check this link: Īnd I didn’t use USB thumb drive to copy “debrick.sh” and “rootfs.img” to it. I used USB thumb drive formatted to FAT32 with Linux Live CD (version Ubuntu 12.10 ) instead of it. I didn’t use Download SystemRescueCd, because I have only two SATA cables in my PC. And I want to apologize for my bad English beforehand!ĭuring preparation I did everything like nfodiz wrote except two things. This may be helpful for people who don’t have advanced technical knowledge. I will try to describe all steps in detail. Here are the results of installing fresh OS on two empty drives on MBLD. Please try to be specific as possible as I don’t own a MBLDUO so can’t reproduce your stepsįirst of all I would like to thank nfodiz for a great guide! You are doing a great job and helping lots of people! Are there any changes I need to make to the guide? Yes this looks perfect if you have a 4TB MBLDUOīy the looks of things, you are back up and running now. Number Start End Size File system Name Flagsģ 15.7MB 528MB 513MB linux-swap(v1) primary raid Were the drives formatted to any filesystem prior to running the debrick script? I’m wondering if the script has trouble creating the EXT4 filesystem on the DataVolume because it is a RAW partition? With the single drive, it has been suggested to format the drive to ANY filesystem and then delete all partitions so all you are left with is UNALLOCATED space.Īfter i rebuild the raid1.then go normal as below No as the script specifically creates an EXT4 filesystem to that partition I use “parted” to check is drives partition is ready…sda4 still don’t have the file system(should be ext4?) The script should create an EXT4 filesystem to your DataVolume partition without issue I found the script can’t format the /dev/sda4
Not sure why this happens to a very small amount of people I have seen this reported a few times by people who used a similar debrick script on the single drive MBL. The OS should be enabling this by itself on boot. The script can’t auto enbale the drives samrt? I use smartctl -s on … to enable the /dev/sda and /dev/sdb…is this correct?
I search some meeage on the forums, is this caused by samrt diable ?
0 kommentar(er)
