|
|
| Applications |
| Mailing Lists |
| Miscellaneous |
| Operating Systems |
| Programming |
debian-user-digest Digest V2007 #2036
Date: Fri Jul 27 2007 - 00:24:13 EDT
Content-Type: text/plain
debian-user-digest Digest Volume 2007 : Issue 2036
Today's Topics:
Re: Weird partition arrangements and [ "Nguyen, Cuong K." <cuongkieunguyen ]
Re: Sarge: Lost # of failed logins [ Andrew Sackville-West <andrew@farwe ]
Date: Thu, 26 Jul 2007 22:51:23 -0400
From: "Nguyen, Cuong K." <cuongkieunguyen@gmail.com>
To: debian-user@lists.debian.org
Subject: Re: Weird partition arrangements and broken GRUB
Message-ID: <b36fe63b0707261951p5f996cf4m49427edb4b574f4e@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="----=_Part_121_30735563.1185504683786"
------=_Part_121_30735563.1185504683786
Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 7/26/07, Hamza Saglam <hamzasaglam@googlemail.com> wrote:
>
> Hi KC,
>
> Thanks for your suggestions. I have removed the boot flag from sda1
> (while keeping it on sda5) and changed the Windows 'root' to (hd0,4),
> but unfortunately I still get the dreaded 'Filesystem type unknown,
> partition type 0x7' message.
>
I have read somewhere else that Windows could only boot from a primary
> partition, I don't know if that is the issue here but do you think it
> might be related?
Yes, in mine, XP is in primary partition. But after reviewing your table, I guess you have a bad partition table (I do not see sda4 anywhere). Here is some suggestions:
- Try replacing root with rootnoverify in XP partition. So it will read:
title Microsoft Windows XP rootnoverify (hd0,4)
savedefault
makeactive
chainloader +1
2. If the above does not work, then you may have bad master boot record. Try to fix it with Windows XP Installation CD, when booting with the CD, choose Recovery Mode to go to Console, and try fixboot and fixmbr. Those commands will try to reset your boot record of XP partition.
Good luck :)
KC.
Someone, through another channel, suggested me to use /dev/sda1's
> bootloader to boot into Windows XP, but seeing that /dev/sda1 contains
> a crippled WinPE recovery application, I don't think it will really
> work.
>
>
> Suggestions would be much appreciated,
>
> Thanks.
>
> On 7/27/07, Nguyen, Cuong K. <cuongkieunguyen@gmail.com> wrote:
> >
> >
> >
> > On 7/26/07, Hamza Saglam <hamzasaglam@googlemail.com> wrote:
> > >
> > > Hi,
> > >
> > > After reading dozens of GRUB tutorials for a good few hours and not
> > > getting anywhere, I've decided to post on this mailing list regarding
> > > my problem. If it has been covered before please pardon me, I really
> > > can't see it :(
> > >
> > > Now before I start, I'd like to point out that we are both debian
> > > users both due to the nature of our work, we have to have a windows
> > > installation on our machines. Sad but true :(
> > >
> > > A friend of mine brought in his laptop after he said he couldn't get
> > > 'windows booting', and when I had a look at the partition table using
> > > gparted, I was presented with the following monstrosity:
> > >
> > > screenshot:
> > > http://***image.***bayimg.***com/oaeikaabk.jpg
> > > (please get rid of the 9 stars, the mailing list wouldn't accept my
> > > message without these)
> > >
> > >
> > > (for the text based readers), it looks a bit like:
> > > /dev/sda1 fat32 (boot)
> > > /dev/sda2 extended (lba)
> > > /dev/sda5 ntfs (boot)
> > > /dev/sda6 linux-swap
> > > /dev/sda3 ext3
> > >
> > > The first fat32 partition is the recovery files that came with the
> > > laptop, the rest is a bit of mess really :)
> > >
> > > Relevant bits from /boot/grub/menu.lst:
> > >
> > > title Debian GNU/Linux, kernel 2.6.18-4-686
> > > root (hd0,2)
> > > kernel /boot/vmlinuz-2.6.18-4-686
> > root=/dev/sda3 ro
> > > initrd /boot/initrd.img- 2.6.18-4-686
> > > savedefault
> > >
> > > title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user
> mode)
> > > root (hd0,2)
> > > kernel /boot/vmlinuz- 2.6.18-4-686
> > root=/dev/sda3 ro single
> > > initrd /boot/initrd.img- 2.6.18-4-686
> > > savedefault
> > >
> > > title Microsoft Windows XP
> > > root (hd0,3)
> > > savedefault
> > > makeactive
> > > chainloader +1
> > >
> > > title Acer eRecovery Management
> > > root (hd0,0)
> > > savedefault
> > > makeactive
> > > chainloader +1
> > >
> > >
> > > I've tried all the possible combinations for the root directive of the
> > > Windows section, but it doesn't want to load windows.
> > >
> > > Is there any way I can address the ntfs partition within that extended
> > > partition, or do I need to modify the structure. (I'd very much prefer
> > > not changing the structure, even though it is quite messy)
> > >
> > >
> > > I am stuck so any help would be much appreciated.
> > >
> > > Many thanks.
> > > Hamza
> > >
> > >
> > > --
> > > To UNSUBSCRIBE, email to
> > debian-user-REQUEST@lists.debian.org
> > > with a subject of "unsubscribe". Trouble? Contact
> > listmaster@lists.debian.org
> > >
> > >
> >
> > If you look at my partition table, you may call it "messier" or
> "weirder":
> >
> > Disk /dev/sda: 100.0 GB, 100030242816 bytes
> > 255 heads, 63 sectors/track, 12161 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> >
> > Device Boot Start End Blocks Id System
> > /dev/sda1 1 784 6297448+ 12 Compaq
> diagnostics
> > /dev/sda2 * 785 3356 20659590 7 HPFS/NTFS
> > /dev/sda3 4507 12161 61488787+ f W95 Ext'd (LBA)
> > /dev/sda4 3357 4506 9237375 7 HPFS/NTFS
> > /dev/sda5 4507 7064 20547103+ 83 Linux
> > /dev/sda6 7065 7203 1116486 82 Linux swap /
> Solaris
> > /dev/sda7 11974 12161 1510078+ 82 Linux swap /
> Solaris
> > /dev/sda8 7204 9635 19535008+ 83 Linux
> > /dev/sda9 9636 11973 18779953+ 83 Linux
> >
> > Partition table entries are not in disk order
> >
> > And here is the menu.lst
> >
> > ## ## End Default Options ##
> >
> > title Ubuntu, kernel 2.6.20-16-generic
> > root (hd0,7)
> > kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro quiet
> splash
> > initrd /boot/initrd.img-2.6.20-16-generic
> > quiet
> > savedefault
> >
> > title Ubuntu, kernel 2.6.20-16-generic (recovery mode)
> > root (hd0,7)
> > kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro single
> > initrd /boot/initrd.img- 2.6.20-16-generic
> >
> > title Ubuntu, kernel 2.6.20-15-generic
> > root (hd0,7)
> > kernel /boot/vmlinuz-2.6.20-15-generic
> > root=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro quiet
> > splash break=top
> > initrd /boot/initrd.img- 2.6.20-15-generic
> > quiet
> > savedefault
> >
> > title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
> > root (hd0,7)
> > kernel /boot/vmlinuz-2.6.20-15-generic
> > root=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro single
> > initrd /boot/initrd.img-2.6.20-15-generic
> >
> > title Ubuntu, memtest86+
> > root (hd0,7)
> > kernel /boot/memtest86+.bin
> > quiet
> >
> > ### END DEBIAN AUTOMAGIC KERNELS LIST
> >
> > # This is a divider, added to separate the menu items below from the
> Debian
> > # ones.
> > title Other operating systems:
> > root
> >
> >
> > # This entry automatically added by the Debian installer for a non-linux
> OS
> > # on /dev/hda1
> > title Windows NT/2000/XP Recovery
> > root (hd0,0)
> > savedefault
> > makeactive
> > chainloader +1
> >
> >
> > # This entry automatically added by the Debian installer for a non-linux
> OS
> > # on /dev/hda2
> > title Microsoft Windows XP Professional
> > root (hd0,1)
> > savedefault
> > makeactive
> > chainloader +1
> >
> >
> > # This entry automatically added by the Debian installer for an existing
> > # linux installation on /dev/hda5.
> > title Mandriva 2007 (on /dev/hda5)
> > root (hd0,4)
> > kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6
> splash=silent
> > initrd /boot/initrd.img
> > savedefault
> > boot
> >
> >
> > # This entry automatically added by the Debian installer for an existing
> > # linux installation on /dev/hda5.
> > title Mandriva 2007 (recovery mode) (on /dev/hda5)
> > root (hd0,4)
> > kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6
> > initrd /boot/initrd.img
> > savedefault
> > boot
> >
> >
> > # This entry automatically added by the Debian installer for an existing
> > # linux installation on /dev/hda5.
> > title failsafe (on /dev/hda5)
> > root (hd0,4)
> > kernel /boot/vmlinuz root=/dev/hda5 failsafe resume=/dev/hda6
> > initrd /boot/initrd.img
> > savedefault
> > boot
> >
> > Very similar to your case: I have one Recovery partition (sda1), one
> Windows
> > XP Pro, one Ubuntu box, and one Mandriva box. Everything works just
> fine: by
> > selecting on the boot menu, I can boot into any OS I want.
> >
> > As about your case, here is my suggestion for menu.lst (not sure it will
> > work, but worth giving a try)
> >
> > title Debian GNU/Linux, kernel 2.6.18-4-686
> > root (hd0,2)
> > kernel /boot/vmlinuz- 2.6.18-4-686 root=/dev/sda3 ro
> > initrd /boot/initrd.img- 2.6.18-4-686
> > savedefault
> >
> > title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user
> mode)
> > root (hd0,2)
> > kernel /boot/vmlinuz- 2.6.18-4-686 root=/dev/sda3 ro single
> > initrd /boot/initrd.img- 2.6.18-4-686
> > savedefault
> >
> > title Microsoft Windows XP
> > root (hd0,4)
> > savedefault
> > makeactive
> > chainloader +1
> >
> > title Acer eRecovery Management
> > root (hd0,0)
> > savedefault
> > makeactive
> > chainloader +1
> >
> > The only change here is for XP partition: root (hd0,4) not (hd0,3)
> because
> > your ntfs partition is sda5. Also, you may need just one partition to be
> > bootable like me (you have two bootable).
> >
> > Hope that this can help,
> >
> > KC.
> >
>
------=_Part_121_30735563.1185504683786
Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline
On 7/26/07, <b class="gmail_sendername">Hamza Saglam</b> <<a href="mailto:hamzasaglam@googlemail.com">hamzasaglam@googlemail.com</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi KC,<br><br>Thanks for your suggestions. I have removed the boot flag from sda1<br>(while keeping it on sda5) and changed the Windows 'root' to (hd0,4),<br>but unfortunately I still get the dreaded 'Filesystem type unknown,
partition type 0x7' message.I have read somewhere else that Windows could only boot from a primary
partition, I don't know if that is the issue here but do you think it
might be related?
Yes, in mine, XP is in primary partition. But after reviewing your table, I guess you have a bad partition table (I do not see sda4 anywhere). Here is some suggestions:
1. Try replacing root with rootnoverify in XP partition. So it will read:
title Microsoft Windows XP
rootnoverify (hd0,4)
savedefault
makeactive<br>
chainloader +1</span><br></div><br>2. If the above does not work, then you may have bad master boot record. Try to fix it with Windows XP Installation CD, when booting with the CD, choose Recovery Mode to go to Console, and try fixboot and fixmbr. Those commands will try to reset your boot record of XP partition.hamzasaglam@googlemail.com</a>> wrote:<br>> ><br>> > Hi,<br>> ><br>> > After reading dozens of GRUB tutorials for a good few hours and not<br>> > getting anywhere, I've decided to post on this mailing list regarding
Good luck :)
KC.Someone, through another channel, suggested me to use /dev/sda1's
bootloader to boot into Windows XP, but seeing that /dev/sda1 contains
a crippled WinPE recovery application, I don't think it will really
work.
Suggestions would be much appreciated,
Thanks.
On 7/27/07, Nguyen, Cuong K. <cuongkieunguyen@gmail.com> wrote:
>
>
>
> On 7/26/07, Hamza Saglam <2.6.18-4-686<br>> root=/dev/sda3 ro<br>> > initrd /boot/initrd.img- 2.6.18-4-686<br>> > savedefault<br>> ><br>> > title Debian GNU/Linux, kernel 2.6.18-4-686 (single-user mode)
> > my problem. If it has been covered before please pardon me, I really
> > can't see it :(
> >
> > Now before I start, I'd like to point out that we are both debian
> > users both due to the nature of our work, we have to have a windows
> > installation on our machines. Sad but true :(
> >
> > A friend of mine brought in his laptop after he said he couldn't get
> > 'windows booting', and when I had a look at the partition table using
> > gparted, I was presented with the following monstrosity:
> >
> > screenshot:
> > http://***image.***bayimg.***com/oaeikaabk.jpg
> > (please get rid of the 9 stars, the mailing list wouldn't accept my
> > message without these)
> >
> >
> > (for the text based readers), it looks a bit like:
> > /dev/sda1 fat32 (boot)
> > /dev/sda2 extended (lba)
> > /dev/sda5 ntfs (boot)
> > /dev/sda6 linux-swap
> > /dev/sda3 ext3
> >
> > The first fat32 partition is the recovery files that came with the
> > laptop, the rest is a bit of mess really :)
> >
> > Relevant bits from /boot/grub/menu.lst:
> >
> > title Debian GNU/Linux, kernel 2.6.18-4-686
> > root (hd0,2)
> > kernel /boot/vmlinuz-<br>> > Windows section, but it doesn't want to load windows.<br>> ><br>> > Is there any way I can address the ntfs partition within that extended<br>> > partition, or do I need to modify the structure. (I'd very much prefer
> > root (hd0,2)
> > kernel /boot/vmlinuz- 2.6.18-4-686
> root=/dev/sda3 ro single
> > initrd /boot/initrd.img- 2.6.18-4-686
> > savedefault
> >
> > title Microsoft Windows XP
> > root (hd0,3)
> > savedefault
> > makeactive
> > chainloader +1
> >
> > title Acer eRecovery Management
> > root (hd0,0)
> > savedefault
> > makeactive
> > chainloader +1
> >
> >
> > I've tried all the possible combinations for the root directive of the<br>><br>> Partition table entries are not in disk order<br>><br>> And here is the menu.lst<br>><br>> ## ## End Default Options ##<br>><br>> title Ubuntu, kernel 2.6.20-16-generic<br>> root (hd0,7) <br>> kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro quiet splash<br>> initrd /boot/initrd.img-2.6.20-16-generic<br>> quiet<br>> savedefault<br>><br>> title Ubuntu, kernel
> > not changing the structure, even though it is quite messy)
> >
> >
> > I am stuck so any help would be much appreciated.
> >
> > Many thanks.
> > Hamza
> >
> >
> > --
> > To UNSUBSCRIBE, email to
> debian-user-REQUEST@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact
> listmaster@lists.debian.org
> >
> >
>
> If you look at my partition table, you may call it "messier" or "weirder":
>
> Disk /dev/sda: 100.0 GB, 100030242816 bytes
> 255 heads, 63 sectors/track, 12161 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
> Device Boot Start End Blocks Id System
> /dev/sda1 1 784 6297448+ 12 Compaq diagnostics
> /dev/sda2 * 785 3356 20659590 7 HPFS/NTFS
> /dev/sda3 4507 12161 61488787+ f W95 Ext'd (LBA)
> /dev/sda4 3357 4506 9237375 7 HPFS/NTFS
> /dev/sda5 4507 7064 20547103+ 83 Linux
> /dev/sda6 7065 7203 1116486 82 Linux swap / Solaris
> /dev/sda7 11974 12161 1510078+ 82 Linux swap / Solaris
> /dev/sda8 7204 9635 19535008+ 83 Linux
> /dev/sda9 9636 11973 18779953+ 83 Linux2.6.20-16-generic (recovery mode)(single-user mode)<br>> root (hd0,2)<br>> kernel /boot/vmlinuz- 2.6.18-4-686 root=/dev/sda3 ro single<br>> initrd /boot/initrd.img- 2.6.18-4-686<br>> savedefault<br>><br>
> root (hd0,7)
> kernel /boot/vmlinuz-2.6.20-16-generic root=/dev/sda8 ro single
> initrd /boot/initrd.img- 2.6.20-16-generic
>
> title Ubuntu, kernel 2.6.20-15-generic
> root (hd0,7)
> kernel /boot/vmlinuz-2.6.20-15-generic
> root=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro quiet
> splash break=top
> initrd /boot/initrd.img- 2.6.20-15-generic
> quiet
> savedefault
>
> title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
> root (hd0,7)
> kernel /boot/vmlinuz-2.6.20-15-generic
> root=UUID=3ce886e2-7b3d-4803-ba0e-19a605fb1153 ro single
> initrd /boot/initrd.img-2.6.20-15-generic
>
> title Ubuntu, memtest86+
> root (hd0,7)
> kernel /boot/memtest86+.bin
> quiet
>
> ### END DEBIAN AUTOMAGIC KERNELS LIST
>
> # This is a divider, added to separate the menu items below from the Debian
> # ones.
> title Other operating systems:
> root
>
>
> # This entry automatically added by the Debian installer for a non-linux OS
> # on /dev/hda1
> title Windows NT/2000/XP Recovery
> root (hd0,0)
> savedefault
> makeactive
> chainloader +1
>
>
> # This entry automatically added by the Debian installer for a non-linux OS
> # on /dev/hda2
> title Microsoft Windows XP Professional
> root (hd0,1)
> savedefault
> makeactive
> chainloader +1
>
>
> # This entry automatically added by the Debian installer for an existing
> # linux installation on /dev/hda5.
> title Mandriva 2007 (on /dev/hda5)
> root (hd0,4)
> kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6 splash=silent
> initrd /boot/initrd.img
> savedefault
> boot
>
>
> # This entry automatically added by the Debian installer for an existing
> # linux installation on /dev/hda5.
> title Mandriva 2007 (recovery mode) (on /dev/hda5)
> root (hd0,4)
> kernel /boot/vmlinuz root=/dev/hda5 resume=/dev/hda6
> initrd /boot/initrd.img
> savedefault
> boot
>
>
> # This entry automatically added by the Debian installer for an existing
> # linux installation on /dev/hda5.
> title failsafe (on /dev/hda5)
> root (hd0,4)
> kernel /boot/vmlinuz root=/dev/hda5 failsafe resume=/dev/hda6
> initrd /boot/initrd.img
> savedefault
> boot
>
> Very similar to your case: I have one Recovery partition (sda1), one Windows
> XP Pro, one Ubuntu box, and one Mandriva box. Everything works just fine: by
> selecting on the boot menu, I can boot into any OS I want.
>
> As about your case, here is my suggestion for menu.lst (not sure it will
> work, but worth giving a try)
>
> title Debian GNU/Linux, kernel 2.6.18-4-686
> root (hd0,2)
> kernel /boot/vmlinuz- 2.6.18-4-686 root=/dev/sda3 ro
> initrd /boot/initrd.img- 2.6.18-4-686
> savedefault
>
> title Debian GNU/Linux, kernel 2.6.18-4-686> title Microsoft Windows XP
> root (hd0,4)
> savedefault
> makeactive
> chainloader +1
>
> title Acer eRecovery Management
> root (hd0,0)
> savedefault
> makeactive
> chainloader +1
>
> The only change here is for XP partition: root (hd0,4) not (hd0,3) because
> your ntfs partition is sda5. Also, you may need just one partition to be
> bootable like me (you have two bootable).
>
> Hope that this can help,
>
> KC.
>
------=_Part_121_30735563.1185504683786--
Date: Thu, 26 Jul 2007 20:44:49 -0700
From: Andrew Sackville-West <andrew@farwestbilliards.com>
To: debian-user@lists.debian.org
Subject: Re: Sarge: Lost # of failed logins
Message-ID: <20070727034449.GK31753@localhost.localdomain>
Content-Type: multipart/signed; micalg=pgp-sha1;
protocol="application/pgp-signature"; boundary="rwbb4r/vLufKlfJs" Content-Disposition: inline
--rwbb4r/vLufKlfJs
Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable
On Thu, Jul 26, 2007 at 05:52:00PM -0600, Bob Proulx wrote:
> Florian Kulzer wrote:
> > I have been using Debian for about 5 years now. As far as I remember, it
> > always had the "n failure(s) since last login" message (if n was greater
> > than zero).
>=20
> I have never seen that message.
it works reliably on this particular up-to-date sid box, shows the proper number of failures. I think it must come from login, but I can't see what might cause to happen or not.
>=20
> > I never had to do anything to set it up, therefore I
> > unfortunately don't know exactly how it works. My best guess is that it
> > involves some PAM modules which parse /var/log/faillog and/or use the
> > "faillog" command. Maybe this link helps to track it down:
>=20
> I always have a ~/.hushlogin. When I remove it I still never see
> failures. I see this instead:
>=20
> Last login: Thu Jul 26 17:32:14 2007 from dementia.proulx.com
>=20
> If you create a .hushlogin file for you does your login failure
> message at login go away?
>=20
> touch ~/.hushlogin
>=20
I see _nothing_ with a ~/.hushlogin and everything: motd, Last login, failures etc, without ~/.hushlogin
> The sshd uses the presence of .hushlogin to silence the banner. In
> the sshd man page:
>=20
> 1. If the login is on a tty, and no command has been specified,
> prints last login time and /etc/motd (unless prevented in the
> configuration file or by $HOME/.hushlogin; see the FILES section).
>=20
I do _not_ get this message over ssh, so it must come from that pair -- login or getty...
A
--rwbb4r/vLufKlfJs
Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQFGqWoxaIeIEqwil4YRAtl9AKCeoh1AaPT3SvcKAbH1QP989kSehgCgu28y
/fsoXn9kXgfZ+aXZ3sQl7MA=
=P6nd
-----END PGP SIGNATURE-----
--rwbb4r/vLufKlfJs--
End of debian-user-digest Digest V2007 Issue #2036
Received on Fri Jul 27 00:21:52 2007
This archive was generated by hypermail 2.1.8 : Thu Aug 09 2007 - 19:05:31 EDT
|
Contact Us Legal Notices Order Services Online Pantek Home Privacy Policy IT news Site Map Pantek Library |