You can subscribe to this list here.
| 2004 |
Jan
|
Feb
|
Mar
|
Apr
(30) |
May
(47) |
Jun
(37) |
Jul
(63) |
Aug
(55) |
Sep
(56) |
Oct
(36) |
Nov
(24) |
Dec
(28) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2005 |
Jan
(60) |
Feb
(32) |
Mar
(39) |
Apr
(14) |
May
(17) |
Jun
(13) |
Jul
(22) |
Aug
(33) |
Sep
(70) |
Oct
(48) |
Nov
(30) |
Dec
(4) |
| 2006 |
Jan
(13) |
Feb
(8) |
Mar
|
Apr
(3) |
May
(8) |
Jun
(10) |
Jul
(13) |
Aug
(9) |
Sep
|
Oct
(13) |
Nov
|
Dec
|
| 2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
(24) |
Jul
(1) |
Aug
(1) |
Sep
(18) |
Oct
|
Nov
|
Dec
|
| 2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(2) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(5) |
Oct
|
Nov
(2) |
Dec
|
| 2010 |
Jan
(1) |
Feb
(3) |
Mar
|
Apr
(3) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: SourceForge.net <no...@so...> - 2005-04-01 19:56:28
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3079006 By: szaka Hello, This is a known, very rare, documented issue. The first time I've written about it here: http://marc.theaimsgroup.com/?l=linux-ntfs-dev&m=108401439420179&w=2 In the last 17 months I've got 5-6 such reports and thankfully recently I got two such NTFS images for development so I can add the needed support soon, when I have enough spare time. If you are willing to contribute by providing additional such NTFS metadata image then that would be also highly valuable. The compressed metadata is usually 0.5-3 MB and 'man ntfsclone' or the above URL tells how to create and compress it (note, most recent tar's, versions 1.14+, have a very serious bug that corrupts data thus just pure bzip2 is recomended for compression). Until we implement the needed support, you might look for a defragmenter that can defragment the MFT (Master File Table, inode 0). ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-30 20:06:02
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3075010 By: nobody I have a question about ntfsprogs-1.9.4 (mkntfs). I have tried to create and format NTFS drive placed in image file. The program says "all ok", but OS says "The file or directory is corrupted and unreadable" when I tried copy files and directories on it. What is wrong? ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-28 16:15:24
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3070382 By: nobody Hi folks, I am using the bundled ntfsprogs-1.9.0-21 with my SuSE Linux system. I have an NTFS partition that I have defragmented more than once, with paging turned off, and shut down cleanly. I get the following information -- linux:/home/ihab # ntfsresize -i /dev/hdc2 ntfsresize v1.9.0 NTFS volume version: 3.1 Cluster size : 4096 bytes Current volume size: 34371265024 bytes (34372 MB) Current device size: 34381670400 bytes (34382 MB) Accounting clusters ... Space in use : 14065 MB (40.9%) Estimating smallest shrunken size supported ... File feature Last used at By inode Multi-Record : 30372 MB 0 You might resize at 30371397632 bytes or 30372 MB (freeing 4000 MB). In Windows, the defrag graphical output shows nothing beyond the pretty contiguous block of files at the beginning of the filesystem. I understand this is a common question, but is there any way I could shrink this filesystem further? I mounted the filesystem and did "find -inum 0", but this returned no results. What should I do next? Thanks a huge lot and peace, Ihab Awad Palo Alto, CA ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-27 02:15:18
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3068729 By: formyh2 Additionally,The version of my OS is windows Xp ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-27 02:12:49
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3068728 By: formyh2 Hello, I have been reading the document on http://linux-ntfs.sourceforge.net/ntfs/concepts/file_record.html ,and try to write a NTFS_Manager_Program. I found that the Sequence Number of a File Record in the Record Header couldn't be writed freely,or windows will display 'the file or directory is breaken' .I think ,The Sequence Number must be submited strictly in a rule,it doesn't like The Update Sequence Number whose value can be set freely. My question is,how should I set the value of Sequence Number when I create a File Record. Excuse for my poor english,please. Thank you. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-23 00:53:42
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3062300 By: gkmohan I am happy that the problem is resolved. Kudos to you. Now we can backup ntfs partitions more reliably. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-21 03:08:29
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3058092 By: szaka OK, I know the explanation why the driver can read the directory but it's not possible by a loop mounted ntfsclone image. The driver can work at sector level meanwhile ntfsclone always works at cluster level. If one sector is wrong then ntfsclone marks the entire cluster bad, in your case all the 8 sectors. This is not too smart, I was aware of it already but so far I didn't consider it too important to improve on it. Your example demonstrated that it is important and I'll add the needed support for ntfsclone as soon as possible (after about two weeks). Thank you for your contribution, persistence! ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-20 19:36:12
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3057671 By: szaka > You are correct, today I ran it with --rescue > [root@localhost root]# ntfsclone --rescue -O /mnt/freestore/win-full.img /dev/hda3 > and it gives out errors "WARNING: Couldn't read a cluster, > data is lost" but finishes to create an image, ofcourse without > these clusters. This image has the same properties as the > image created before chkdsk /r was run. (i.e, I still can't > access some of the data e.g., /mnt/loop/WINDOWS) Unless somebody tells or figures out, I'll check after about two weeks why the NTFS driver can read dying sectors but not badblocks and ntfsclone. > Please let me know when you include the option --retries=<number>. It would take about 0.5-1 hour but currently I'm too sick to do any productive thing. Next chance will be about after two weeks. > Alternatively on a very bad disk with a lot of bad sectors, to save > time, you could only retry those sectors where windows claims to have > data. This is how it is done already. > I have no clue here but would not using ntfs driver simplify life a > lot? Is ntfsclone designed to be a stand-alone program? Ntfsclone makes an _exact_ backup, at bit level. Currently the NTFS driver doesn't support getting all the needed information, also the Linux kernel has a lot of limitations to export exotic things to user space. > To summarize for future references (szaka please make amends as necessary) > To clone an ntfs partition > 1) run `badblocks <device>` to check for bad blocks. > If there are bad blocks this will dump some numbers to stdout > If there are bad blocks > 2) run `chkdsk /f /r <drive:>` (ofcourse in windows) > 3) run `ntfsclone --rescue --retries=<number> -o <image> <device> > otherwise > 2) run `ntfsclone -o <image> <device>` Simpler: 1) run `ntfsclone -o <image> <device>` if you get the 'read_all: I/O error' 2) run `ntfsclone --rescue --retries=<number> -o <image> <device> then you could run 3) run `chkdsk /f /r <drive:>` and retry to make a better backup 4) run `ntfsclone --rescue --retries=<number> -o <image> <device> The reason to postpone chkdsk /r is that sometimes it kills the disk entirely (the disk stops working at all) so you won't have any chance anymore to save your data. Similarly, running badblocks on a dying disk first may kill the disk and no chance to save the data later on. > Optionally I strongly suggest (if your kernel supports ntfs read) > o `mkdir /mnt/loop` > o `mount <image> /mnt/loop -t ntfs -o loop` > o if windows is not mounted mount it (say, /mnt/windows') > o `diff -r /mnt/loop /mnt/windows` > If all goes well you should not see any errors on the last command. Right, this is guaranteed. Any error would mean a bug somewhere or one has bad sectors and used the ntfsclone --rescue option. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-20 18:53:03
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3057628 By: gkmohan Thanks for the lesson on bad blocks. Yes, when I ran chkdsk /r there were 5 stages. You are correct, today I ran it with --rescue [root@localhost root]# ntfsclone --rescue -O /mnt/freestore/win-full.img /dev/hda3 and it gives out errors "WARNING: Couldn't read a cluster, data is lost" but finishes to create an image, ofcourse without these clusters. This image has the same properties as the image created before chkdsk /r was run. (i.e, I still can't access some of the data e.g., /mnt/loop/WINDOWS) Please let me know when you include the option --retries=<number>. Alternatively on a very bad disk with a lot of bad sectors, to save time, you could only retry those sectors where windows claims to have data. Then one needs to first create a table of data sector numbers based on the directory structure. Tedious. I have no clue here but would not using ntfs driver simplify life a lot? Is ntfsclone designed to be a stand-alone program? To summarize for future references (szaka please make amends as necessary) To clone an ntfs partition 1) run `badblocks <device>` to check for bad blocks. If there are bad blocks this will dump some numbers to stdout If there are bad blocks 2) run `chkdsk /f /r <drive:>` (ofcourse in windows) 3) run `ntfsclone --rescue --retries=<number> -o <image> <device> otherwise 2) run `ntfsclone -o <image> <device>` Optionally I strongly suggest (if your kernel supports ntfs read) o `mkdir /mnt/loop` o `mount <image> /mnt/loop -t ntfs -o loop` o if windows is not mounted mount it (say, /mnt/windows') o `diff -r /mnt/loop /mnt/windows` If all goes well you should not see any errors on the last command. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-20 14:57:32
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3057420 By: szaka > My knowledge on bad blocks is limited. First I start with a question, > what constitues a bad block? Does failing to read a block more than a > few times constitute bad block? Disks are divided into sectors, one sector is usually 512 bytes. Sector is the smallest unit what can be addressed. If reading or writing a sector fail because the disk surface got damaged for whatever reason (too old, sudden power outage, kicking the computer, etc) then the sector is considered bad, flawed, damaged, unrecoverable, unusable. If you had data there then you lost it unless you go to a VERY EXPENSIVE data recovery company who have the needed hardware to save the data. Actually it's not even guaranteed that they can recover your data. Block is a term what Linux uses for filesystem data units. It's either 512, 1024, 2048, ... 64 kB, 128 kB, etc. Cluster is the NTFS terminology for block. It's either 512, 1024, 2048, ... 64 kB. A sector is not necessarily either dead or healthy exclusively. Depending on the OS driver, the temperature and many other things they could or could not be read. Overall, these sectors are bad but somtimes, having enough luck, they can be read. Perhaps only once and never again. They are dying. > I see that chkdsk says there are 36 KB of bad blocks (i.e., 72 > sectors). I think chkdsk reports in sectors. So you have 36 KB / 512 = 72 bad sectors. This is minimum 9, maximum 72 bad cluster. > While `badblocks` gives 128 bad blocks (sectors?). By default badblocks use 1024 bytes as block size. That means minimum minimum 128, maximum 256 bad sectors, i.e. minimum 64 KB, maximim 128 KB bad sectors. > Why this discrepency? One of these: - Windows lies about bad sectors, e.g. it didn't test the entire disk surface. - Windows can read dying disks more reliable than Linux. - You missed something and Windows didn't run chkdsk /r. But I doubt this is the case (I guess you have seen the 5 passes chkdsk running during boot, right?) > Finally why did ntfsclone exit on a read error, isn't it supposed mark > the block bad and proceed? The --rescue option does that. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-20 03:14:52
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3057075 By: gkmohan My knowledge on bad blocks is limited. First I start with a question, what constitues a bad block? Does failing to read a block more than a few times constitute bad block? I see that chkdsk says there are 36 KB of bad blocks (i.e., 72 sectors). While `badblocks` gives 128 bad blocks (sectors?). Why this discrepency? Finally why did ntfsclone exit on a read error, isn't it supposed mark the block bad and proceed? ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-19 22:16:14
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3056876 By: szaka > [root@localhost root]# ntfsclone -O /mnt/freestore/win-full.img /dev/hda3 [ ... ] > WARNING: The disk has 9 or more bad sectors (hardware faults). > Cloning NTFS ... > ERROR(5): read_all: Input/output error > > This time though we have an error. Is this a kernel bug? Good question. Windows either didn't detect this bad sector or ignored it or the Linux driver is too rigid. I guess you have the same kernel error messages as earlier. To confirm the bad sectors you can run 'badblocks /dev/hda3'. It's a read-only test. If the kernel doesn't retry reading these then perhaps it would be useful to add a new feature to ntfsclone, --retries=<number> that would retry failed read operations maximum <number> times unless it succeeds. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-19 20:25:38
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3056800 By: gkmohan Hi szaka, You should take rest and get well. Please do that. I did a chkdsk /r and tried to make an image again ---- [root@localhost root]# ntfsclone -O /mnt/freestore/win-full.img /dev/hda3 ntfsclone v2.0.0-WIP NTFS volume version: 3.1 Cluster size : 4096 bytes Current volume size: 6168956928 bytes (6169 MB) Current device size: 6168960000 bytes (6169 MB) Scanning volume ... 100.00 percent completed Accounting clusters ... Space in use : 3184 MB (51.6%) WARNING: The disk has 9 or more bad sectors (hardware faults). Cloning NTFS ... ERROR(5): read_all: Input/output error ---- This time though we have an error. Is this a kernel bug? regards, Krishna. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-19 14:51:12
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3056475 By: szaka > I am using Mandrake 10.1 Community, kernel 2.6.8.1-10mdk, I do not > know which ntfs module version this kernel uses. Ok, it has: % dmesg | grep NTFS NTFS driver 2.1.15 [Flags: R/O DEBUG MODULE]. > it is bizarre that the BadClusteRs are not marked. Yes, it is indeed strange. Because strings and grep didn't work, you could also try ntfsclone -o - win-full.img | grep BadClusteR One of the error messages below indicates that the read error was detected and the content of the unreadable sector/cluster was filled by 0x02 so the BadClusteR should be there too. What I did: - checked the source tarball you downloaded has the right ntfsclone. It has. - checked the source code for a bug that would result missing this BadClusteR signature but I couldn't find any. - checked bad sector images but they were OK. > I see from my /var/log/messages that there were lot of I/O errors like > the one below during the cloning process. Am I doing something wrong? No, everything happens as it should be. The kernel tries to read the damaged disk surface and it may or may not succeed. > ---- > Mar 17 20:50:00 localhost kernel: hda: dma_intr: status=0x51 { DriveReady > SeekComple > te Error } > Mar 17 20:50:00 localhost kernel: hda: dma_intr: error=0x40 { UncorrectableError> }, > LBAsect=51461830, sector=51461614 > Mar 17 20:50:00 localhost kernel: end_request: I/O error, dev hda, sector > 51461614 > Mar 17 20:50:00 localhost kernel: Buffer I/O error on device hda3, logical block > 3127352 > --- Yep, bad sectors. > here is the error I get when I try to access the /mnt/loop/WINDOWS > directory. > Mar 18 17:01:17 localhost kernel: NTFS-fs error (device loop0): > ntfs_readdir(): Actual VCN (0x202020202020202) of index buffer is > different from expected VCN (0x0). Directory inode 0x1c is corrupt or > driver bug. Very interesting. The 0x202020202020202 clearly indicates that originally the kernel couldn't read the given sector so ntfsclone filled the buffer by this value. How is it possible that you can still see /mnt/windows/WINDOWS using the NTFS driver? You shouldn't be able to do that. Well, one explanation could be that the NTFS driver, the Linux VFS, etc tries harder/repeatedly to read the sector and it succeeds at the 2nd, 3rd, etc attempts. Ntfsclone tries only once. I thought the kernel takes care about these things but perheps this depends on subsystems and kernel versions. I need to check this out. What you could do? Run chkdsk /r then use ntfsclone. The /r option is VERY important. This should result a full list of bad sectors stored in a NTFS file and ntfsclone and the kernel shouldn't report any error unless bad sectors develop too fast. > thanks for your patience in answering my questions It was quite rewarding, we found several problems. I must also lie in bed, having high fever instead of realizing my plans, travelling around in Tunisia so currently I can't really do much anyway ... ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-19 00:18:48
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3055854 By: gkmohan I am using Mandrake 10.1 Community, kernel 2.6.8.1-10mdk, I do not know which ntfs module version this kernel uses. you are correct, the loopback device mount is identical in size with ntfs mount /dev/hda3 6168956928 3183087616 2985869312 52% /mnt/windows /mnt/freestore/win-full.img 6168956928 3183087616 2985869312 52% /mnt/loop but it is bizarre that the BadClusteRs are not marked. I see from my /var/log/messages that there were lot of I/O errors like the one below during the cloning process. Am I doing something wrong? ---- Mar 17 20:50:00 localhost kernel: hda: dma_intr: status=0x51 { DriveReady SeekComple te Error } Mar 17 20:50:00 localhost kernel: hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=51461830, sector=51461614 Mar 17 20:50:00 localhost kernel: end_request: I/O error, dev hda, sector 51461614 Mar 17 20:50:00 localhost kernel: Buffer I/O error on device hda3, logical block 3127352 --- here is the error I get when I try to access the /mnt/loop/WINDOWS directory. Mar 18 17:01:17 localhost kernel: NTFS-fs error (device loop0): ntfs_readdir(): Actual VCN (0x202020202020202) of index buffer is different from expected VCN (0x0). Directory inode 0x1c is corrupt or driver bug. thanks for your patience in answering my questions ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-18 23:21:52
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3055786 By: szaka What distro or LiveCD do you use? Name, version? You seem to have more problems then you should ... > strings gives up without trying complaining large sizes > [root@localhost root]# strings -td /mnt/freestore/win-full.img > strings: Warning: could not locate '/mnt/freestore/win-full.img'. > reason: Value too large for defined data type Known 'strings' bug, it was fixed already. Please see e.g.: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=138494 https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=133555 > But I did just grep Good idea. > [root@localhost root]# grep BadClusteR /mnt/freestore/win-special.img > [root@localhost root]# grep BadClusteR /mnt/freestore/win-full.img > grep: memory exhausted I'm not sure if this bug is known or not but you could also try grep -boa BadClusteR image > that is (according to grep manual), win-special.img does not have > BadClusteR strings. I will try to find out a way search the file > win-full.img If no match in win-special.img then there shouldn't be in win-full.img either. This also means that you don't need to use the --rescue option. The --rescue option overcomes read errors but if no BadClusteR then you didn't have read errors. > here are the stats one /mnt/windows (df -B1 /mnt/windows) > Filesystem 1B-blocks Used Available Use% Mounted on > /dev/hda3 6168956928 3183087616 2985869312 52% /mnt/windows > > here are the reserved sizes (ls -l /mnt/freestore/*.img) > -rwx------ 1 root root 6168957440 Mar 17 22:50 /mnt/freestore/win-full.img* > -rwx------ 1 root root 3183839628 Mar 17 21:08 /mnt/freestore/win-special.im$> > here are the actual sizes (du -B1 /mnt/freestore/*.img) > 3186274304 /mnt/freestore/win-full.img > 3186958336 /mnt/freestore/win-special.img > > As specified in the ntfsclone manual, I can mount win-full.img but not > win-special.img All these values are correct. The win-full.img is a sparse file with holes and matches the partition size (minus the size of the redundant backup boot sector). > I need to be more specific here. I can access mnt/windows/WINDOWS but > not /mnt/loop/WINDOWS. That is the kernel can read the WINDOWS > directory on the mounted ntfs partition but not from the image > win-full.img mounted from a loopback device on /mnt/loop. What's the exact error message? Something in the /var/log/messages file? dmesg? What's the kernel version and the NTFS driver version? If you don't have BadClusteR then this should work fine. > Sorry for being dumb here but what happens during restore to a > partition with no bad sectors. Will BadSectoR signature still be > restored? Actually this is a good point to think about it. Currently yes, it will be restored. But this doesn't make any sense if the sectors are physically bad and can't be written. On the other hand, NTFS can store the list of bad sectors and the latest (development) version of ntfsclone will always ignore them, it doesn't try to save, nor restore them. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-18 20:11:15
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3055536 By: gkmohan win-full.img is generated using ntfsclone --rescue -o win-full.img /dev/hda3 win-special.img is generated using ntfsclone --rescue -so win-special.img /dev/hda3 --- strings -td ntfs-bad-blocks.img /mnt/freestore/winxp.img | grep BadClusteR --- strings gives up without trying complaining large sizes [root@localhost root]# strings -td /mnt/freestore/win-full.img strings: Warning: could not locate '/mnt/freestore/win-full.img'. reason: Value too large for defined data type [root@localhost root]# strings -td /mnt/freestore/win-special.img strings: Warning: could not locate '/mnt/freestore/win-special.img'. reason: Value too large for defined data type But I did just grep [root@localhost root]# grep BadClusteR /mnt/freestore/win-special.img [root@localhost root]# grep BadClusteR /mnt/freestore/win-full.img grep: memory exhausted that is (according to grep manual), win-special.img does not have BadClusteR strings. I will try to find out a way search the file win-full.img --- Please explain in more details/examples what you mean. There are several sizes. --- here are the stats one /mnt/windows (df -B1 /mnt/windows) Filesystem 1B-blocks Used Available Use% Mounted on /dev/hda3 6168956928 3183087616 2985869312 52% /mnt/windows here are the reserved sizes (ls -l /mnt/freestore/*.img) -rwx------ 1 root root 6168957440 Mar 17 22:50 /mnt/freestore/win-full.img* -rwx------ 1 root root 3183839628 Mar 17 21:08 /mnt/freestore/win-special.img* here are the actual sizes (du -B1 /mnt/freestore/*.img) 3186274304 /mnt/freestore/win-full.img 3186958336 /mnt/freestore/win-special.img As specified in the ntfsclone manual, I can mount win-full.img but not win-special.img --- > To check that everything went right I mounted the image file as a > loopback device mount /mnt/freestore/winxp.img /mnt/loop -t ntfs -o > loop=/dev/loop0 and then did a diff with the mounted ntfs partition > diff -r /mnt/loop /mnt/windows which reveals that I cannot access > /mnt/loop/WINDOWS directory. I get an I/O error when I try to access > this directory. Do you have any idea of what could have gone wrong? So it seems the kernel couldn't read the data there. If Windows can see that directory then this is a kernel bug/feature again. --- I need to be more specific here. I can access mnt/windows/WINDOWS but not /mnt/loop/WINDOWS. That is the kernel can read the WINDOWS directory on the mounted ntfs partition but not from the image win-full.img mounted from a loopback device on /mnt/loop. --- > I also have another question. What happens to the bad sectors portion > of the data when the image used for restore? The unreadable content of the disk having bad sectors is filled by 0x02 (this will change to a readable character) and a "BadClusteR" signature is written at the start of these sectors. --- Sorry for being dumb here but what happens during restore to a partition with no bad sectors. Will BadSectoR signature still be restored? ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-18 16:48:01
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3055133 By: szaka > If I wait long enough (~5 min) the system seem to recover from reading > all the bad sectors (this kernel does not seem to dump the I/O error > messages) and ntfsclone seem to finish its job. Probably the kernel tries to read the faulty sectors and it gives up after awhile. This is why the process seems to be slow. You can run strings -td ntfs-bad-blocks.img /mnt/freestore/winxp.img | grep BadClusteR to see how many bad sectors the kernel couldn't read and where they are (offset from the partition start). Unfortunately ntfsclone doesn't make a statistic about this yet. > But I have a problem again. When I tried to make an exact copy of the > partition using ntfsclone --rescue -o /mnt/freestore/winxp.img > /dev/hda3 I get an image with a size lesser than that of the > partition. Please explain in more details/examples what you mean. There are several sizes. > To check that everything went right I mounted the image file as a > loopback device mount /mnt/freestore/winxp.img /mnt/loop -t ntfs -o > loop=/dev/loop0 and then did a diff with the mounted ntfs partition > diff -r /mnt/loop /mnt/windows which reveals that I cannot access > /mnt/loop/WINDOWS directory. I get an I/O error when I try to access > this directory. Do you have any idea of what could have gone wrong? So it seems the kernel couldn't read the data there. If Windows can see that directory then this is a kernel bug/feature again. > I also have another question. What happens to the bad sectors portion > of the data when the image used for restore? The unreadable content of the disk having bad sectors is filled by 0x02 (this will change to a readable character) and a "BadClusteR" signature is written at the start of these sectors. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-18 07:31:02
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3054293 By: gkmohan Hi szaka, If I wait long enough (~5 min) the system seem to recover from reading all the bad sectors (this kernel does not seem to dump the I/O error messages) and ntfsclone seem to finish its job. But I have a problem again. When I tried to make an exact copy of the partition using ntfsclone --rescue -o /mnt/freestore/winxp.img /dev/hda3 I get an image with a size lesser than that of the partition. To check that everything went right I mounted the image file as a loopback device mount /mnt/freestore/winxp.img /mnt/loop -t ntfs -o loop=/dev/loop0 and then did a diff with the mounted ntfs partition diff -r /mnt/loop /mnt/windows which reveals that I cannot access /mnt/loop/WINDOWS directory. I get an I/O error when I try to access this directory. Do you have any idea of what could have gone wrong? I also have another question. What happens to the bad sectors portion of the data when the image used for restore? cheers, Krishna. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-17 20:46:40
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3053605 By: szaka If it still hangs then it's a kernel (device driver) problem and you should report it to the kernel developers by following the instructions at http://www.kernel.org/pub/linux/docs/lkml/reporting-bugs.html You can confirm that the kernel hangs the ntfsclone process by using strace, e.g.: strace ntfsclone -so /mnt/freestore/winxp.img /dev/hda3 You will see floods of outputs and it may take quite a while but after then the process will hang at a read(....) kernel system call. There isn't much ntfsclone could do about it. You can speed up the process considerably by saving the output into a file using strace's -o option. You can monitor it by e.g. 'tail -f file'. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-17 19:43:43
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3053485 By: gkmohan Hello szaka, I compiled the source at http://linux-ntfs.sourceforge.net/snapshots/ntfsprogs-200503060058.tar.bz2 and ran ntfsclone as ntfsclone -so /mnt/freestore/winxp.img /dev/hda3 ntfsclone --rescue -so /mnt/freestore/winxp.img /dev/hda3 It still hangs, here is the output (I saved the output before it hangs and adjusted the percentage) ntfsclone v2.0.0-WIP NTFS volume version: 3.1 Cluster size : 4096 bytes Current volume size: 6168956928 bytes (6169 MB) Current device size: 6168960000 bytes (6169 MB) Scanning volume ... 100.00 percent completed Accounting clusters ... Space in use : 3183 MB (51.6%) WARNING: The disk has 9 or more bad sectors (hardware faults). Saving NTFS to image ... 75.97 percent completed What could be going wrong? regards, Krishna. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-17 14:58:10
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3053015 By: szaka Hello Krishna! Ntfsclone indeed incorrectly handles bad blocks in the latest stable version, 1.9.4. However this issue was fixed long ago and you can get the fixes from here http://linux-ntfs.sourceforge.net/snapshots/readme.html or a statically linked binary from http://mlf.linux.rulez.org/mlf/ezaz/ntfsclone-static-20040228.tgz Please also note that there is a new option --rescue. It ignores read errors so disks having bad sectors (dying disks, as you have) can be rescued. The content of the cluster having bad sectors is filled by code '2' (this will change to a readable character) and the start of the cluster is marked as "BadClusteR". ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-17 14:57:45
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3053012 By: szaka Hello Krishna! Ntfsclone indeed incorrectly handles bad blocks in the latest stable version, 1.9.4. However this issue was fixed long ago and you can get the fixes from here http://linux-ntfs.sourceforge.net/snapshots/readme.html or a statically linked binary from http://mlf.linux.rulez.org/mlf/ezaz/ntfsclone-static-20040228.tgz Please also note that there is a new option --rescue. It ignores read errors so disks having bad sectors (dying disks, as you have) can be rescued. The content of the cluster having bad sectors is filled by code '2' (this will change to a readable character) and the start of the cluster is marked as "BadClusteR". ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-17 07:55:30
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3052379 By: gkmohan Hi, I am trying to make an image of ntfs partition (/dev/hda3) (created by windows xp home edition installation, if that matters). I installed ntfsprogs-1.9.4-1 and tried ntfsclone -so /mnt/freestore/winxp.img /dev/hda3 ntfsclone -o /mnt/freestore/winxp.img /dev/hda3 /mnt/freestore is ext3 filesystem on /dev/hda6. I am using Mandrakelinux release 10.1 (Community) for i586 Kernel 2.6.8.1-10mdk on an i686 For both commands ntfsclone freezes at 75.06%. I ran chkdsk in winxp and it showed that there are 32KB of bad blocks. Could it be possible that ntfsclone keeps reading the bad blocks in an infinite loop? regards, Krishna. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
|
From: SourceForge.net <no...@so...> - 2005-03-17 07:54:43
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3052377 By: nobody Hi, I am trying to make an image of ntfs partition (/dev/hda3) (created by windows xp home edition installation, if that matters). I installed ntfsprogs-1.9.4-1 and tried ntfsclone -so /mnt/freestore/winxp.img /dev/hda3 ntfsclone -o /mnt/freestore/winxp.img /dev/hda3 /mnt/freestore is ext3 filesystem on /dev/hda6. I am using Mandrakelinux release 10.1 (Community) for i586 Kernel 2.6.8.1-10mdk on an i686 For both commands ntfsclone freezes at 75.06%. I ran chkdsk in winxp and it showed that there are 32KB of bad blocks. Could it be possible that ntfsclone keeps reading the bad blocks in an infinite loop? regards, Krishna. ______________________________________________________________________ You are receiving this email because you elected to monitor this forum. To stop monitoring this forum, login to SourceForge.net and visit: https://sourceforge.net/forum/unmonitor.php?forum_id=44084 |
