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: Anton A. <ai...@ca...> - 2007-06-26 21:42:58
|
Hi, On 22 Jun 2007, at 10:07, Arindam wrote: > I am new to this list. I am trying to identify the OS installed on > some NTFS partitions by mounting those partitions under Linux (RHEL 4 > u3). I have been stuck in trying to identify and differentiate between > x64 and IA64 installations of Windows on such an NTFS partition. I was > wondering if it is possible to do that from Linux. > > Are there specifically any filesystem markers, or some files whose > contents can be indicative of whether it is x64 or IA64. Sorry I have no idea at all except what is the output of running the Linux "file" command on the Windows binaries? I only have 32-bit Windows so have no idea what might be displayed on the 64-bit versions... But for example running "file" on OpenSUSE 10.2 against the ntfs.sys from Windows XP SP2 gives me: ntfs.sys: MS-DOS executable PE for MS Windows (native) Intel 80386 32-bit So if you are very lucky file will tell you something like "Windows PE executable x86_64 architecture" and "Windows PE executable ia64 architecture" or something... Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: Anton A. <ai...@ca...> - 2007-06-25 07:28:06
|
Hi, On 25 Jun 2007, at 05:29, K T Ligesh wrote: > OK. I have finally isolated all my windows woes into a simple > reproducable and seemingly weird problem. I have an LV image of > 1.7GB of windows that boots perfectly. > > --------------------- > $ fdisk -ul /dev/VolGroup00/ > windows_rootimg > ~[8] > > Disk /dev/VolGroup00/windows_rootimg: 1811 MB, 1811939328 bytes > 46 heads, 45 sectors/track, 1709 cylinders, total 3538944 sectors > Units = sectors of 1 * 512 = 512 bytes > > Device Boot Start End > Blocks Id System > /dev/VolGroup00/windows_rootimg1 * 63 3538943 > 1769440+ 7 HPFS/NTFS > ------------------------- > > The above boots perfectly. > > Now I merely do lvextend /dev/VolGroup00/windows_rootimg -L+1.5G > > And that's it, the boot hangs at the very beginning itself; It > stops after printing the message "booting from harddisk". The fdisk > for the extended image is: > > --------------------- > $ fdisk -ul /dev/VolGroup00/ > windows_rootimg > ~[8] > > Disk /dev/VolGroup00/windows_rootimg: 3422 MB, 3422552064 bytes > 46 heads, 45 sectors/track, 3229 cylinders, total 6684672 sectors > Units = sectors of 1 * 512 = 512 bytes > > Device Boot Start End > Blocks Id System > /dev/VolGroup00/windows_rootimg1 * 63 3538943 > 1769440+ 7 HPFS/NTFS > -------------------- > > Why would merely extending the partition prevent it from booting, > and how do I overcome this? Well you are not extending the partition, you are effectively replacing the hard disk with a bigger one as far as Windows is concerned. That almost certainly means that the CHS values change thus the values in the NTFS boot sector are no longer valid and this Windows fails to boot. To confirm this is the case, simply install Windows from a CD or whatever on the bigger disk, then once you have done that compare the boot sectors from the smaller disk and the bigger disk. The fields of interest are the "sectors_per_track" and "heads". They are both 16-bit fields (little endian) and to be found at offset 0xd and 0xf in the bios parameter block (bpb) respectively. Adding the bpb offset inside the boot sector which is 0xb gives an absolute offset of: sectors_per_track: 0x18 (or 24 in decimal) heads: 0x1a (or 26 in decimal) Those offset are from the start of the partition thus you need to figure out the start from the disk by looking at the fdisk -ul output which shows a starting sector of 63, i.e. 63*512=32256 bytes thus the absolute offsets from the beginning of the disk are: sectors_per_track: 0x7e18 (or 32280 in decimal) heads: 0x7e1a (or 32282 in decimal) Easiest way to do this is to take a copy of the values before reinstalling windows like so: dd if=/dev/VolGroup00/windows_rootimg of=~/old-sectors_per_track.dat bs=1 count=2 skip=32280 dd if=/dev/VolGroup00/windows_rootimg of=~/old-heads.dat bs=1 count=2 skip=32282 Then reinstall windows and issue: dd if=/dev/VolGroup00/windows_rootimg of=~/new-sectors_per_track.dat bs=1 count=2 skip=32280 dd if=/dev/VolGroup00/windows_rootimg of=~/new-heads.dat bs=1 count=2 skip=32282 Now use hexdump: hexdump -C ~/old-sectors_per_track.dat hexdump -C ~/new-sectors_per_track.dat hexdump -C ~/old-heads.dat hexdump -C ~/new-heads.dat For example on my real NTFS partition I see: $ hexdump -C ~/old-sectors-per_track.dat 00000000 3f 00 |?.| 00000002 The interesting two bytes are the "3f 00" which means that the sectors per track value is 0x003f = 0x3f = 63 sectors per track and for the heads I see: $ hexdump -C ~/old-heads.dat 00000000 ff 00 |..| 00000002 Again the insteresting two bytes are the "ff 00" which means the heads value is 0x00ff = 0xff = 255 heads. I am almost certain you will see different values between old and new, i.e. Windows sees the disk as a completely different geometry thus unless you can work out how Windows determines the geometry you are screwed. Alternatively you need to figure out how your virtualization software determines the geometry and then tells it to Windows via the virtual BIOS. I am not sure how the geometry is obtained so can't tell you which of the two is doing it... Good luck! If you figure something out please let us know. A lot of people are in the position that you are in and really would like to know how to determine the geometry. Heck if we knew how to do it accurately we could put it into ntfsclone or create a new utility to fix bootability... Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: K T L. <li...@lx...> - 2007-06-25 04:13:42
|
OK. I have finally isolated all my windows woes into a simple reproducable and seemingly weird problem. I have an LV image of 1.7GB of windows that boots perfectly.
---------------------
$ fdisk -ul /dev/VolGroup00/windows_rootimg ~[8]
Disk /dev/VolGroup00/windows_rootimg: 1811 MB, 1811939328 bytes
46 heads, 45 sectors/track, 1709 cylinders, total 3538944 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/VolGroup00/windows_rootimg1 * 63 3538943 1769440+ 7 HPFS/NTFS
-------------------------
The above boots perfectly.
Now I merely do lvextend /dev/VolGroup00/windows_rootimg -L+1.5G
And that's it, the boot hangs at the very beginning itself; It stops after printing the message "booting from harddisk". The fdisk for the extended image is:
---------------------
$ fdisk -ul /dev/VolGroup00/windows_rootimg ~[8]
Disk /dev/VolGroup00/windows_rootimg: 3422 MB, 3422552064 bytes
46 heads, 45 sectors/track, 3229 cylinders, total 6684672 sectors
Units = sectors of 1 * 512 = 512 bytes
Device Boot Start End Blocks Id System
/dev/VolGroup00/windows_rootimg1 * 63 3538943 1769440+ 7 HPFS/NTFS
--------------------
Why would merely extending the partition prevent it from booting, and how do I overcome this?
Thanks a lot in advance.
|
|
From: Arindam <ari...@gm...> - 2007-06-22 09:07:17
|
Hi, I am new to this list. I am trying to identify the OS installed on some NTFS partitions by mounting those partitions under Linux (RHEL 4 u3). I have been stuck in trying to identify and differentiate between x64 and IA64 installations of Windows on such an NTFS partition. I was wondering if it is possible to do that from Linux. Are there specifically any filesystem markers, or some files whose contents can be indicative of whether it is x64 or IA64. Thanks, Arindam |
|
From: K T L. <li...@lx...> - 2007-06-22 02:10:56
|
> We try to do not change ntfsresize output without REALLY good reason. > BTW, ntfsresize source have following warning in the begging: > > * WARNING FOR DEVELOPERS!!! Several external tools grep for text messages > * to control execution thus if you would like to change any message > * then PLEASE think twice before doing so then don't modify it. Thanks! > I think you should have an option like "--i-know-what-the-heck-i-am-doing", which will not ask for confirmation. My attempts to use expect has been futile. Can you tell me the app that uses ntfsresize in the non-interactive fashion? My expect script was: --------------- spawn ntfsresize -f /dev/loop0 expect -re ".*Are you sure you want to proceed ........ " send "y\r" -------------- I used '.' instead of the actual letters, since the last few chars were all meta-characters for reguilar expressions. Searching google for "ntfsresize expect script", naturally gives me pages where 'expect' is used as a regular english word, and not the program. Thanks. |
|
From: Yura P. <pak...@gm...> - 2007-06-21 13:36:08
|
On Thu, 21 Jun 2007 at 18:35 +0530, K T Ligesh wrote:
> On Thu, Jun 21, 2007 at 01:51:40PM +0300, Yura Pakhuchiy wrote:
> > On Thu, 21 Jun 2007 at 06:57 +0530, K T Ligesh wrote:
> > > Is there someway I can run ntfsresize in a non-interactive
> > > manner? It seems that ntfsresize always asks for user confirmation
> > > before finally proceeding to the final step.
> >
> > You can write script that parses ntfsresize output and responds
> > respectively. There several ntfsresize front-ends, you can look on
> > some of them for example.
>
> Yes. I am using 'expect'. But it is very fragile, and it will depend
> on the output that ntfsresize prints, and any change means that it
> will not work. Genarally it becomes a bit more complex for debugging,
> and more chances of error, but yes, it can be done.
We try to do not change ntfsresize output without REALLY good reason.
BTW, ntfsresize source have following warning in the begging:
* WARNING FOR DEVELOPERS!!! Several external tools grep for text messages
* to control execution thus if you would like to change any message
* then PLEASE think twice before doing so then don't modify it. Thanks!
--
Best regards,
Yura
|
|
From: Anton A. <ai...@ca...> - 2007-06-21 13:02:16
|
Hi, On 19 Jun 2007, at 23:16, K T Ligesh wrote: > Actually, ntfsclone is working very fine. I created an image out > of a working windows partition, and then wrote it back, and it > booted fine. So the problem is obviously with the disk image I > created with parted. > > So can anyone tellme how to create a working windows image from > an LV? The LV should act act like a full harddisk. I have tried > with parted. The commands I ran on parted. > > ---------------- > parted /dev/VolGroup00/swindows mklabel msdos > parted /dev/VolGroup00/swindows unit s mkpart primary ntfs 0 > 6666666 set 1 boot on > --------------- > > This created a proper msdos partition on the main LV, and made it > bootable. > > This is the output of parted print. But after I ntfsclone the > image into the first partition, I am not able to boot. Any help > would be appreciated. Thanks a lot in advance. > > > > ------------------- > Model: Linux device-mapper (dm) > Disk /dev/mapper/VolGroup00-swindows: 4295MB > Sector size (logical/physical): 512B/512B > Partition Table: msdos > > Number Start End Size Type File system Flags > 1 32.3kB 3413MB 3413MB primary ntfs boot > > ------------------ What is the output of: fdisk -ul /dev/mapper/VolGroup00-swindows Also what is the output of the same command but on the volume that the partition was cloned from? Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: K T L. <li...@lx...> - 2007-06-21 13:01:35
|
I hope the devs are aware that ntfs is now integrated with fedora, and also that it has become a very important because of Xen/kvm's ability to create windows virtual machines, and linux-ntfs becomes an absolute must if you need to productively use this facility. I have read somewhere that development activity for linux-ntfs had slowed down. Is there any chance of it picking up considering the new developments with Xen? Thanks a lot. |
|
From: K T L. <li...@lx...> - 2007-06-21 12:50:11
|
On Thu, Jun 21, 2007 at 01:51:40PM +0300, Yura Pakhuchiy wrote: > On Thu, 21 Jun 2007 at 06:57 +0530, K T Ligesh wrote: > > Is there someway I can run ntfsresize in a non-interactive manner? It > > seems that ntfsresize always asks for user confirmation before finally > > proceeding to the final step. > > You can write script that parses ntfsresize output and responds > respectively. There several ntfsresize front-ends, you can look on some > of them for example. > Yes. I am using 'expect'. But it is very fragile, and it will depend on the output that ntfsresize prints, and any change means that it will not work. Genarally it becomes a bit more complex for debugging, and more chances of error, but yes, it can be done. Thanks for the response. |
|
From: Yura P. <pak...@gm...> - 2007-06-21 11:22:43
|
Not sure that this would help, but you can try using relocntfs to restore windows boot ability: http://wiki.linux-ntfs.org/doku.php?id=contrib:relocntfs -- Best regards, Yura |
|
From: Yura P. <pak...@gm...> - 2007-06-21 11:22:40
|
On Thu, 21 Jun 2007 at 06:57 +0530, K T Ligesh wrote:
> Is there someway I can run ntfsresize in a non-interactive manner? It
> seems that ntfsresize always asks for user confirmation before finally
> proceeding to the final step.
You can write script that parses ntfsresize output and responds
respectively. There several ntfsresize front-ends, you can look on some
of them for example.
--
Best regards,
Yura
|
|
From: K T L. <li...@lx...> - 2007-06-21 01:12:39
|
Hi, Is there someway I can run ntfsresize in a non-interactive manner? It seems that ntfsresize always asks for user confirmation before finally proceeding to the final step. Thanks in advance. |
|
From: K T L. <li...@lx...> - 2007-06-19 22:01:57
|
Hi, Actually, ntfsclone is working very fine. I created an image out of a working windows partition, and then wrote it back, and it booted fine. So the problem is obviously with the disk image I created with parted. So can anyone tellme how to create a working windows image from an LV? The LV should act act like a full harddisk. I have tried with parted. The commands I ran on parted. ---------------- parted /dev/VolGroup00/swindows mklabel msdos parted /dev/VolGroup00/swindows unit s mkpart primary ntfs 0 6666666 set 1 boot on --------------- This created a proper msdos partition on the main LV, and made it bootable. This is the output of parted print. But after I ntfsclone the image into the first partition, I am not able to boot. Any help would be appreciated. Thanks a lot in advance. ------------------- Model: Linux device-mapper (dm) Disk /dev/mapper/VolGroup00-swindows: 4295MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 3413MB 3413MB primary ntfs boot ------------------ |
|
From: K T L. <li...@lx...> - 2007-06-19 12:51:07
|
OK, I have read the man page, and it clearly says that ntfs does not cater to booting issues, but I am not really dealing with hardware here, but rather with LVMs of exact same configuration, and I think it is supposed to work. Here's what I did: 0) I already have a working windows logical volume, which contains a windows partition 1) I Created a new Logical Volume 2) Ran parted on it. 3) Created a new partition on the new LV 4) Made it bootable, ntfs etc. 5) Lsetupd the Old LVM on /dev/loop6 at offset 32256 6) Losetuped the new LV to /dev/loop7 at the offset 32256 7) ntfsclone -O /dev/loop7 /dev/loop6 8) Then tried to boot the new windows LV using Xen. I got this error: Disk Read Error Occured. Press Ctrl-Alt-Del to reboot. The thing is, the images, and logical volumes are all 100% identical. Can someone help me here? Thanks. |
|
From: Anton A. <ai...@ca...> - 2007-06-07 10:11:16
|
Hi, On 7 Jun 2007, at 09:16, K T Ligesh wrote: > Thanks for the reply. That solved it beautifully. First run fdisk - > lu to find the beginning of the partition, and then use losetup to > mount it. (-: > Can you just confirm these are the steps to use ntfsresize on a > windows disk image? > > a) Increase the actual disk image > > b) Use parted to fill the partition to the full hard disk image > > c) Losetup the partition to dev/loop > > d) Run ntfsresize on /dev/loop Yes, that should work as long as parted doesn't screw up the partition table in any way... I would suggest to either keep a backup of the partition table (just use "dd" to make a copy of the first 512 bytes of your disk which will contain it) or to use fdisk to be on the safe side. > Thanks a lot in advance. You are welcome. Best regards, Anton > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by DB2 Express > Download DB2 Express C - the FREE version of DB2 express and take > control of your XML. No limits. Just data. Click to get it now. > http://sourceforge.net/powerbar/db2/ > _______________________________________________ > Linux-NTFS-User mailing list > Lin...@li... > https://lists.sourceforge.net/lists/listinfo/linux-ntfs-user Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: K T L. <li...@lx...> - 2007-06-07 08:03:15
|
Thanks for the reply. That solved it beautifully. First run fdisk -lu to find the beginning of the partition, and then use losetup to mount it. Can you just confirm these are the steps to use ntfsresize on a windows disk image? a) Increase the actual disk image b) Use parted to fill the partition to the full hard disk image c) Losetup the partition to dev/loop d) Run ntfsresize on /dev/loop Thanks a lot in advance. |
|
From: Anton A. <ai...@ca...> - 2007-06-07 07:38:43
|
On 7 Jun 2007, at 08:15, Anton Altaparmakov wrote: > On 6 Jun 2007, at 23:41, K T Ligesh wrote: >> I have a file that represents an entire disk image, and not just >> a partition. If you run parted on that, I get > > Use the loo driver to create a device from the file. See "man > losetup" for details. Hint you need to use the "-o" option to > losetup to tell it the start of the partition inside the file... > Then just mount the loopback device created with NTFS and/or use > the ntfsprogs and all will be fine... Sorry that meant to say "Use the loop driver"... Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: Anton A. <ai...@ca...> - 2007-06-07 07:15:33
|
Hi, On 6 Jun 2007, at 23:41, K T Ligesh wrote: > I have a file that represents an entire disk image, and not just a > partition. If you run parted on that, I get Use the loo driver to create a device from the file. See "man losetup" for details. Hint you need to use the "-o" option to losetup to tell it the start of the partition inside the file... Then just mount the loopback device created with NTFS and/or use the ntfsprogs and all will be fine... Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: K T L. <li...@lx...> - 2007-06-06 22:28:27
|
Hi folks, I have a file that represents an entire disk image, and not just a partition. If you run parted on that, I get ------------------------ $ parted /dev/VolGroup00/windows GNU Parted 1.8.1 Using /dev/mapper/VolGroup00-windows Welcome to GNU Parted! Type 'help' to view a list of commands. (parted) print Model: Linux device-mapper (dm) Disk /dev/mapper/VolGroup00-windows: 3221MB Sector size (logical/physical): 512B/512B Partition Table: msdos Number Start End Size Type File system Flags 1 32.3kB 3216MB 3216MB primary ntfs boot (parted) quit -------------------------------- Now, I need the ntfs-prog to look inside this image and into the first partition. How can I do this? Is there some way I can access the ntfs partition inside a disk image. Btw, the above is a xen virtual machine, and I think it would be nice to have the ability to access inside the image. Thanks a lot in advance. |
|
From: Avuton O. <av...@gm...> - 2007-06-02 22:22:01
|
On 6/2/07, Anton Altaparmakov <ai...@ca...> wrote: > I think I have answered that already... Yes you did something > obviously wrong. You did not use ntfsclone to do the backup... Wow, didn't realize. Now I do, thanks for the knowledge. -- avuton -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. |
|
From: Anton A. <ai...@ca...> - 2007-06-02 19:21:49
|
Hi, On 2 Jun 2007, at 17:52, Avuton Olrich wrote: > For some time now, I've been doing a backup to a XFS partition (using > rsync snapshots) from an NTFS/Windows XP partition that I need often > backups of. A few days ago I had a hard drive loss, so I went to > restore, here are the steps I used: Bad plan, this does not give you everything. > Got a new hard drive in and: > 1) cfdisk /dev/hda (Use '07' for the type, set boot flag) > 2) mkfs.ntfs /dev/hda1 > 3) (mounted with ntfs-3g) > 4) Restored the files from my XFS backup partition > 5) Setup grub as it is on the Windows machine > > After I reboot, I select the Windows partition in grub exactly as it > was also restored and it tells me something went wrong and I need to > insert a system disk (sorry, I didn't write down the complete error > message). Expected behaviour. This can never work. Windows is very picky about what modes and attributes the system files have, whether their names are in WIN32 & DOS namespace or POSIX namespace, etc, etc. NTFS-3g will neither read nor write any of these features and even if it did rsync would not know about them thus it would not backup/ restore them. Thus your backup method cannot work. If you want to do what you do you would have to only backup your files then on the new disk install Windows from scratch and then put your files back (note NOT Windows files only the data files you added). > Luckily for me, the drive wasn't completely trashed so I got the old > hard drive and: > 1) ntfsclone'd the old drive onto the new one > 2) Used ntfsresize > > This worked perfectly. This also means I need to either figure out > what went wrong the first time, or change my backup method to a full > backup rather than a incremental backup. No full backup would be no use either. You have to use ntfsclone if you want to be able to restore it. Just copying the files cannot work. > Did I do something (obviously) wrong when trying to restore from my > XFS partition, or is this simply not supported yet? Insight? I think I have answered that already... Yes you did something obviously wrong. You did not use ntfsclone to do the backup... Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: Avuton O. <av...@gm...> - 2007-06-02 16:53:01
|
Hello, For some time now, I've been doing a backup to a XFS partition (using rsync snapshots) from an NTFS/Windows XP partition that I need often backups of. A few days ago I had a hard drive loss, so I went to restore, here are the steps I used: Got a new hard drive in and: 1) cfdisk /dev/hda (Use '07' for the type, set boot flag) 2) mkfs.ntfs /dev/hda1 3) (mounted with ntfs-3g) 4) Restored the files from my XFS backup partition 5) Setup grub as it is on the Windows machine After I reboot, I select the Windows partition in grub exactly as it was also restored and it tells me something went wrong and I need to insert a system disk (sorry, I didn't write down the complete error message). Luckily for me, the drive wasn't completely trashed so I got the old hard drive and: 1) ntfsclone'd the old drive onto the new one 2) Used ntfsresize This worked perfectly. This also means I need to either figure out what went wrong the first time, or change my backup method to a full backup rather than a incremental backup. Did I do something (obviously) wrong when trying to restore from my XFS partition, or is this simply not supported yet? Insight? Thanks, -- avuton -- Anyone who quotes me in their sig is an idiot. -- Rusty Russell. |
|
From: Jeremy L. M. <je...@em...> - 2007-05-11 18:07:50
|
First of all, thanks a ton for the response! :) On Fri, 2007-05-11 at 19:01 +0100, Anton Altaparmakov wrote: > Hi, > > On 11 May 2007, at 17:34, Jeremy L. Moles wrote: > > We are currently using the latest CVS checkout of ntfsprogs. I have > > read > > online that these should support Vista resizing fine and, in fact, the > > first few Vista machines we saw worked okay. Recently, though, all of > > the Sony, IBM/Lenovo, and Dell Vista machines we've received simply do > > not work consistently w/ any of the ntfsprogs. > > > > Without ever even booting a machine into Windows once, we netboot > > into a > > small Linux image. At this point, we ask ntfsresize to operate on the > > Vista partition. It always says that the partition is dirty and > > recommends we run chkdsk--which we can do, to no effect. (I also read > > you have to use a non-Vista chkdsk, though I have no idea how one > > would > > go about acquiring that as my Windows knowledge--and that of my > > associates--is limited only to very basic usage.) > > You likely are receving the laptops in a hibernated/suspended state > instead of a true shutdown state. This is why the volumes are dirty > and why using ntfsresize totally screws up the volume and why chkdsk > does not help. > > As an experiment to see if my guess is correct, before doing the > netboot, boot the laptop into the native on-disk Vista installation, > then shut it down (you can do this on the login screen or once logged > in, does not matter) by clicking on "Shut down options" (this is the > little arrow button on the right of the shutdown button when not > logged in and on the right of the lock button on the start menu once > logged in) and then choosing "shut down" from the menu that appears. Hmm, this is certainly something to investigate. However, we have a new policy (which we inform our customers of) of creating their first user for them, so that we can at least have access to the Vista partition. It hasn't yet changed the behavior to do a proper halt VS. just using it straight from the manufacturer. Regardless, I'll run back in the storeroom here in a bit and confirm. > By default when you click the start menu and from that you click what > looks like to be a "power off" button Vista actually hibernates > instead of shutting down. That makes it look like Vista takes hardly > any time to start/shutdown but in reality it cheats by using suspend > to disk instead. > > Now once the machine is shut down correctly, try your linux netboot > image and see if ntfsresize still complains... > > The other point worthy of note is that Vista Ultimate at least has a > built-in NTFS resizer so you can use that instead of Linux-NTFS > ntfsresize then you know it will work. Probably not what you wanted > to hear but it is worth mentioning because you may not be aware of it... We investigated this as well, but I was unable to coax the machine into resizing adequately. Apparently there are all manner of complex restore and recovery options that I simply could not disable w/out having more advanced Windows admin knowledge than I do. If I remember correctly, something to do with swap (I disabled) and shadow files (I believe I also disabled). > Best regards, Thanks again for the response! > Anton |
|
From: Anton A. <ai...@ca...> - 2007-05-11 18:01:26
|
Hi, On 11 May 2007, at 17:34, Jeremy L. Moles wrote: > We are currently using the latest CVS checkout of ntfsprogs. I have > read > online that these should support Vista resizing fine and, in fact, the > first few Vista machines we saw worked okay. Recently, though, all of > the Sony, IBM/Lenovo, and Dell Vista machines we've received simply do > not work consistently w/ any of the ntfsprogs. > > Without ever even booting a machine into Windows once, we netboot > into a > small Linux image. At this point, we ask ntfsresize to operate on the > Vista partition. It always says that the partition is dirty and > recommends we run chkdsk--which we can do, to no effect. (I also read > you have to use a non-Vista chkdsk, though I have no idea how one > would > go about acquiring that as my Windows knowledge--and that of my > associates--is limited only to very basic usage.) You likely are receving the laptops in a hibernated/suspended state instead of a true shutdown state. This is why the volumes are dirty and why using ntfsresize totally screws up the volume and why chkdsk does not help. As an experiment to see if my guess is correct, before doing the netboot, boot the laptop into the native on-disk Vista installation, then shut it down (you can do this on the login screen or once logged in, does not matter) by clicking on "Shut down options" (this is the little arrow button on the right of the shutdown button when not logged in and on the right of the lock button on the start menu once logged in) and then choosing "shut down" from the menu that appears. By default when you click the start menu and from that you click what looks like to be a "power off" button Vista actually hibernates instead of shutting down. That makes it look like Vista takes hardly any time to start/shutdown but in reality it cheats by using suspend to disk instead. Now once the machine is shut down correctly, try your linux netboot image and see if ntfsresize still complains... The other point worthy of note is that Vista Ultimate at least has a built-in NTFS resizer so you can use that instead of Linux-NTFS ntfsresize then you know it will work. Probably not what you wanted to hear but it is worth mentioning because you may not be aware of it... Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge, CB2 3QH, UK Linux NTFS maintainer, http://www.linux-ntfs.org/ |
|
From: Jeremy L. M. <je...@em...> - 2007-05-11 16:35:15
|
Hello all. :) We've been using the ntfsprogs package here for many years with great success--in fact, it's a very crucial part of our automated installation scripts we use internally. However, with the influx of Vista machines we are seeing, resizing NTFS has become literally impossible. I'll explain: We are currently using the latest CVS checkout of ntfsprogs. I have read online that these should support Vista resizing fine and, in fact, the first few Vista machines we saw worked okay. Recently, though, all of the Sony, IBM/Lenovo, and Dell Vista machines we've received simply do not work consistently w/ any of the ntfsprogs. Without ever even booting a machine into Windows once, we netboot into a small Linux image. At this point, we ask ntfsresize to operate on the Vista partition. It always says that the partition is dirty and recommends we run chkdsk--which we can do, to no effect. (I also read you have to use a non-Vista chkdsk, though I have no idea how one would go about acquiring that as my Windows knowledge--and that of my associates--is limited only to very basic usage.) Sometimes, I can run ntfsfix followed immediately by ntfsresize -f, which will refuse to boot Windows the FIRST time, but will work out okay on the second windows boot IF and _only_ IF you choose "Safe Mode (Command Prompt)." This seems to work most of the time w/ Sony machines. My question is: would it be possible to get an official developer declaration of what should and should not work? We have access to pretty much any laptop conceivable, most of which are now coming with Vista, and would be more than willing to help test in any way possible (this includes via e-mail, phone, etc.) This obviously is a high priority for us and while many of our technicians are programmers in their free time, the majority of our work time is spent doing installation and technical support--so I'm not sure how much time we could devote to actually developing ntfsprogs further. Lincoln is prepared to offer a discount to anyone interested in (or in the market for) a new laptop if we can get a real fix or guidance for this. We won't need hand-holding or anything, our expertise is enough such that one or two keywords or a simple "here's the patch, make it happen" will do. :) I would even be willing to write the required code, if the problem is understood enough. Thanks, and I hope this message isn't in violation of any rules here, or is out-of-place. We desperately want to avoid a commercial solution if possible... |
