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-10-26 04:17:52
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3399065 By: nobody Greetings. I'm trying to resize an NTFS partition, but when I do, I get conflicting reports as to whether it worked or not. I'm trying to resize an NTFS partition on a disk image. Not wanting to go through the hastle (and possible technical difficulty) of using losetup and calculating the offset of the partition, I simply booted into a guest Damn Small Linux 1.5 system under Qemu with my Windows XP (SP1, I think) disk image (windoze.img) as hda using something like this: qemu -hda windoze.img -cdrom dsl-1.5.iso -boot d Once I got it booted all the way up, I installed GCC and then NTFSProgs 1.12.1. (I had to add a symbolic link from /usr/local/lib/libntfs.so.8 to /lib/libntfs.so.8 to make it work. But I don't think that would cause a problem...) Then, I did the following: ntfsresize -i -d /dev/hda1 Which showed me that I could resize the NTFS partition (at that time about 11GB) down to about 2.5GB. I then used the following to make sure everything would go alright: ntfresize -s 5000M -n -d /dev/hda1 It returned with an all systems go. So, I then did this: ntfsresize -s 5000M -d /dev/hda1 Which worked just fine. I then shut down and restarted Qemu this time booting into Windows which happily performed its disk checking and booted. I checked the properties on disk C: and found that indeed the partition was only 5GB in size. I then decided that it would be more fun to have a smaller partition yet, so I restarted DSL and used the same method above (complete with the -i and -n checks) to resize it to closer to 4GB. Again, I booted into Windows which did its disk check and booted just fine, and found that My Computer said that the disk was only 4GB (It said precisely 3.8GB with 1.71GB free.) So, then, I decided to install ReactOS in the newly created space on the disk image. I booted up the ReactOS installation iso in Qemu using this: qemu -hda windoze.img -cdrom ReactOS.iso -boot d However, when I got to the portion of the ReactOS install that asked where I wanted to install ReactOS, it said that I had 1 partition 10590MB in size and just over 8000KB of unpartitioned space. Confused, I booted back into Windows which still insisted I had a single partition of size 3.8GB. I opened cmd in Windows and ran diskpart which said I had one hard drive that was 10.3GB, one volume of size 10.3GB, and one partition of size 10.3GB Even more confused, I rebooted Qemu into DSL again. I ran fdisk /dev/hda and found one partition on the disk 10GB in size. So, needless to say, I can't partition the 10.3-3.8=6.5GB "My Computer" insists I have unpartitioned for ReactOS. Perhaps I'm too new to partition/volume/disk image/formatting theory to be attempting this and am incorrect in my assumptions? Or is this some fluke of the system that's *not* my fault? And, when you use ntfsresize to resize a partition, does it also resize the volume containing that partition? (I had no idea there was a difference between a partition and a volume until I delved into this project.) Thanks very much for your help. I appreciate it. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-23 16:41:19
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3394931 By: nobody hi, i've installed the latest i586 rpm for Fedora 4 (i have athlon, tough im new to linux and still not sure how ix86 differs i red i586 was proper to atlhon rather than i686, anyway - not sure) and ntfs doesn't appear on "cat /proc/filesystems/" list. It it properly inslled since i've tried to reinstall it and i get "already installed!" message. I can only believe it is some ix86 problem since it is the only matter i am not sure to be correct in installation. i have an amd athlon xp-M laptop. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-22 18:33:22
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3394161 By: nobody You should add the nls option to the mount command/fstab. Type "locale charmap" in the console to find out what charset you are using. I'll assume it is "UTF-8". $ locale charmap Then mount with the following command (Replace the device and mount point to what you need): $ mount /dev/hda1 /mnt/hda1 -o nls=utf8,umask=0002 ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-22 09:31:07
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3393736 By: inightmare NTFS driver wouldn't show files that have Baltic letters in their filenames. Is there any sollution for this? I have Ubuntu with 2.6.10 kernel. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-21 18:09:46
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3393153 By: nobody Hi, thank you for your reply. I found a FreeBSD patch for ntfstools 1.9.4. http://www.freebsd.org/cgi/query-pr.cgi?pr=84048 This has succesfully compiled and installed for me but I need to check if this will solve my problem later since I dont have physical access to the machine (to plugin a ntfs driver) Gustaf Sandmark ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-21 06:56:47
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3392201 By: szaka > I use ntfsclone with FreeBSD 5.4 We don't develop and support ntfsprogs on FreeBSD at all. You must contact those people who ported it to FreeBSD. The port is incomplete, non-functional. See below. > -----cut----- > imageserver# ntfsclone --save-image -o - /dev/ad3s1 | gzip -c > pm.img.gz > ntfsclone v1.12.1 (libntfs 8:1:0) > ERROR(22): Opening '/dev/ad3s1' as NTFS failed: Invalid argument > Apparently device '/dev/ad3s1' doesn't have a valid NTFS. Maybe you selected > the whole disk instead of a partition (e.g. /dev/hda, not /dev/hda1)? > imageserver# > ---------cut---------- > > This failed? FreeBSD has problem locking block devices or something like that. It's a FreeBSD porting problem. > So I tested to use dd on the parition first. > > ---------cut---------- > imageserver# dd if=/dev/ad3s1 of=/images/FLASH/PM/pmtest.img bs=1M > 487+1 records in > 487+1 records out > 510902784 bytes transferred in 131.978711 secs (3871100 bytes/sec) > ---------cut---------- > > This worked ok.... dd doesn't lock the device. > now lets try to ntfsclone the image file. > > imageserver# ntfsclone --save-image -o - pmtest.img | gzip -c > pmtest.img.gz > ntfsclone v1.12.1 (libntfs 8:1:0) > NTFS volume version: 3.1 > Cluster size : 512 bytes > Current volume size: 510902272 bytes (511 MB) > Current device size: 510902784 bytes (511 MB) > Scanning volume ... > 100.00 percent completed > Accounting clusters ... > Space in use : 201 MB (39.2%) > Saving NTFS to image ... > 100.00 percent completed > Syncing ... > imageserver# > ---------cut---------- > Why is this way working? Because FreeBSD implemented files as files but block devices as something else. In Unix everything is file but FreeBSD makes an exception for block devices thus ntfsclone doesn't work. It's a FreeBSD kernel implementaion and porting problem. > Can anyone help me out to do the ntfsclone directly. Use Linux (LiveCD, etc), at least until somebody ports the tool correctly to FreeBSD. The above problems are not the only onces, there are more. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-20 22:26:50
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3391813 By: nobody Hello, I use ntfsclone with FreeBSD 5.4 I try to clone a CF card to disk directly via ntfsclone. -----cut----- imageserver# ntfsclone --save-image -o - /dev/ad3s1 | gzip -c > pm.img.gz ntfsclone v1.12.1 (libntfs 8:1:0) ERROR(22): Opening '/dev/ad3s1' as NTFS failed: Invalid argument Apparently device '/dev/ad3s1' doesn't have a valid NTFS. Maybe you selected the whole disk instead of a partition (e.g. /dev/hda, not /dev/hda1)? imageserver# ---------cut---------- This failed? So I tested to use dd on the parition first. ---------cut---------- imageserver# dd if=/dev/ad3s1 of=/images/FLASH/PM/pmtest.img bs=1M 487+1 records in 487+1 records out 510902784 bytes transferred in 131.978711 secs (3871100 bytes/sec) imageserver# ---------cut---------- This worked ok.... now lets try to ntfsclone the image file. imageserver# ntfsclone --save-image -o - pmtest.img | gzip -c > pmtest.img.gz ntfsclone v1.12.1 (libntfs 8:1:0) NTFS volume version: 3.1 Cluster size : 512 bytes Current volume size: 510902272 bytes (511 MB) Current device size: 510902784 bytes (511 MB) Scanning volume ... 100.00 percent completed Accounting clusters ... Space in use : 201 MB (39.2%) Saving NTFS to image ... 100.00 percent completed Syncing ... imageserver# ---------cut---------- Why is this way working? Can anyone help me out to do the ntfsclone directly. This is an OK way for me to clone CF cards but if I copy a 20GB IDE disks that 3 GB filled with ntfs files this procedure will waste time and unnecessary diskwrites. Anyone have an idea? Many Thanks Gustaf Sandmark dc ~at~ sandmark.se ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-19 23:49:05
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3390111 By: uvman Hi Raj, Your problem indeed sounds like the $MFT is badly fragmented. I have an idea on how you can check it out. It requires using ntfsinfo from the ntfsprogs suite. You can either compile it with cygwin if the system must be online, or run some Live-CD that includes ntfsprogs (example: RIP, which is less than a 30MB download) if you can get the system offline for a while. use "ntfsinfo -v -d /dev/hda1 -i 0 | grep reference" This will output the FILE record that $MFT resides on. (by the order they were allocated) If this list includes records 17-23, you probably hit the maximum. It is ok if there are duplicate lines. In this case, the logical thing for the driver would be to continue allocating high records instead of the reserved ones. It probably does not happen, and in this case I would love to know about it add a comment about this bug. In this case, you should defrag your disk with a defragger that can defrag the MFT, notify Microsoft and wait for an update. Can you post the resulting output here? It should be about 0-15 lines. (The most fragmented file on my computer is 7 lines at the moment) If you can use use "ntfsinfo -v -d /dev/hda1 -i X | grep reference" where X varies from 1 to 11 and check if one of them reports that it is using an inode from the 17-23 pool. One thing that intrigues me: You said your NTFS version is 1.3. I'm not familiar with this version. How did you get this number? What Windows version are you using? What Service Pack level? Another way would be if you can send me a copy of your metadata in private. It would include the names of the files and directory layout of your partition but not any content. That would allow me to analyze a possible cause and send you the result. Mail me in private if you are willing to do so, needs instructions on how to do so, or any other clarification about this comment. Thanks a lot for your help. -- Yuval ______________________________________________________________________ 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-10-19 19:20:09
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3389828 By: nobody Hello, We are experiencing a peculiar problem with our 80 GB hard disks which are formatted using Ontrack (to load Dynamic Disk overlay) and loaded with an image created from an NTFS (v1.3) partition with 512 bytes Cluster size. These hard disks are failing to boot up after a period of massive activity where our application is writing around 2-3 MB binary files to the Hard disk 24x7 every 10 seconds. Our application takes care of maintaining the disk size at 75% utilization, but still we see that the system fails to reboot (We have randomly scheduled system reboots) . On using a Drive examiner (DFSee) all we can see is it says that the Allocation Check has failed for all the files. I was looking at your website and found this information. Can you relate to our situation for evidence ? Is there anything else I can provide for your analysis which will help us out too? Thanks, Raj http://linux-ntfs.sourceforge.net/ntfs/files/index.html Unused Inodes On a freshly formatted volume, inodes 0x0B to 0x0F are marked as in use, but empty. Inodes 0x10 to 0x17 are marked as free and not used. This doesn't change until the volume is under a lot of stress. When the $MFT becomes very fragmented it won't fit into one FILE Record and an extension record is needed. If a new record was simply allocated at the end of the $MFT then we encounter a problem. The $DATA Attribute describing the location of the new record is in the new record. The new records are therefore allocated from inode 0x0F, onwards. The $MFT is always a minimum of 16 FILE Records long, therefore always exists. After inodes 0x0F to 0x17 are used up, higher, unreserved, inodes are used. This effect may not be limited to the $MFT, but more evidence is needed. ______________________________________________________________________ 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-10-19 08:38:24
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3388945 By: antona Hi, If you are interested in solving your problem, please send an email to the developer mailing list where such bug reports belong and not to these forums and we can see further... lin...@li... is the address. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-19 06:35:54
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3388802 By: snecklifter Hi there, I have never had a problem with large directory numbers on an NTFS drive - I would be more concerned at first with the trivial. Could you post back your /etc/fstab contents kernel version, as well as kernel-module-ntfs version. Other than that, is there any I/O on the hard drive when initially mounting the NTFS drive or is the freeze immediate. What kind of hardware are you mounting? Cheers Chris ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-19 02:54:10
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3388672 By: nobody I'm mounting an NTFS drive on Fedora core 4 with a very very large number of directories, and the ntfs driver completely jams the entire system when reading the drive. Everything freezes, meaning I have to manually power off the computer and then reboot. The driver works fine on other drives, so I'm thinking maybe it's the number of directories on this drive that's screwing up the program. Any thoughts about how to fix it so I can read this drive? ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-17 12:22:49
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3385689 By: kasperberg Often extended partitions contain one or more logical partions. If this is the case then /dev/hda2 points to this "container" partition and can not be mounted. And /dev/hda5 (to /dev/hda9 and beyond) would be your logical partitions. So you can try to mount /dev/hda5. I believe Win95 Ext'd (LBA) is a partion type telling windows that this partion is used as described above. It can contain different types of filesystems. I hope this helps. Please correct me when i'm wrong about this. Groetjes, Kasper ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-17 11:30:28
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3385612 By: nobody I have a main NTFS partition and an extended partition on the same drive. I have no problem mounting the main partition but can't figure out how to get the extended one mounted. For example, from the manual page, how would I mount hda2? What is the "type" of "Win95 Ext'd (LBA)"? /dev/hda2 2126 19851 35735616 0f Win95 Ext'd (LBA) ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-12 12:08:06
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3378892 By: nobody Everything worked :-)) ntfsresize reported no problems, chkdsk reported no problems. Everything is as it was before. I am extremely grateful to you for helping me with this! I would just like to finish what I had started. I wanted to shrink the sda6 partition and enlarge sda7. I've done the first part, but how do I enlarge sda7 "from the left" (by moving its starting sector)? I think I would have to move sda7 up to just after the sda6 ending sector and then enlarge it "from the right" (the "normal" way). How do I do that? I've been looking at the ntfsresize manual and FAQ and could not find any information on how to do this. I think this is again something that isn't really what ntfsresize is supposed to do, but could you please recommend a tool I could use to move the partition up before I can resize it with ntfsresize? ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-12 02:18:46
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3378424 By: nobody ------------------------------------------------------------------------ The prob is this...I had xp installed on my machine with 3 hdd's...all drives were ntfs and were converted to dynamic...well that was all working fine until windows crashed on me. So I reinstalled. The drive that I put windows on was formated completely and the second drive is able to be seen with all the information that was there....but the 3rd drive where all my music and movies and such was stored can no longer be accessed by windows....under disc mngr it shows the drive but it says unreadable.....so I loaded my linux cd in hopes of coping the information to another drive....no go....and from reading other posts it looks like you can't write to a ntfs disk/partition through linux...so anyone got any ideas as to what I can do to get the data off the disc so that I can reformat that drive and continue using it? I havn't found a way for windows to recongize the drive in anyway shape or form...though I'm sure there is something that I havn't done.....thanks for any help any of you can provide.... ------------------------------------------------------------------------ You can mount the NTFS partition read-write with ntfsmount. ntfsmount /dev/hda3 /mnt/win "Limited write support!" Or, if there's NTFS support in the kernel, mount it read-only. mount -t ntfs -o ro /dev/hda3 /mnt/win See if linux can access the partition and take it from there. The RIP rescue system has ntfsmount etc. http://www.tux.org/pub/people/kent-robotti/looplinux/rip ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 21:41:10
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3378205 By: nobody Hey all, I'm extremely new to linux...a friend gave me a knoppix live cd with 2.6 kernel on it.... The prob is this...I had xp installed on my machine with 3 hdd's...all drives were ntfs and were converted to dynamic...well that was all working fine until windows crashed on me. So I reinstalled. The drive that I put windows on was formated completely and the second drive is able to be seen with all the information that was there....but the 3rd drive where all my music and movies and such was stored can no longer be accessed by windows....under disc mngr it shows the drive but it says unreadable.....so I loaded my linux cd in hopes of coping the information to another drive....no go....and from reading other posts it looks like you can't write to a ntfs disk/partition through linux...so anyone got any ideas as to what I can do to get the data off the disc so that I can reformat that drive and continue using it? I havn't found a way for windows to recongize the drive in anyway shape or form...though I'm sure there is something that I havn't done.....thanks for any help any of you can provide.... jared civ...@co... ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 21:07:40
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3378171 By: szaka > And what should I use for the ending sectors? The same values as they are > now Same as now. > or the starting sector + "NumberOfSectors" from the ntfsresize output, or > something else? No. > Should I do anything between using fdisk and trying to boot into windows? Run ntfsresize -ffi <partition> and it will tell if you still have problems or did something wrong. > For example, I read somewhere I should use ntfsfix after doing anything > using the kernel driver or something like that. I'm not sure if it > applies here. It doesn't apply here, don't run it. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 20:53:29
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3378158 By: nobody And what should I use for the ending sectors? The same values as they are now or the starting sector + "NumberOfSectors" from the ntfsresize output, or something else? Should I do anything between using fdisk and trying to boot into windows? For example, I read somewhere I should use ntfsfix after doing anything using the kernel driver or something like that. I'm not sure if it applies here. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 20:49:58
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3378027 By: szaka > I don't think I will contact them since I don't know how to explain the > problem. Exactly like here ;-) > All I could say is I used the tools and made a mess out of my hard drive. > I'm pretty sure I did something wrong (although I don't think the way I I'm fairly sure you didn't. Fdisk does have this start shifting problem though I bet it's considered to be a feature, not a bug. > and ./findntfs /dev/sda > Device size: 82348277760 > NTFS signature at sector: 63 pointing to 63 > NTFS signature at sector: 11277629 pointing to 63 > NTFS signature at sector: 11791709 pointing to 63 > NTFS signature at sector: 11791777 pointing to 67 > NTFS signature at sector: 37078089 pointing to 69 > NTFS signature at sector: 39246865 pointing to 70 > NTFS signature at sector: 39246872 pointing to 70 > NTFS signature at sector: 65689784 pointing to 70 > NTFS signature at sector: 65689853 pointing to 68 > NTFS signature at sector: 65689854 pointing to 68 > NTFS signature at sector: 92775374 pointing to 68 > NTFS signature at sector: 92775445 pointing to 70 > NTFS signature at sector: 92775450 pointing to 70 > NTFS signature at sector: 160441154 pointing to 70 > 100.00 percent completed /dev/sda6 starts at sector 39246865 not 39246872 /dev/sda7 starts at sector 65689853 not 65689854 /dev/sda8 starts at sector 92775445 not 92775450 Recreate these partition entries but use the 'u' fdisk command to switch to the reliable sector unit from the default cylinder one. This is very important. Also fix the partition order if needed, as you did previously. Always partition as sector the unit, never as cylinder. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 18:47:06
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3377996 By: nobody > BTW, fundamentally this problem has nothing to do with NTFS because these > things happen with all other filesystems. So one should report these > problems and contact the fdisk, testdisk, etc developers. I don't think I will contact them since I don't know how to explain the problem. All I could say is I used the tools and made a mess out of my hard drive. I'm pretty sure I did something wrong (although I don't think the way I did it was much different from the ntfsresize FAQ). I don't have enough experience to blame the tools. To blame the tools I should first be sure that I did everything right, and I'm not sure of that. Here's ./ntfsresize -dffi /dev/sda7 ntfsresize v1.12.0 (libntfs 8:0:0) Failed to set locale, using default 'C'. Reading bootsector... ntfs_pread(): Entering for pos 0x0, count 0x200. OK Beginning bootsector check... Calculating bootsector checksum... OK Checking OEMid... OK Checking bytes per sector... OK Checking sectors per cluster... OK Checking cluster size... OK Checking reserved fields are zero... OK Checking clusters per mft record... OK Checking clusters per index block... OK Bootsector check completed successfully. SectorSize = 0x200 SectorSizeBits = 9 NumberOfSectors = 27085520 SectorsPerCluster = 0x8 MFT LCN = 0x1fb5dc MFTMirr LCN = 0x1fb60a ClusterSize = 0x1000 ClusterSizeBits = 12 ClustersPerMftRecord = 0xfffffff6 MftRecordSize = 0x400 MftRecordSizeBits = 10 ClustersPerINDXRecord = 0x1 INDXRecordSize = 0x1000 INDXRecordSizeBits = 12 mft_zone_pos = 0x1fb5dc mft_zone_start = 0x1fb5dc mft_zone_end = 0x262b07 data1_zone_pos = 0x262b07 data2_zone_pos = 0x0 Loading $MFT... ntfs_pread(): Entering for pos 0x1fb5dc000, count 0x400. Error: $MFT has invalid magic. FAILED Failed to load $MFT: Input/output error Failed to startup volume: Input/output error ERROR(5): Opening '/dev/sda7' as NTFS failed: Input/output error This software has detected that your NTFS is corrupted. Please run chkdsk /f on Windows then reboot it TWICE! Important, don't forget the /f parameter! Afterwards you can run ntfsresize. No modification was made to NTFS. and ./ntfsresize -dffi /dev/sda8 ntfsresize v1.12.0 (libntfs 8:0:0) Failed to set locale, using default 'C'. Reading bootsector... ntfs_pread(): Entering for pos 0x0, count 0x200. OK Beginning bootsector check... Calculating bootsector checksum... OK Checking OEMid... OK Checking bytes per sector... OK Checking sectors per cluster... OK Checking cluster size... OK Checking reserved fields are zero... OK Checking clusters per mft record... OK Checking clusters per index block... OK Bootsector check completed successfully. SectorSize = 0x200 SectorSizeBits = 9 NumberOfSectors = 67665704 SectorsPerCluster = 0x8 MFT LCN = 0x25b304 MFTMirr LCN = 0x3dd7c8 ClusterSize = 0x1000 ClusterSizeBits = 12 ClustersPerMftRecord = 0xfffffff6 MftRecordSize = 0x400 MftRecordSizeBits = 10 ClustersPerINDXRecord = 0x1 INDXRecordSize = 0x1000 INDXRecordSizeBits = 12 mft_zone_pos = 0x25b304 mft_zone_start = 0x25b304 mft_zone_end = 0x35d500 data1_zone_pos = 0x35d500 data2_zone_pos = 0x0 Loading $MFT... ntfs_pread(): Entering for pos 0x25b304000, count 0x400. Error: $MFT has invalid magic. FAILED Failed to load $MFT: Input/output error Failed to startup volume: Input/output error ERROR(5): Opening '/dev/sda8' as NTFS failed: Input/output error This software has detected that your NTFS is corrupted. Please run chkdsk /f on Windows then reboot it TWICE! Important, don't forget the /f parameter! Afterwards you can run ntfsresize. No modification was made to NTFS. ----- and ./findntfs /dev/sda Device size: 82348277760 NTFS signature at sector: 63 pointing to 63 NTFS signature at sector: 11277629 pointing to 63 NTFS signature at sector: 11791709 pointing to 63 NTFS signature at sector: 11791777 pointing to 67 NTFS signature at sector: 37078089 pointing to 69 NTFS signature at sector: 39246865 pointing to 70 NTFS signature at sector: 39246872 pointing to 70 NTFS signature at sector: 65689784 pointing to 70 NTFS signature at sector: 65689853 pointing to 68 NTFS signature at sector: 65689854 pointing to 68 NTFS signature at sector: 92775374 pointing to 68 NTFS signature at sector: 92775445 pointing to 70 NTFS signature at sector: 92775450 pointing to 70 NTFS signature at sector: 160441154 pointing to 70 100.00 percent completed ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 17:59:01
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3377945 By: nobody This is the error: Oct 11 19:57:02 pcabraham kernel: Initializing USB Mass Storage driver... Oct 11 19:57:02 pcabraham kernel: scsi0 : SCSI emulation for USB Mass Storage de vices Oct 11 19:57:02 pcabraham kernel: usbcore: registered new driver usb-storage Oct 11 19:57:02 pcabraham kernel: USB Mass Storage support registered. Oct 11 19:57:07 pcabraham kernel: Vendor: Maxtor 6 Model: Y160P0 R ev: YAR4 Oct 11 19:57:07 pcabraham kernel: Type: Direct-Access A NSI SCSI revision: 04 Oct 11 19:57:07 pcabraham scsi.agent[8698]: disk at /devices/pci0000:00/0000:00: 03.3/usb1/1-5/1-5:1.0/host0/target0:0:0/0:0:0:0 Oct 11 19:57:13 pcabraham kernel: usb 1-5: reset high speed USB device using ehc i_hcd and address 5 Oct 11 19:57:16 pcabraham kernel: usb 1-5: device descriptor read/64, error -110 Oct 11 19:57:24 pcabraham su(pam_unix)[8735]: session opened for user root by (u id=500) Oct 11 19:57:31 pcabraham kernel: usb 1-5: device descriptor read/64, error -110 Oct 11 19:57:31 pcabraham kernel: usb 1-5: reset high speed USB device using ehc i_hcd and address 5 Oct 11 19:57:34 pcabraham kernel: usb 1-5: device descriptor read/64, error -110 Oct 11 19:58:10 pcabraham kernel: usb 1-5: USB disconnect, address 5 Oct 11 19:58:10 pcabraham kernel: scsi: Device offlined - not ready after error recovery: host 0 channel 0 id 0 lun 0 Oct 11 19:58:10 pcabraham kernel: scsi0 (0:0): rejecting I/O to offline device Oct 11 19:58:10 pcabraham last message repeated 5 times Oct 11 19:58:10 pcabraham kernel: sda : READ CAPACITY failed. Oct 11 19:58:10 pcabraham kernel: sda : status=0, message=00, host=0, driver=04 Oct 11 19:58:10 pcabraham kernel: sda : sense not available. Oct 11 19:58:10 pcabraham kernel: sda: assuming drive cache: write through Oct 11 19:58:10 pcabraham kernel: Attached scsi disk sda at scsi0, channel 0, id 0, lun 0 Oct 11 19:58:10 pcabraham kernel: usb 1-5: new high speed USB device using ehci_hcd and address 6 Oct 11 19:58:13 pcabraham kernel: usb 1-5: device descriptor read/64, error -110 Oct 11 19:58:29 pcabraham kernel: usb 1-5: device descriptor read/64, error -110 Thanks all ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 17:44:30
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3377883 By: szaka BTW, please post the ntfsresize debug output for the other partitions too. I'm afraid when TestDisk made a worse partition table then chkdsk messed up also your NTFS data. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 17:03:08
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3377873 By: szaka > ./ntfsresize -dffi /dev/sda6 [ ... ] > Error: $MFT has invalid magic. > FAILED This is not an NTFS partition. Apparently TestDisk screwed up the partition table to be even more corrupted (this happens with other people too, unfortunately). > sda7 and sda8 also say "invalid magic", I can post their output also if you > need it. TestDisk did a highly bad job :-((( > ./findntfs /dev/sda6 You have to use the entire disk as a parameter, not a partition, e.g. /dev/sda, not /dev/sda6. It will take a while to finish but if you still have your NTFS partitions then it will find them. BTW, fundamentally this problem has nothing to do with NTFS because these things happen with all other filesystems. So one should report these problems and contact the fdisk, testdisk, etc developers. We don't develop partition mangling tools at all because there are already plenty of them but nobody else works on NTFS, only us, and we have still a lot of things to implement. ______________________________________________________________________ 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=44085 |
|
From: SourceForge.net <no...@so...> - 2005-10-11 16:11:36
|
Read and respond to this message at: https://sourceforge.net/forum/message.php?msg_id=3377835 By: nobody > 2) if logical partitions are modified then it reorders them thus greatly confusing Windows, etc. ------ Yes, fdisk reordered them, I corrected that by pressing x (extra functionality), then f (fix partition order). But the current partition table I have was written with testdisk. Here is the output of fdisk -lu: Disk /dev/sda: 82.3 GB, 82348277760 bytes 255 heads, 63 sectors/track, 10011 cylinders, total 160836480 sectors Units = sectors of 1 * 512 = 512 bytes Device Boot Start End Blocks Id System /dev/sda1 * 63 11277629 5638783+ 7 HPFS/NTFS /dev/sda2 11277630 37270799 12996585 83 Linux /dev/sda3 37286865 160826714 61769925 f W95 Ext'd (LBA) /dev/sda5 37286928 39246794 979933+ 82 Linux swap / Solaris /dev/sda6 39246872 65689784 13221456+ 7 HPFS/NTFS /dev/sda7 65689854 92775374 13542760+ 7 HPFS/NTFS /dev/sda8 92775450 160441154 33832852+ 7 HPFS/NTFS /dev/sda9 160441218 160826714 192748+ c W95 FAT32 (LBA) ----- ./ntfsresize -dffi /dev/sda6 ntfsresize v1.12.0 (libntfs 8:0:0) Failed to set locale, using default 'C'. Reading bootsector... ntfs_pread(): Entering for pos 0x0, count 0x200. OK Beginning bootsector check... Calculating bootsector checksum... OK Checking OEMid... OK Checking bytes per sector... OK Checking sectors per cluster... OK Checking cluster size... OK Checking reserved fields are zero... OK Checking clusters per mft record... OK Checking clusters per index block... OK Bootsector check completed successfully. SectorSize = 0x200 SectorSizeBits = 9 NumberOfSectors = 26442912 SectorsPerCluster = 0x8 MFT LCN = 0x98755 MFTMirr LCN = 0x98783 ClusterSize = 0x1000 ClusterSizeBits = 12 ClustersPerMftRecord = 0xfffffff6 MftRecordSize = 0x400 MftRecordSizeBits = 10 ClustersPerINDXRecord = 0x1 INDXRecordSize = 0x1000 INDXRecordSizeBits = 12 mft_zone_pos = 0x98755 mft_zone_start = 0x98755 mft_zone_end = 0xfd547 data1_zone_pos = 0xfd547 data2_zone_pos = 0x0 Loading $MFT... ntfs_pread(): Entering for pos 0x98755000, count 0x400. Error: $MFT has invalid magic. FAILED Failed to load $MFT: Input/output error Failed to startup volume: Input/output error ERROR(5): Opening '/dev/sda6' as NTFS failed: Input/output error This software has detected that your NTFS is corrupted. Please run chkdsk /f on Windows then reboot it TWICE! Important, don't forget the /f parameter! Afterwards you can run ntfsresize. No modification was made to NTFS. sda7 and sda8 also say "invalid magic", I can post their output also if you need it. ----- ./findntfs /dev/sda6 Device size: 13538771456 NTFS signature at sector: 0 pointing to 70 100.00 percent completed NTFS signature at sector: 26442912 pointing to 70 ./findntfs /dev/sda7 Device size: 13867786752 NTFS signature at sector: 0 pointing to 68 100.00 percent completed NTFS signature at sector: 27085520 pointing to 68 ./findtnfs /dev/sda8 Device size: 34644840960 NTFS signature at sector: 0 pointing to 70 100.00 percent completed NTFS signature at sector: 67665704 pointing to 70 ______________________________________________________________________ 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=44085 |
