i do have very many problems and the Guide doens´t help me :-(…
So i decided to enable SSH and installed minidlna… everything was fine… after this i tried to install an funambol server. My MBL starts no more… so no i try to give my MBL a new life But the Guide herer doesn’t work… PLEASE I NEED HELP I AM A LINUX NEWBIE…
i thought i had to enter the complete line like this
mdadm - S /dev/md0 ./debrick.sh rootfs.img /dev/sda
could you please explain for what ist the line mdadm -S /dev/md0 ?! I searched in google for it and it refers me to software raid system… is this correct?
and the biggest question what is device md0 ?! should this be my dvd rom drive, where the recue disc is in?
the other steps are understandable because i know the commands from the MS DOS system.
But the mdadm -S /dev/md0 line i do not understand…
thanks for the information - but i cannot reach anything :-(…
My situation:
Lenovo thinkpad t60
1 usb drive ntfs formated with rootfs and debrick script on it
2 usb drive is the mbl drive - one big 2 tb gpt file system without partition
Frist strange thing is that the Kernel setup hangs, when the mbl drive is connected and i get erros, when the mdam dialog comes… when i disconnect the mbl hard drive the recue disc starts up promt
After the startup i connect the mbl via usb and when i hit the dialog
mdadm -S dev/md0
mdadm: error opening /dev/md0: No such file or directory
when i type in the
./debrick.sh rootfs.img /dev/sda
there comes a screen
script will use the following disk:
and then nothing happens any more… the script hungs up
i saw the second guide on thje first page but i thought becuase there are no partitions anymore i do have to use the first guide with building the partiotion structure… i thought this is clever…
NEWS:
after 5 min waiting the script goes on … the word destroy i didn’t forget… mounting an ntfs drive and using the correct paths is also not the problem
now there is another question…
Warning blocksize 65536 not usable on the most systems
mkefs
mkfs.ext4 65536 bte blockss too big for system (max 4096)
proceed anyway? yes no?
i choosed no… no it ist checking for bad block… 35 min elapsed and only 0,14 % and (123/0/0 errors) is it good or bad?
tried everything the night - but i doesn’t help … now i launched my wd hard drive to windows and started wd lifeguard… i made a fuell scan and i got a lot of bad sectors… i think the hard drive is finished…
i have to order a new one… Big question … mit MBL was an 2 TB version … can i order a 3 TB WD Red and put it into the mbl case? will it work with the here posted guide?
I’ve tried various other operations and it seems to hang/pause forever. I did a recovery procedure w/ R-Linux, but it didn’t seem to recover any of my media files. Which folder are my files located in? isn’t it /media ?
so yesterday i bought a new wd red and i tried the script with an old toshiba hard drive… but it didn’t work … any ideas?
root@sysresccd /mnt/usb % ./debrick.sh rootfs.img /dev/sdc destroy
**********************DISK**********************
script will use the following disk:
Model: TOSHIBA MK8032GSX (scsi)
Disk /dev/sdc: 80.0GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
is this REALLY the disk you want? [y] y
**********************IMAGE**********************
**********************IMPLEMENTATION**********************
everything is now prepared!
device: /dev/sdc
image_img: rootfs.img
destroy: true
this is the point of no return, continue? [y] y
dd: writing ‘/dev/sdc1’: No space left on device
11+0 records in
10+0 records out
10485760 bytes (10 MB) copied, 0.0129123 s, 812 MB/s
dd: writing ‘/dev/sdc2’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000972191 s, 0.0 kB/s
dd: writing ‘/dev/sdc3’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000831251 s, 0.0 kB/s
dd: writing ‘/dev/sdc4’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.000795841 s, 0.0 kB/s
Testing with pattern 0x00: done
Reading and comparing: done
GNU Parted 3.1
Using /dev/sdc
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) mklabel gpt
(parted) mkpart primary 528M 2576M
(parted) mkpart primary 2576M 4624M
(parted) mkpart primary 16M 528M
(parted) mkpart primary 4624M -1M
(parted) set 1 raid on
(parted) set 2 raid on
(parted) quit
Information: You may need to update /etc/fstab.
Warning: blocksize 65536 not usable on most systems.
mke2fs 1.42.7 (21-Jan-2013)
/dev/sdc4 is not a block special device.
Proceed anyway? (y,n) y
mkfs.ext4: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
destroying was done, would you like to continue with installation? [y] y
mdadm: size set to 10176K
mdadm: ADD_NEW_DISK for /dev/sdc1 failed: No such device or address
mke2fs 1.42.7 (21-Jan-2013)
mkfs.ext3: Device size reported to be zero. Invalid partition specified, or
partition table wasn't reread after running fdisk, due to
a modified partition being busy and in use. You may need to reboot
to re-read your partition table.
mdadm: cannot get array info for /dev/md0
synchronize raid... done
copying image to disk...
dd: writing to ‘/dev/md0’: No space left on device
1+0 records in
0+0 records out
0 bytes (0 B) copied, 0.0190004 s, 0.0 kB/s
mount: /dev/md0: can't read superblock
cp: cannot stat ‘/mnt/md0/usr/local/share/bootmd0.scr’: No such file or directory
./debrick.sh: line 359: /mnt/md0/etc/nas/service_startup/ssh: No such file or directory
umount: /mnt/md0: not mounted
mdadm: stopped /dev/md0
BLKGETSIZE: Inappropriate ioctl for device
BLKGETSIZE: Inappropriate ioctl for device
all done! device should be debricked!
I have no more ideas … i will try the 2nd guide and report again…
I’ve tried various other operations and it seems to hang/pause forever. I did a recovery procedure w/ R-Linux, but it didn’t seem to recover any of my media files. Which folder are my files located in? isn’t it /media ?
Any thoughts are appreciated.
Kind regards,
-pro
The drive sounds to be dying but you may be able to pull your data off a little at a time. The data is located in the /DataVolume/shares folder. You may need to turn to a professional data recovery company if the data is irreplaceable and the above doesn’t work
@MJB0006 sometimes you need to run the script a second time after the partitions and table have been created. You will want to completely shut down the computer and boot the sysrescd and try again. If it doesn’t work, guide 2 is your best bet
I’ve tried various other operations and it seems to hang/pause forever. I did a recovery procedure w/ R-Linux, but it didn’t seem to recover any of my media files. Which folder are my files located in? isn’t it /media ?
Any thoughts are appreciated.
Kind regards,
-pro
The drive sounds to be dying but you may be able to pull your data off a little at a time. The data is located in the /DataVolume/shares folder. You may need to turn to a professional data recovery company if the data is irreplaceable and the above doesn’t work
What do you think of this?
Nothing shows up in the DataVolume. It only located maybe 15-20% of file names and I cancelled. But here it shows 0 under DataVolume. Do you think some how the drive got wiped out (formatted) or the hardware failure is just preventing anything from showing?
Thx for your input nfodiz. Really great to have your responsive help. Better than WD Customer support line (which told me my data is definitely recoverable). I hope WD is paying you.
I wish lol, but nope I’m just an end-user just like you that enjoys helping people when I can. Thanks for the kind words and I hope it all works out in the end for you.
