Re: Partition problems.
Hello, Thanks for your reaction. The NAS in question is a QNAP TS-109, a one bay model. From what I could gather the firmware is stored in flash and the disk is used to it's maximum for data storage. This is the layout I see when doing cat /proc/partitions: 120060864 sdb 530113 sdb1 530145 sdb2 118913130 sdb3 72292 sdb4 The guys from Qnap have connected to the system in the past to try and repair it and they claimed the data was there but the system partition is corrupt. I'm letting ddrescue do its thing again, hopefully getting a better image. I found some things online in the Forensics wiki: ddrescue --no-split /dev/sdb image log followed by: ddrescue --direct --max-retries=3 /dev/sdb image log and finally: ddrescue --direct --retrim --max-retries=3 /dev/sdb image log Once the process completes I'll let e2fsck run again and come back with detailed error messages. Fingers crossed. J. -Original Message- From: Camaleón Sent: Friday, November 04, 2011 6:17 PM To: debian-user@lists.debian.org Subject: Re: Partition problems. On Thu, 03 Nov 2011 15:48:50 +0100, Johan Verbelen wrote: I've been trying to fix this disk for a week now, but everythin I tried hasn't been working. I'm a linux starter however, so that doesn't help. The drive in question is a 120G Maxtor that was housed in a NAS. After a power outage the NAS reported the disk as empty. I took it out and assumed a hardware error. I have access to a harddisk hardware test suite but all those tests indicated that the disk is fine. The NAS runs an embedded linux (debian based) and has ext3 partitions so I started looking around for possible solutions. What kind of NAS appliance was that and what kind of disk layout did you have setup? Maybe what hapenned is that hard disk was part of a RAID or spanned volume and after the power outage the disk itslef was healthy but the RAID volume was put in degraded mode or the spanned layout had any problem :-? Using ddrescue an image was made, it reported 10 errors (45056B). I took a 1TB drive and installed that in my Ubuntu 32 bit machine as secondary disk with two partitions. One holding the image, one to hold the extracted image. When running e2fsck on that extracted image it reports a bad magic number in a superblock. I tried other superblocks and the last one worked (10240), however, the system ran out of memory trying to fix errors (4Gb system memory). I decided to run Ubuntu 64 bit live cd and hope that would solve the memory issue, but the issue remained. I then booted my main machine (12Gb memory) with Ubuntu live 64bit, but alas, out of memory again. The exact error message could have been useful. It could have been that e2fsck was complaining about /tmp or tmpfs space or something that can be tweaked easily... Of course, a LiveCD environment is very limited to carry out these recovery tasks because the live system has limited room for doing anything :-) At this point my hair is turning grey and I'm seeing linux commands in my sleep (good, I'm learning!). I decide to try some datacarving. Foremost and Photorec worked but the amount of usable files was pretty low and a lot didn't show up. At an end, I ran Testdisk and Parted. Both detect partitions but seem to think they're ext2. After they do their thing I still can't access it though (possibly I'm doing something wrong, this was late last night). Does anyone know how to fix the issue or what I could try next?Thanks for any advice you can dispense. :) J. If the device was acting as a single hard disk or volume, Photorec is one of the recommended tools for data recovery, so if you had no success with this tool it does not look good :-( If the disk was part of any kind of RAID 0, LVM or spanning layout maybe the remainder data is needed in order to be able to perform a full recovery, I would contact the manufacturer of the NAS and ask for any advice on how to proceed in such cases. ((I'm sorry if this is a double post, I tried using a different e-mail address yesterday but since it didn't show I assumed it might have gotten filtered.)) Mmm, this is the only post I have seen from you but AFAIK there is no filter in this mailing list. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.11.04.17.17...@gmail.com -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/042D6FF9B1B44AD3AE3B50457D24FD16@Win7
Re: Partition problems.
On Thu, 03 Nov 2011 15:48:50 +0100, Johan Verbelen wrote: I've been trying to fix this disk for a week now, but everythin I tried hasn't been working. I'm a linux starter however, so that doesn't help. The drive in question is a 120G Maxtor that was housed in a NAS. After a power outage the NAS reported the disk as empty. I took it out and assumed a hardware error. I have access to a harddisk hardware test suite but all those tests indicated that the disk is fine. The NAS runs an embedded linux (debian based) and has ext3 partitions so I started looking around for possible solutions. What kind of NAS appliance was that and what kind of disk layout did you have setup? Maybe what hapenned is that hard disk was part of a RAID or spanned volume and after the power outage the disk itslef was healthy but the RAID volume was put in degraded mode or the spanned layout had any problem :-? Using ddrescue an image was made, it reported 10 errors (45056B). I took a 1TB drive and installed that in my Ubuntu 32 bit machine as secondary disk with two partitions. One holding the image, one to hold the extracted image. When running e2fsck on that extracted image it reports a bad magic number in a superblock. I tried other superblocks and the last one worked (10240), however, the system ran out of memory trying to fix errors (4Gb system memory). I decided to run Ubuntu 64 bit live cd and hope that would solve the memory issue, but the issue remained. I then booted my main machine (12Gb memory) with Ubuntu live 64bit, but alas, out of memory again. The exact error message could have been useful. It could have been that e2fsck was complaining about /tmp or tmpfs space or something that can be tweaked easily... Of course, a LiveCD environment is very limited to carry out these recovery tasks because the live system has limited room for doing anything :-) At this point my hair is turning grey and I'm seeing linux commands in my sleep (good, I'm learning!). I decide to try some datacarving. Foremost and Photorec worked but the amount of usable files was pretty low and a lot didn't show up. At an end, I ran Testdisk and Parted. Both detect partitions but seem to think they're ext2. After they do their thing I still can't access it though (possibly I'm doing something wrong, this was late last night). Does anyone know how to fix the issue or what I could try next?Thanks for any advice you can dispense. :) J. If the device was acting as a single hard disk or volume, Photorec is one of the recommended tools for data recovery, so if you had no success with this tool it does not look good :-( If the disk was part of any kind of RAID 0, LVM or spanning layout maybe the remainder data is needed in order to be able to perform a full recovery, I would contact the manufacturer of the NAS and ask for any advice on how to proceed in such cases. ((I'm sorry if this is a double post, I tried using a different e-mail address yesterday but since it didn't show I assumed it might have gotten filtered.)) Mmm, this is the only post I have seen from you but AFAIK there is no filter in this mailing list. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pan.2011.11.04.17.17...@gmail.com
Re: partition problems
On Sat, 21 Jan 2006 15:56:17 + (GMT) david cuthbertson [EMAIL PROTECTED] wrote: Hi, Sorry, I am still learning, so not very good at explaining things. /dev/hda1 is winxp I now know that /dev/hda2 is the extended partition Then comes Debian: /dev/hda5 is swap /dev/hda7 is /home (ext3) /dev/hda6 is / (and everything else) (ext3) There are no other unused partitons or unpartitioned space. Grub boots from MBR into either Debian (hda6,(hda7,hda5)) or winxp (not very often) without any problems - appears to be fully functional. My other Debian system is on /dev/hdb1. From there, or from a knoppix livecd, I can mount /dev/hda7 but /dev/hda6 will not mount (sorry I can't remember the error message and I am not at home right now to reproduce it). well, this would really be crucial information... so you might want to provide that. where are you trying to mount /dev/hda6? The reason for mounting these partitions is to backup stuff from /etc, /usr, /var, etc, in case of problems! After failing to mount I ran fdisk to check for more information and discovered that: what prevents you from making backups from your other debian boot? 'Partition 2 does not end on cylinder boundary.' Would mkfs destroy the data on the partition? ummm. yeah. A Cheers, David david cuthbertson wrote: Hi, Mounting /dev/hda2 or /dev/hda6 to backup my hard-drive fails. /dev/hda7 mounts OK. Running fdisk I get: Command (m for help): p Disk /dev/hda: 20.4 GB, 20490559488 bytes 16 heads, 63 sectors/track, 39703 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 13564 6836224+ 7 HPFS/NTFS /dev/hda2 13579 3970113165267+ 5 Note carefully where /dev/hda2 starts and ends. Extended Partition 2 does not end on cylinder boundary. /dev/hda5 37772 39701 971901 82 Linux swap / Solaris /dev/hda6 * 13579 25676 6096604+ 83 Note carefully where /dev/hda6 starts and ends Linux /dev/hda7 25676 37772 6096636 83 Linux Note carefully where /dev/hda7 starts and ends /dev/hda2 is an *extended* partition. That means that it is a chunk of disc which has been reserved to create other partitions in it. It cannot be used as a partition itself. Both /dev/hda6 and /dev/hda7 are *part* of /dev/hda2. I don't know what you have done with your mounts, since you didn't show them, but you might try mounting /dev/hda6, it might have a file system in it. If it doesn't, then you could try mkfs and then mount /dev/hda6 ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] pgpckrGkVU9Ta.pgp Description: PGP signature
Re: partition problems
Hi, Sorry, I am still learning, so not very good at explaining things. /dev/hda1 is winxp I now know that /dev/hda2 is the extended partition Then comes Debian: /dev/hda5 is swap /dev/hda7 is /home (ext3) /dev/hda6 is / (and everything else) (ext3) There are no other unused partitons or unpartitioned space. Grub boots from MBR into either Debian (hda6,(hda7,hda5)) or winxp (not very often) without any problems - appears to be fully functional. My other Debian system is on /dev/hdb1. From there, or from a knoppix livecd, I can mount /dev/hda7 but /dev/hda6 will not mount (sorry I can't remember the error message and I am not at home right now to reproduce it). The reason for mounting these partitions is to backup stuff from /etc, /usr, /var, etc, in case of problems! After failing to mount I ran fdisk to check for more information and discovered that: 'Partition 2 does not end on cylinder boundary.' Would mkfs destroy the data on the partition? Cheers, David david cuthbertson wrote: Hi, Mounting /dev/hda2 or /dev/hda6 to backup my hard-drive fails. /dev/hda7 mounts OK. Running fdisk I get: Command (m for help): p Disk /dev/hda: 20.4 GB, 20490559488 bytes 16 heads, 63 sectors/track, 39703 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 13564 6836224+ 7 HPFS/NTFS /dev/hda2 13579 3970113165267+ 5 Note carefully where /dev/hda2 starts and ends. Extended Partition 2 does not end on cylinder boundary. /dev/hda5 37772 39701 971901 82 Linux swap / Solaris /dev/hda6 * 13579 25676 6096604+ 83 Note carefully where /dev/hda6 starts and ends Linux /dev/hda7 25676 37772 6096636 83 Linux Note carefully where /dev/hda7 starts and ends /dev/hda2 is an *extended* partition. That means that it is a chunk of disc which has been reserved to create other partitions in it. It cannot be used as a partition itself. Both /dev/hda6 and /dev/hda7 are *part* of /dev/hda2. I don't know what you have done with your mounts, since you didn't show them, but you might try mounting /dev/hda6, it might have a file system in it. If it doesn't, then you could try mkfs and then mount /dev/hda6 ___ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: partition problems
Command (m for help): p Disk /dev/hda: 20.4 GB, 20490559488 bytes 16 heads, 63 sectors/track, 39703 cylinders Units = cylinders of 1008 * 512 = 516096 bytes Device Boot Start End Blocks Id System /dev/hda1 1 13564 6836224+ 7 HPFS/NTFS /dev/hda2 13579 3970113165267+ 5 Extended Partition 2 does not end on cylinder boundary. /dev/hda5 37772 39701 971901 82 Linux swap / Solaris /dev/hda6 * 13579 25676 6096604+ 83 Linux /dev/hda7 25676 37772 6096636 83 Linux Hda1 is WindozeXP; the rest is Debian Sarge (ext3) I suppose you have debian on /dev/hda7 and want to use hda6 for backup. Did you format /dev/hda6 (mkfs.ext3 /dev/hda6)? What does mount /dev/hda6 /mnt say? /dev/hda2 is an extended partition, it does not contain a file system, thus cannot be mounted. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: partition problems
david cuthbertson wrote:
Hi,
Mounting /dev/hda2 or /dev/hda6 to backup my
hard-drive fails. /dev/hda7 mounts OK.
Running fdisk I get:
Command (m for help): p
Disk /dev/hda: 20.4 GB, 20490559488 bytes
16 heads, 63 sectors/track, 39703 cylinders
Units = cylinders of 1008 * 512 = 516096 bytes
Device Boot Start End Blocks Id
System
/dev/hda1 1 13564 6836224+ 7
HPFS/NTFS
/dev/hda2 13579 3970113165267+ 5
Note carefully where /dev/hda2 starts and ends.
Extended
Partition 2 does not end on cylinder boundary.
/dev/hda5 37772 39701 971901 82
Linux swap /
Solaris
/dev/hda6 * 13579 25676 6096604+ 83
Note carefully where /dev/hda6 starts and ends
Linux
/dev/hda7 25676 37772 6096636 83
Linux
Note carefully where /dev/hda7 starts and ends
/dev/hda2 is an *extended* partition. That means that it
is a chunk of disc which has been reserved to create
other partitions in it. It cannot be used as a partition
itself. Both /dev/hda6 and /dev/hda7 are *part* of /dev/hda2.
I don't know what you have done with your mounts, since
you didn't show them, but you might try mounting /dev/hda6,
it might have a file system in it. If it doesn't, then
you could try mkfs and then mount /dev/hda6
HTH
Mike
--
p=p=%c%s%c;main(){printf(p,34,p,34);};main(){printf(p,34,p,34);}
This message made from 100% recycled bits.
You have found the bank of Larn.
I can explain it for you, but I can't understand it for you.
I speak only for myself, and I am unanimous in that!
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Partition problems
On Fri, Aug 04, 2000 at 11:16:47AM +0200, Sven Burgener wrote: Hi all When running fdisk -l I get the following: box:~ # fdisk -l Disk /dev/hda: 64 heads, 63 sectors, 787 cylinders Units = cylinders of 4032 * 512 bytes Device BootStart EndBlocks Id System /dev/hda1 * 111 20632+ 83 Linux Partition 1 has different physical/logical endings: phys=(40, 15, 63) logical=(10, 15, 63) Partition 1 does not end on cylinder boundary: phys=(40, 15, 63) should be (40, 63, 63) /dev/hda21176131544 82 Linux swap Partition 2 has different physical/logical beginnings (non-Linux?): phys=(41, 0, 1) logical=(10, 16, 1) Partition 2 has different physical/logical endings: phys=(301, 15, 63) logical=(75, 31, 63) Partition 2 does not end on cylinder boundary: phys=(301, 15, 63) should be (301, 63, 63) /dev/hda376 787 1434384 83 Linux Partition 3 has different physical/logical beginnings (non-Linux?): phys=(302, 0, 1) logical=(75, 32, 1) Partition 3 has different physical/logical endings: phys=(1023, 15, 63) logical=(786, 63, 63) Partition 3 does not end on cylinder boundary: phys=(1023, 15, 63) should be (1023, 63, 63) Disk /dev/hdb: 128 heads, 63 sectors, 782 cylinders Units = cylinders of 8064 * 512 bytes Device BootStart EndBlocks Id System /dev/hdb1 1 381 1536160+ 83 Linux /dev/hdb2 382 762 1536192 83 Linux /dev/hdb3 763 782 80640 83 Linux I have 2 HDs, hda and hdb; both have 3 partitions. hda is the system disk containing a /boot, a / and a swap partition. What can I do about the Partition X has different physical ... lines from fdisk -l's output? Anyone experienced this before? Harmful? Things seem fine; havent'd had problems so far... I'd like to be CC'ed. If I'm doing my math right, your /dev/hda is a 1.5 GB disk. Which seems a bit small for the issue I suspect. But I suck at math. Something in th 6-12 GB range would more likely have these issues. Usually I get this sort of message if I've got my disk geometry configured wrong. Read the LILO docs on specifying disk geometry in /etc/lilo.conf or at the boot prompt. It's cyl/sec/head or cyl/head/sec or something like that. See if your fdisk isn't happier after this. Kernel version may make a difference as well, but I believe this refers to larger disks than you seem to be dealing with. -- Karsten M. Self kmself@ix.netcom.com http://www.netcom.com/~kmself Evangelist, Opensales, Inc.http://www.opensales.org What part of Gestalt don't you understand? Debian GNU/Linux rocks! http://gestalt-system.sourceforge.net/K5: http://www.kuro5hin.org GPG fingerprint: F932 8B25 5FDD 2528 D595 DC61 3847 889F 55F2 B9B0 pgpQ9gCc7PRBC.pgp Description: PGP signature
Re: Partition problems
kmself@ix.netcom.com wrote: [snipped my stuff] If I'm doing my math right, your /dev/hda is a 1.5 GB disk. Which seems a bit small for the issue I suspect. But I suck at math. Something in th 6-12 GB range would more likely have these issues. Yes, it is a 1.5 GB disk. The other (hdb) is ~ 3 GB in size. Usually I get this sort of message if I've got my disk geometry configured wrong. Read the LILO docs on specifying disk geometry in /etc/lilo.conf or at the boot prompt. It's cyl/sec/head or cyl/head/sec or something like that. See if your fdisk isn't happier after this. I'll try. Kernel version may make a difference as well, but I believe this refers to larger disks than you seem to be dealing with. Seems to hit me, though... Cheers Sven
