I need to copy data from a single HD, which used to be part of a Linux RAID 1. I've googled around, but can't find any clue how to mount partitions from this single HD.
Background: The HD comes from a linux based NAS box Synology DS207+. The NAS uses ext3 as filesystem. Both NAS disks are fine, but the other NAS hardware is dead and not worth repairing or replacing.
I have a 2 TB disk in an external SATA dock, formatted with a single ext3 (Linux) partition, which doesn't show up in the Windows 7 Computer Management->Disk Management utility, even as a raw/blank disk. I've verified that there's nothing wrong with the disk by connecting it to my Linux machine and mounting it, and I've verified that the dock is functioning properly by connecting a different FAT32-formatted disk, which mounts flawlessly as expected.I realize that I can't actually read the ext3 partition without additional software (e.g., Ext3IFS), but why doesn't the disk show up at all? Is there some sort of stupid anti-Linux filter built in? Is there any way to force Windows to recognize the disk, so that I can at the very least use direct block access with it?
Background: I want to clone an identical 2 TB disk onto this one. Due to my hardware layout, it's much easier to have the source disk attached to one machine and the destination disk connected to another, and do the clone over the network (the network is not a bottleneck with switched gigabit ethernet), than it is to hook them both up to one machine.(1) I did this once before when both machines were running Linux, but I've since upgraded the destination machine and decided to switch back to Windows for regular desktop use. I've got Cygwin installed, and have verified that the same basic method (dd + nc) will work, but I can't do anything if Windows doesn't even consider the destination disk to exist.I only have one eSATA port on each machine. Opening them up just to do this clone is a rather large annoyance. Also, since this is my backup disk, I'd like to eventually automate the cloning from the active disk to another one that I regularly swap with a third disk that I store off-site.
I have 2 identical disks originally configured as a pair for a server. Each of the disks has 2 partitions dev/sdb1,dev/sdb2. The sdb1 partitions I had configured as a raid1 mirror. The sdb2 partitions were non-raid and used as extra misc. Space. Further, the raid setup is also encrypted using dm-crypt luks. Now I want to redeploy each of the disks for new purposes. One of the disks i want to deploy exactly as before (keeping the partitions and content), however without being part of a raid array.
I've successfully deployed this disk into a new system and I am mounting the dev/sdb1 partition as dev/md0 because the disk is set to autodetect raid. Actually I am using cryptsetup and mounting with mapper. Can I get rid of the setting for auto detect on this partition without losing the data, or breaking the encryption? I just want to mount the partition as a standalone encrypted disk. Is it as simple as doing crypt setup luksOpen /dev/sdb1 then mounting it with mapper? Or do I need to change the partition in some way. Or do I simply continue to operate it as a 'broken' raid array?
my Fedora 11 system is not starting anylonger. It stops with the message:
Code:
VFS: Can't find ext4 filesystem on dev dm-0
The system told me since a while, that a lot of the sectors of one disk of the (software) RAID compound are failed already. So tried to disconnect each of the disks and start them separately. Unfortunaltly this is not working (for one its is not working at all, the other wents the same far as with both), when I tried to recover the system with the Fedora DVD, it said no distribution found. I am quite new and do not know so much about linux system, so i do not know what further information you could need. Maybe it can be important, that both disks are encryped (the system wents so far, that I can type in the password).
I recently installed Linux to run a few Linux based tools on a disk images I have, and I can't seem to copy the disk image over to my ext3 partition.
The particular distibution I'm using is BackTrack 4 r2, which is Ubuntu based. I can't seem to find specifically which version of Ubuntu is being used. The disk image is 108GB. It is currently located on a NTFS partition on a SATA hard drive connected directly to the computer. The ext3 partition is located on a second SATA hard drive connected to the same computer. It has 200GB total. I do not remember exactly how much free space it had but "df -h" showed a lot more than 108GB. The computer has 4GB of RAM and I gave it 8GB of swap space.
At this point it has been running for more than 12 hours. This is far longer than I would expect it to take had I been copying the file under Windows. How ever I do not have much experience with Linux, so if it's supose to take this long please let me know. I am planning on letting it run until I wake up tomorrow.
"cp -v" hasn't been very verbose at all. The only sign I have that indicates the computer is still trying to do something is the HDD light on my chasis that has stayed lit this whole time.
I had done a new lucid install to a 1 TB RAID 1 array using the alternate CD a few weeks back. I messed up that system trying to some hardware working that lucid doesn't have drivers for yet, so I gave up on it and reinstalled to a single 80 GB disk that I now want to move over to the RAID array.
I moved all of the existing files on the array to a single folder, then copied all of the folders from the 80 GB disk over to the array with permissions and symlinks (minus the contents of /proc and /sys, which I created empty).
These are the commands I used:
Quote:
p -a -d -R -v -t /media/raid_array /b*
cp -a -d -R -v -t /media/raid_array /d*
cp -a -d -R -v -t /media/raid_array /e*
cp -a -d -R -v -t /media/raid_array /h*
[Code]....
I tried to change fstab to use the 689a... for root, but when I try to boot, it's still trying to open /dev/disk/by-uuid/412d...
So then I booted from the single disk again and chrooted into the array, then ran update-initramfs -u. I got 3 "grep: /proc/modules: No such file or directory" errors, and "cat: /proc/cmdline: No such file or directory"- so I created directory /proc/modules, created an empty file /proc/cmdline, and ran the initramfs update again. Then I tried to shut down, which hung (probably because I was doing all of this from a terminal window in Gnome), so I killed the power after a couple of minutes.
It's still trying to use /dev/disk/by-uuid/412d... to boot.
What am I missing? I assume I just have to change the UUID to mount as root, but I don't know how.
Can RAID be implemented on a single hard disk ? If yes, plz give a link for it.
View 2 Replies View RelatedRecently, one the SMART utility said that one of the drives had failed and another drive was about to fail. I downed the box and hooked them up to my windows machine to run sea tools on them (They are all seagate drives). Sea Tools said that the drives were fine, while ubuntu said they were failing/dead. Yesterday I decided to try to fix one of the drives in the raid. I turned the server off, took the failed drive out, and restarted. Of course the raid didn't work because only 2 of the 3 drives were there, however it had been working w/ only 2 of the 3 drives for a couple months now (I'm a lazy college student). I turned it back off and back on with the drive there just to see if I could get the raid up again, but I havn't been able to get it to go. So far I've tried:
Code:
mdadm --assemble /dev/md0 /dev/sd[b,c,d]
mdadm: no recogniseable superblock on /dev/sdb
mdadm: /dev/sdb has no superblock - assembly aborted
[code]....
I'm looking for a way to trick the raid into working with just 2 drives until I can warranty the seagate and buy an external 1.5 TB drive to use as another backup. how to remove the bad drive from the array and replace it with a fresh drive, without data loss.
If you want a full run down as to WHY I want to do this, read here: webhostingtalk.com/showthread.php?t=899909Basically, my ISP could not get my server running stable on a simple raid 1 (or raid 5) so what it came down to was having them install my system on a single disk. I don't exactly like this, main reason being, if the system (or HDD) crashes, I'll end up with another several hours of down time..
View 1 Replies View RelatedI'm fairly new to Ubuntu and I'm running Karmic Koala. I just reformatted an NTFS partition to Ext3, as I no longer need to access is from my windows installation. Now I'm unable to mount it though, and I get the message: Error mounting: mount exited with exit code 1: helper failed with: mount: only root can mount /dev/sda6 on /media/DATA2 (DATA2 being the name of the previous NTFS partition. Now the label is linuxdata)
When I try to mount it using sudo in terminal I get the following message if I use the label DATA2:
NTFS signature is missing.
Failed to mount '/dev/sda6': Ogiltigt argument
The device '/dev/sda6' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
And if I use the label linuxdata: mount: can't find /media/linuxdata in /etc/fstab or /etc/mtab I've tried to search for help, but been unable to find an explanation.
I just made a new storage partition and formatted it as Ext3. Now, this particular partition is shown and can be read at the terminal "fdisk -l". However, unlike in my Mint 7 partition, it does not show in my Fedora 10.
Code: [jun@localhost ~]$ sudo fdisk -l
[sudo] password for jun:
Disk /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc5e3f820
[Code]....
This partition can also shows be seen in gparted in Fedora. However, even in the "Places" tab, it does not show.
I dont know if this is possible or not but here what I would like to do. I have 6 linux server and each has 100GB disk space. All of these 6 box are compute nodes and space are not used really. However, If I can combine 6 servershard disk that will in total 6*100GB gives you quite a bigger space. Is there any tool or ways to mount these drive in one volume instead of mounting individually ?
View 2 Replies View RelatedI can't seem to get past step 6 of he installation of Ubuntu 10.04. I get the error: The ext4 file system creation failed... on single partition (no raid). I chose ' / ' as the mount point, and have tried with and without a swap drive. I'm installing on a Sony VAIO VGN-NS160D, and the HDD was previously formatted to NTFS. There's no other OS so I don't see any way of getting a command line to try a sudo fdisk..
View 1 Replies View RelatedI attach a picture of my future disk partitioning,as I thought it should be. As you can see, the first two partitions are 2 different windows installations. At the end of the disk, I have specified a partition as ext3 104855 MB (sda9) and swap 8192 MB (sda. What should the the mount point of sda9 be? Should I specify a partition for /, /boot, /home, /tmp, ...etc? Or it is ok to make mount point '/'?
View 5 Replies View RelatedOS: Debian unstable 32bit, kernel 2.6.32-2, grub 1.98 from late january 2010 (only have working net-access from work now, so I am grabbing information from memory). EXT3 and EXT4 support is compiled into the kernel along with chipset/scsi/sata support (not as modules), and I have tested to boot ext3 with it before proceeding. Prereq: my old disk started to have too much S.M.A.R.T errors, so I bought another one, put in a USB cabinet, added swap and ext4 partition/filesystem to it, and copied over all data from the old system to the new that was mounted at /dest using the command "find ./ -xdev -print0 | cpio -paV0 /dest". Swiched disks, so I now have the ext4 disk sitting at /dev/sda (partitions: sda1 => ext4, sda2 => swap), and booted into rescue-mode from cdrom, using /dev/sda1 as root with a shell on. After doing this, I performed the following commands:
mount --bind /dev /dest/dev
chroot /dest
modified the /etc/default/grub to instruct the kernel to boot using ext4, ran grub-install --recheck /dev/sda
ran update-grub to modify /boot/grub/grub.cfg (which looks as it should) After doing this, grub finds my partition and mounts it. It however stalls with the message: "warning: unable to open an initial console" and does nothing after this point. I have no ramdisk, but my old kernel booted fine from ext3 (and still does if I copy it to a ext3 partition), and since the ext4 support is compiled into the kernel - should I really need a ramdisk?
Just ran into an uncomfortable problem. I usually never save any documents on my machine, and keep all my stuff on an external USB hard disk. (an 80GB TrekStor DS microdisk q.u)
Well yesterday this disk just would not mount.
Read through related posts but nothing seemed to work. Even tried it on a Windows machine.
Tried TestDisk utility. Found nothing wrong with the drive, but still could not repair the MBR.log code...
Palimpsest Utility recognized the drive, but just will not let me do anything with it except format it.
How can i repair the partitions and MBR without losing all my data?
Have a new debian install on a asus h170m-plus (was going to use ubuntu but didnt support the hardware/software combo i needed)
Install is fine. but during install it didnt see my 1tb raid1 drive..
after reboot, debain boots great, and i can mount the raid drive in the file manager.
I can see it and in mtab it shows up :
"/dev/md126 /media/user/50666249-947c-4e8f-8f56-556b713a6b6a ext4 rw,nosuid,nodev,relatime,data=ordered 0 0"
How can I permanently add this mount point so it is found at boot up at /data...
After an install of suse 11.4, one of my drives raid 0 (ichr9 intel) does not mount and is not recognized as being formatted in NTSF, while the other unit raid 0 (ichr9) is recognized without problems?
View 4 Replies View Relatedconcerning Linux, mdadm, and creating RAID Array's in Debian. I've done a lot of reading and research on RAID both on this board and elsewhere (The Linux Documentation Project's Software-RAID HOWTO is especially good), but I've run across something that no one seems to explain, and I'm not sure why. I'm instructed to create partitions on the drives I wish to add to my array. These partitions inevitably take up the whole disk, and are always have their system IDs set to "Linux raid autodetect". What I don't understand is why, after creating these partitions, some guides then go on to create an array (say a RAID5 one) with just the disks themselves as members, while others go on to create the RAID5 array with the previously created partitions as members. E.g.,
mdadm --create --verbose /dev/md0 --level=5 --raid-devices=4 /dev/sda /dev/sdb /dev/sdc /dev/sdd
vs.
mdadm --create --verbose /dev/md0 --level=5 --raid-devices=4 /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1
What's the advantage of using one over the other?
I wanted to implement raid5 such that one partition is from my laptop's hard disk and others from other hard disks. After making one partition a raid partition, I rebooted the system. The computer stopped mid-way during booting, and brought me to the shell. On typing fsck -p, it told me an unexpected error occured in the partition which I had made for raid. Is there some condition that we cannot boot from a disk containing one of the raid partitions ?
View 1 Replies View RelatedI would like to mount a partition on a second disk as /home. I have two hdds. one is 250gigs that I wish to use for the / of two or more os'. The other is 1TB that I would like to use as /home/charlie and /home/prisca as well as some other partitions. Here is my current /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
proc /proc proc defaults 0 0
# / was on /dev/sda6 during installation
[code]....
On my embedded linux box, running on Linux Kernel 2.6.9 embedded with BusyBox utilities.
An Objective are follow:
1/ To figure out how many partitions are on the hard disk
2/ Create a extra partition about 10GB size on the hard disk
3/ Format the partition and mount var on that partition
Only utility to perform above operations I have "sfdisk" utility from BusyBox collection. Which get installed at the time of image flash in to ROM (8mb ROM size). The following is the root directory structure where hdd as a directory mounted /mnt/hdd1
Code:
~ > ls
bin etc lib proc sbin sys var
dev hdd mnt root share tmp var_init
Within /bin sfdisk utility can be used which I tried but no avail.
Code:
~ > sfdisk -l /dev/hda
/dev/hda: No such file or directory
sfdisk: cannot open /dev/hda for reading
~ > sfdisk -l /dev/sda0
/dev/sda0: No such file or directory .....
I have a NAS from WD that runs some stripped down flavor of linux. The NAS has one USB port at the back which can be used to expand the storage. If I plug in an external disk formated in either NTFS or HFS+ then the system automatically mounts the disk and shares it over samba. If I plug in a disk that is formated in ext3, the disk is recognized but that's about it. It doesn't mount or get shared or anything. I have tried asking WD about this and I have tried asking google. But after two days of searching I am turning here for some more expert advice.
Here is what I've managed to figure out so far.
If I check dmesg before and after plugging in the ext3 usb disk I have found out that these lines are added to the log:
Code:
I have tried googleing those last two lines but I haven't found any info that I can make any sense of.
If I run the command "mount -a" I get the following messages from the shell: "mount: Cannot read /etc/fstab: No such file or directory"
Hover I am able to mount the ext3 disk manually. First I get this info from fdisk
Code:
And then I run these two commands:
Code:
This makes the usb disk visible in the shell, but since this is a NAS, it is kinda useless as long as it doesn't show up in samba.
Since I'm pretty new to linux I don't know what to try next so I'm hoping for some advice as to what I can do to make the ext3 usb disk automount.
I'm trying to mount a second hard drive as a ext3 (rw_acl,user_xattr). I type the ff.:
# mkfs.ext3 -c /dev/sdb1(it seems to create a file system from this 2nd HD)
then type:
# mount -v /dev/sdb1 / type ext3 (it seems to mount it)
But when I check the ext3 systems with typing:
# mount -t ext3 (to check the list of ext3 devices, it gives me this)
/dev/sda1 on / type ext3 (rw,acl,user_xattr)
/dev/sda2 on /home type ext3 (rw,acl,user_xattr)
/dev/sdb1 on / type ext3 (rw)
How can I make /dev/sdb1 on type ext3 as (rw,acl,user_xattr) as the others?
Running Debian Squeeze, I used gparted to wipe the fat partition on a 8GB USB thumbdrive, and repartitioned it with ext3. Everything goes fine, and gparted and fdisk -l both show the correct partition, but I can't seem to mount it, and automount in gnome fails as well.code...
View 5 Replies View RelatedI have suddenly lost a lot of free on my new Fedora 14 install.
To keep the story short, here's what disk usage looks like on my home: image
As you can see, home takes 100% but only 34% are actually occupied.
When entered as a root du | sort -nr > out.txt
Code:
81126756.
28141892./VirtualBox VMs
21462488./VirtualBox VMs/Win7
5244308./VirtualBox VMs/WinXP
[Code].....
I have a created an ext3 partition and when i tried to set is hidden flag, there seems no effect. how to set the hidden flag of an ext3 partition?
View 1 Replies View RelatedA HP Netserver LP2000r, with original SCSI controller and HP NetRaid-2M controller, 3x 36GB Ultra3 HDD in RAID5, Debian (sarge/etch), has crashed after 992 days without reboot. From all that I can see, a hardware failure, most likely with the memory. The HP Diagnostic tools cannot find any problem, but everytime I boot into Knoppix, I get between 2minutes and 2 hours of runtime, and then either a kernel oops or just a complete and sudden halt.
Well, the box has earned its money. However, there is some data on the drives that I need to recover (yes, I have beaten myself up properly about not backing up that data, don't even go there !). There are three partitions: sda1 is /, sda2 is swap and sda3 is a LVM volume with 3 logical volumes on it. As far as I can tell, the hardware defect must have been creeping in and has made a total mess of the inodes in all these partitions.
After booting into Knoppix, I can restore the volumes using pvscan, vgscan, lvscan, vgcfgrestore and vgchange. If I try and mount them: mayhem. So I try and check them, using fsck.ext3. All sorts of interesting nonsense, such as a completely empty inode 11 (the first inode) and then obviously from there on all else is pointless. I tried using debugfs, but the information on what to do with it is somewhat spurious.
P.S.: Tomorrow I will go and get myself a 16GB Flash Drive and then hopefully I will be able to dump the partitions one by one onto that drive and transfer the images onto a different computer for analysis and data recovery.
Background for the problem:
A. I have partitioned my WinXP LTop into:
--- WinXP NTFS partition
--- a vfat partition (mounted onto /fat32)
--- Installed F10 on ext3 virtual partition
B. I do not want install grub-loader in the Master Boot Record (that would loose my WinXP boot-loader for ever)
C. I have installed grub boot loader in the First Boot Sector
D. Now I have to boot using Rescue Mode, do:
1. dd if=/dev/sda2 of=/fat32/linux.bin bs=512 count=1
2. mount -t ntfs /dev/sda1 /ntfs
3. cp /fat32/linux.bin /ntfs
4. modify /ntfs/c/boot.ini and introduce the statement 'c:linux.bin="Linux"'
Problem: Im not able to do step D.2 above.
Symptom:
** after booting linux using the Rescue Mode: sh-3.2# chroot /mnt/sysimage sh-3.2# uname -r 2.6.27.5-117.fc10.i586 sh-3.2# mount -f ntfs /dev/sda1 /ntfs FATAL: Could not load /lib/modules/2.6.27.5-117.fc10.i586/modules.dep: No such file or directory ntfs-3g-mount: fuse device is missing, try 'modprobe fuse' as root
sh-3.2#
Observations:
* The rescue mode boots into i586 based kernel (I dont know what is the actual difference between i586 and i686 - will really appreciate if anyone can educate me about it). * The installation is only a i686 image and consequently there is *only* '/lib/modules/2.6.27.5-117.fc10.i686' dir and *no* other dir. There is no dir as xxxx.fc10.i586.
I accidentally formatted a 2TB drive of mine (big oops), but have recovered 2 of the 3 partitions using testdisk. My third partition is a LUKS encrypted partition. Testdisk managed to recover a piece of it, but it won't mount as most of it is unallocated. The partition originally occupied all space from sector 2,930,272,065 to the end of the disk -- sector 3,907,024,064. That is about 473 GBs. Currently, the partition only uses space from sector 2,930,272,065 to 2,930,288,129, about 7.84 MB.
The rest of the space is unallocated. Now what I need to do, is to expand the partition so that it occupies all the space that it used to. How would I do this? I cannot resize the partition, cause it would try to recreate the filesystem AFAIK and I don't want that, as it will fry my data. My data is not terribly important, but I would rather have it then not. I attached a screenie of kpartitionmanager. The partition in question is /dev/sdb2.