Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 13:45, Glen Barber g...@freebsd.org wrote: Mostly what I was getting at here was ensuring the first blocks of the memory stick did not contain actual data. Though, I fear other forces may be at play here with GPT... There are. We've lost this round; let's just throw MBR back onto the memstick images and then focus these boot related issues to fixing the bootloader. :) Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sat, Oct 8, 2011 at 11:03 PM, Adrian Chadd adr...@freebsd.org wrote: On 9 October 2011 13:45, Glen Barber g...@freebsd.org wrote: Mostly what I was getting at here was ensuring the first blocks of the memory stick did not contain actual data. Though, I fear other forces may be at play here with GPT... There are. We've lost this round; let's just throw MBR back onto the memstick images and then focus these boot related issues to fixing the bootloader. :) Another data point. It appears USB related. I have built a GPT system on a SATA drive on a Lenovo T520. Works just fine. Always has. I copied the system onto a USB drive of the same size, not with dd of the disk, but by using gpart(8) to set up the disk including pmbr and gptmbr, just like I did on the SATA drive and then used dd to copy y\the partitions. I did this just to avoid issues with thefinal block as, while both drives are 750GB, they are different models Well, the Lenovo refuses to boot from the USB drive. It does not show up in the list of possible boot devices. I looks like this is an issue with GPT on USB devices, though I could well be missing another explanation. -- R. Kevin Oberman, Network Engineer - Retired E-mail: kob6...@gmail.com ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
One issue that has not come up on the emailing list is that dd, designed to work with memsticks of various capacities, can not make the backup gpt at the end of the memstick. Partition is just big enough to hold the data, and I ran out of inodes at times due to the installer writing to /tmp on the memstick. Maybe a script to put a backup GPT at the end on the memstick, and make the second partition fill the space available so as not to be too tightly squeezed? Tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 19:54, Thomas Mueller mueller6...@bellsouth.net wrote: One issue that has not come up on the emailing list is that dd, designed to work with memsticks of various capacities, can not make the backup gpt at the end of the memstick. Partition is just big enough to hold the data, and I ran out of inodes at times due to the installer writing to /tmp on the memstick. Maybe a script to put a backup GPT at the end on the memstick, and make the second partition fill the space available so as not to be too tightly squeezed? A script is a kludge. As we have no need for larger than 2TiB install images we should use the POLA and continue to support dd writing our memstick images which means don't use GPT for them. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 13:20, Thomas K. f...@gothschlampen.com wrote:
On Sat, Oct 08, 2011 at 07:28:55PM -0600, Warren Block wrote:
On Sun, 9 Oct 2011, Matt Thyer wrote:
On Oct 9, 2011 11:04 AM, Nathan Whitehorn nwhiteh...@freebsd.org
wrote:
On 10/08/11 19:25, Matt Thyer wrote:
There is also the interesting question of actually installing to GPT on
the hard disk, which is the default in 9.0. Does this not work on some
systems? If so, do we want to blacklist
them and use a different default partition scheme? Can we identify
systems that violate regular PC boot standards and reject GPT? Any data on
any of these points would be appreciated.
I don't think there have been any reports of failure to boot properly
formatted GPT yet.
Lenovo T420S and T520, from the links above. Install GPT on the
hard drive, try to boot.
http://forums.freebsd.org/showthread.php?t=26304
http://forums.freebsd.org/showthread.php?t=26759
http://forum.thinkpads.com/viewtopic.php?f=9t=98078
As I used parted from Linux to fix the alternate GPT, i.e. put it not at
the
end of the image data but on the end of the disk, and it still did not
appear
in the boot device list, the Acer AX3960 should probably be on the list
as well.
Being a Core i7 2600k system maybe 6 months old, it's rather recent
hardware,
but doesn't boot from the memstick image.
Regards,
Thomas
Failure to boot the FreeBSD 9.0-BETA{2|3} memstick images does not indicate
a problem with a PCs BIOS/UEFI as these images are not properly formatted.
If we were able to come up with examples of BIOS/UEFI that cannot boot from
GPT partitioned volumes there would not be a problem as long as bsdinstall
still supports partitioning volumes with MSDOS/MBR partitioning schemes.
The big problem is being able to launch the installation process to start
with which is yet another reason to have the memstick image non-GPT even if
you could work out a script/kludge etc to be able to write a properly
formatted GPT memstick.
The solution to this issue is obvious.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 19:10, Matt Thyer matt.th...@gmail.com wrote:
Failure to boot the FreeBSD 9.0-BETA{2|3} memstick images does not indicate
a problem with a PCs BIOS/UEFI as these images are not properly formatted.
Accepted.
If we were able to come up with examples of BIOS/UEFI that cannot boot from
GPT partitioned volumes there would not be a problem as long as bsdinstall
still supports partitioning volumes with MSDOS/MBR partitioning schemes.
The big problem is being able to launch the installation process to start
with which is yet another reason to have the memstick image non-GPT even if
you could work out a script/kludge etc to be able to write a properly
formatted GPT memstick.
The solution to this issue is obvious.
Yes, it's the current solution has a lot of unknown-how broken stuff
about it, let's revert it for 9.0 and then use the 10.0 release cycle
to do further research and testing.
:-)
adrian
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 21:44, Adrian Chadd adr...@freebsd.org wrote:
On 9 October 2011 19:10, Matt Thyer matt.th...@gmail.com wrote:
Failure to boot the FreeBSD 9.0-BETA{2|3} memstick images does not
indicate
a problem with a PCs BIOS/UEFI as these images are not properly
formatted.
Accepted.
If we were able to come up with examples of BIOS/UEFI that cannot boot
from
GPT partitioned volumes there would not be a problem as long as
bsdinstall
still supports partitioning volumes with MSDOS/MBR partitioning schemes.
The big problem is being able to launch the installation process to start
with which is yet another reason to have the memstick image non-GPT even
if
you could work out a script/kludge etc to be able to write a properly
formatted GPT memstick.
The solution to this issue is obvious.
Yes, it's the current solution has a lot of unknown-how broken stuff
about it, let's revert it for 9.0 and then use the 10.0 release cycle
to do further research and testing.
Unfortunately there is no reasonable revert path here. bsdinstall is the
way forward and I agree it should be the installer for 9.0-RELEASE.
Currently bsdinstall relies on labels and that's a good thing (intelligent
design choice).
Work is already underway to make the memstick issue with UFS labels and
MSDOS/MBR partitioning and when that's done this issue will be solved.
So it's not a matter of reverting, it's a matter of forging ahead and
delaying the release as this is a show stopper.
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
Oh, I wasn't suggesting reverting bsdinstall before 9.0. That'll make it a bit annoying to install on USB flash drives for some devices. It may be worthwhile to do at a later date though. I do find myself doing USB 9.0 installs just to test out the release without destroying a physical disk. But yes, I'm really only advocating MBR for memstick USB images. adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Memstick image differences between 8.x and 9.x
Hello, a while ago I downloaded a then current FreeBSD 9 current memstick image and wrote it to an USB pen drive. It didn't boot, but also showed no error. It just did not appear in the list of devices to boot from, after pressing F12 after POST on this box. I thought maybe the pen drive was bad or unbootable or something, and forgot about it. This was for playing around with ZFS, so I went with FreeBSD 8.1 back then. No problems. With FreeBSD 9.0-BETA3 I tried again on another pen drive (known to work ok), same result. It just does not appear in the list of devices to boot from when pressing F12 after POST. Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? I didn't really investigate this issue any further than described, just being curious. Regards, Thomas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sat, Oct 8, 2011 at 8:52 AM, Thomas K. f...@gothschlampen.com wrote: Hello, a while ago I downloaded a then current FreeBSD 9 current memstick image and wrote it to an USB pen drive. It didn't boot, but also showed no error. It just did not appear in the list of devices to boot from, after pressing F12 after POST on this box. I thought maybe the pen drive was bad or unbootable or something, and forgot about it. This was for playing around with ZFS, so I went with FreeBSD 8.1 back then. No problems. With FreeBSD 9.0-BETA3 I tried again on another pen drive (known to work ok), same result. It just does not appear in the list of devices to boot from when pressing F12 after POST. Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? I didn't really investigate this issue any further than described, just being curious. The new memstick image uses GPT instead of MBR partitioning. -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 10/8/11 2:21 PM, Garrett Cooper wrote: Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? The new memstick image uses GPT instead of MBR partitioning. GPT should have no impact on booting from the memory stick, as far as I am aware. Thomas, can you please zero out the beginning of the 1024 bytes of your memory stick, as follows (please take care to note the actual device for your memory stick, and change '/dev/da0' below, as appropriate): dd if=/dev/zero of=/dev/da0 bs=1024 count=1 Then re-write the memory stick per the instructions in the Handbook. Newly added to this section of the Handbook was a note to ensure the device is _not_ mounted (either manually, or automatically). http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/install-pre.html#INSTALL-BOOT-MEDIA Please let us know if this helps. -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 2:21 PM, Garrett Cooper wrote: Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? The new memstick image uses GPT instead of MBR partitioning. GPT should have no impact on booting from the memory stick, as far as I am aware. Memory stick should not be a problem, but some of the Lenovo notebooks hate GPT, even with a PMBR: http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 10/8/11 5:40 PM, Warren Block wrote: On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 2:21 PM, Garrett Cooper wrote: Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? The new memstick image uses GPT instead of MBR partitioning. GPT should have no impact on booting from the memory stick, as far as I am aware. Memory stick should not be a problem, but some of the Lenovo notebooks hate GPT, even with a PMBR: http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 Ugh, that's annoying. I'm half-tempted to note this in the new installer chapter, but I don't like the idea of such edge cases as these to effectively turn that page into a pseudo-HCL. Maybe this should be noted somewhere in the wiki... -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project signature.asc Description: OpenPGP digital signature
Re: Memstick image differences between 8.x and 9.x
On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 5:40 PM, Warren Block wrote: On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 2:21 PM, Garrett Cooper wrote: Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? The new memstick image uses GPT instead of MBR partitioning. GPT should have no impact on booting from the memory stick, as far as I am aware. Memory stick should not be a problem, but some of the Lenovo notebooks hate GPT, even with a PMBR: http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 Ugh, that's annoying. I'm half-tempted to note this in the new installer chapter, but I don't like the idea of such edge cases as these to effectively turn that page into a pseudo-HCL. There are already a couple of notes about having to use MBR with XP and other older operating systems. But instead of updating them, I'd rather see somebody with one of the affected systems contact somebody with influence at Lenovo and say hey, the FreeBSD guys are talking about making your broken GPT support famous followed quickly by a BIOS update. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Oct 9, 2011 8:52 AM, Warren Block wbl...@wonkity.com wrote: On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 5:40 PM, Warren Block wrote: On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 2:21 PM, Garrett Cooper wrote: Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? The new memstick image uses GPT instead of MBR partitioning. GPT should have no impact on booting from the memory stick, as far as I am aware. Memory stick should not be a problem, but some of the Lenovo notebooks hate GPT, even with a PMBR: http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 Ugh, that's annoying. I'm half-tempted to note this in the new installer chapter, but I don't like the idea of such edge cases as these to effectively turn that page into a pseudo-HCL. There are already a couple of notes about having to use MBR with XP and other older operating systems. But instead of updating them, I'd rather see somebody with one of the affected systems contact somebody with influence at Lenovo and say hey, the FreeBSD guys are talking about making your broken GPT support famous followed quickly by a BIOS update. I believe this is actually a case of the memstick image being an improperly formatted GPT as there is no backup partition table at the end of the volume. The only sensible answer is to not use GPT for the memstick image. I not said this,loud enough yet but this is a show stopper for 9.0-RELEASE and must be fixed. We can't have a major release that modern systems cannot install with one of now most popular install methods. As a first step, Andriy Gapon has provided a quick patch for makefs(8) so it can create filesystems with UFS labels (as bsdinstall relys on labels). If you want to fix your memstick, create a copy of the partition table at the end of the volume and it should boot. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 10/08/11 19:25, Matt Thyer wrote: On Oct 9, 2011 8:52 AM, Warren Blockwbl...@wonkity.com wrote: On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 5:40 PM, Warren Block wrote: On Sat, 8 Oct 2011, Glen Barber wrote: On 10/8/11 2:21 PM, Garrett Cooper wrote: Are there any general structural differences between FreeBSD 8 and 9 memstick images which could be at fault here? The new memstick image uses GPT instead of MBR partitioning. GPT should have no impact on booting from the memory stick, as far as I am aware. Memory stick should not be a problem, but some of the Lenovo notebooks hate GPT, even with a PMBR: http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 Ugh, that's annoying. I'm half-tempted to note this in the new installer chapter, but I don't like the idea of such edge cases as these to effectively turn that page into a pseudo-HCL. There are already a couple of notes about having to use MBR with XP and other older operating systems. But instead of updating them, I'd rather see somebody with one of the affected systems contact somebody with influence at Lenovo and say hey, the FreeBSD guys are talking about making your broken GPT support famous followed quickly by a BIOS update. I believe this is actually a case of the memstick image being an improperly formatted GPT as there is no backup partition table at the end of the volume. The only sensible answer is to not use GPT for the memstick image. I not said this,loud enough yet but this is a show stopper for 9.0-RELEASE and must be fixed. We can't have a major release that modern systems cannot install with one of now most popular install methods. As a first step, Andriy Gapon has provided a quick patch for makefs(8) so it can create filesystems with UFS labels (as bsdinstall relys on labels). If you want to fix your memstick, create a copy of the partition table at the end of the volume and it should boot. It is being fixed, pending Andriy's change getting into the tree, which should be soon, and will end up being used for the next build (which I believe is RC1). There is also the interesting question of actually installing to GPT on the hard disk, which is the default in 9.0. Does this not work on some systems? If so, do we want to blacklist them and use a different default partition scheme? Can we identify systems that violate regular PC boot standards and reject GPT? Any data on any of these points would be appreciated. -Nathan ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Oct 9, 2011 11:04 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 10/08/11 19:25, Matt Thyer wrote: I believe this is actually a case of the memstick image being an improperly formatted GPT as there is no backup partition table at the end of the volume. The only sensible answer is to not use GPT for the memstick image. I've not said this loud enough yet but this is a show stopper for 9.0-RELEASE and must be fixed. We can't have a major release that modern systems cannot install with one of the now most popular install methods. As a first step, Andriy Gapon has provided a quick patch for makefs(8) so it can create filesystems with UFS labels (as bsdinstall relys on labels). If you want to fix your memstick, create a copy of the partition table at the end of the volume and it should boot. It is being fixed, pending Andriy's change getting into the tree, which should be soon, and will end up being used for the next build (which I believe is RC1). There is also the interesting question of actually installing to GPT on the hard disk, which is the default in 9.0. Does this not work on some systems? If so, do we want to blacklist them and use a different default partition scheme? Can we identify systems that violate regular PC boot standards and reject GPT? Any data on any of these points would be appreciated. -Nathan I don't think there have been any reports of failure to boot properly formatted GPT yet. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sun, 9 Oct 2011, Matt Thyer wrote: On Oct 9, 2011 11:04 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 10/08/11 19:25, Matt Thyer wrote: There is also the interesting question of actually installing to GPT on the hard disk, which is the default in 9.0. Does this not work on some systems? If so, do we want to blacklist them and use a different default partition scheme? Can we identify systems that violate regular PC boot standards and reject GPT? Any data on any of these points would be appreciated. I don't think there have been any reports of failure to boot properly formatted GPT yet. Lenovo T420S and T520, from the links above. Install GPT on the hard drive, try to boot. http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 http://forum.thinkpads.com/viewtopic.php?f=9t=98078 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 04:38, Glen Barber g...@freebsd.org wrote: GPT should have no impact on booting from the memory stick, as far as I am aware. I've already emailed -current with an example where GPT+memstick == fail. Some theories include that GPT/EFT on USB is what the BIOS expects when doing BIOS reflashing, and gets confused when something else is there. Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 10/8/11 10:00 PM, Adrian Chadd wrote: On 9 October 2011 04:38, Glen Barber g...@freebsd.org wrote: GPT should have no impact on booting from the memory stick, as far as I am aware. I've already emailed -current with an example where GPT+memstick == fail. Some theories include that GPT/EFT on USB is what the BIOS expects when doing BIOS reflashing, and gets confused when something else is there. Yep, and I also recall you bringing this up in IRC. Though, at that time (well, up until a few hours ago), I wasn't aware of the Lenovo issue Warren mentioned. So, that said, I happily stand corrected. I am now aware of a few GPT memstick issues. :) -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project signature.asc Description: OpenPGP digital signature
Re: Memstick image differences between 8.x and 9.x
On 9 October 2011 10:15, Glen Barber g...@freebsd.org wrote: Yep, and I also recall you bringing this up in IRC. Though, at that time (well, up until a few hours ago), I wasn't aware of the Lenovo issue Warren mentioned. So, that said, I happily stand corrected. I am now aware of a few GPT memstick issues. :) Can we please flip off GPT partitions for memstick images?: ) Adrian ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sat, Oct 08, 2011 at 04:38:09PM -0400, Glen Barber wrote: Thomas, can you please zero out the beginning of the 1024 bytes of your memory stick, as follows (please take care to note the actual device for your memory stick, and change '/dev/da0' below, as appropriate): dd if=/dev/zero of=/dev/da0 bs=1024 count=1 Then re-write the memory stick per the instructions in the Handbook. Newly added to this section of the Handbook was a note to ensure the device is _not_ mounted (either manually, or automatically). So you want me to clear the first 1K bytes, and then write the whole image back to the pen drive, did I get this right? If so, I don't understand what we're trying to archive here, maybe you could explain? Anyway, I read it wrong the first time and did the following: I just cleared the first 1K of the stick as it was (with BETA3 image on it), and then put it in when rebooting the box and pressing F12 to get to the boot device list. Without the GPT it showed up in the list, but of course was unbootable when choosen. I then wrote back the 1K with dd if=FreeBSD-9... of=/dev/sde bs=1024 count=1 and verified the stick to be ok with a cmp(1) of the device file vs. the image file, so the pendrive is in the fresh state it should be. When plugging it in under Linux I get the following: [232309.636200] usb 1-1.1: new high speed USB device number 5 using ehci_hcd [232309.730109] scsi9 : usb-storage 1-1.1:1.0 [232310.729101] scsi 9:0:0:0: Direct-Access Ut165USB2FlashStorage 0.00 PQ: 0 ANSI: 2 [232310.904549] sd 9:0:0:0: Attached scsi generic sg5 type 0 [232310.905449] sd 9:0:0:0: [sde] 3948544 512-byte logical blocks: (2.02 GB/1.88 GiB) [232310.906657] sd 9:0:0:0: [sde] Write Protect is off [232310.906663] sd 9:0:0:0: [sde] Mode Sense: 00 00 00 00 [232310.907303] sd 9:0:0:0: [sde] Asking for cache data failed [232310.907308] sd 9:0:0:0: [sde] Assuming drive cache: write through [232310.909803] sd 9:0:0:0: [sde] Asking for cache data failed [232310.909808] sd 9:0:0:0: [sde] Assuming drive cache: write through [232311.031811] GPT:Primary header thinks Alt. header is not at the end of the disk. [232311.031825] GPT:1339319 != 3948543 [232311.031827] GPT:Alternate GPT header not at the end of the disk. [232311.031829] GPT:1339319 != 3948543 [232311.031830] GPT: Use GNU Parted to correct GPT errors. [232311.031845] sde: sde1 sde2 [232311.034154] sd 9:0:0:0: [sde] Asking for cache data failed [232311.034160] sd 9:0:0:0: [sde] Assuming drive cache: write through [232311.034165] sd 9:0:0:0: [sde] Attached SCSI removable disk [232312.081344] ufs was compiled with read-only support, can't be mounted as read-write Notice the GPT stuff. Of course that's because there can't possibly be an alternative GPT header at the end of the disk unless it's size is the same as the image size. As suggested I fixed it with parted and tried to boot from it again. No joy. I'm starting to believe this box just doesn't know GPT and the BIOS can't handle it at all. This is an Acer AX3960 Core i7 from maybe 6 months ago. Does anyone if the other BSDs have images using GPT, so I might verify? Regards, Thomas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sat, Oct 08, 2011 at 07:28:55PM -0600, Warren Block wrote: On Sun, 9 Oct 2011, Matt Thyer wrote: On Oct 9, 2011 11:04 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 10/08/11 19:25, Matt Thyer wrote: There is also the interesting question of actually installing to GPT on the hard disk, which is the default in 9.0. Does this not work on some systems? If so, do we want to blacklist them and use a different default partition scheme? Can we identify systems that violate regular PC boot standards and reject GPT? Any data on any of these points would be appreciated. I don't think there have been any reports of failure to boot properly formatted GPT yet. Lenovo T420S and T520, from the links above. Install GPT on the hard drive, try to boot. http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 http://forum.thinkpads.com/viewtopic.php?f=9t=98078 As I used parted from Linux to fix the alternate GPT, i.e. put it not at the end of the image data but on the end of the disk, and it still did not appear in the boot device list, the Acer AX3960 should probably be on the list as well. Being a Core i7 2600k system maybe 6 months old, it's rather recent hardware, but doesn't boot from the memstick image. Regards, Thomas ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On Sat, Oct 8, 2011 at 7:50 PM, Thomas K. f...@gothschlampen.com wrote: On Sat, Oct 08, 2011 at 07:28:55PM -0600, Warren Block wrote: On Sun, 9 Oct 2011, Matt Thyer wrote: On Oct 9, 2011 11:04 AM, Nathan Whitehorn nwhiteh...@freebsd.org wrote: On 10/08/11 19:25, Matt Thyer wrote: There is also the interesting question of actually installing to GPT on the hard disk, which is the default in 9.0. Does this not work on some systems? If so, do we want to blacklist them and use a different default partition scheme? Can we identify systems that violate regular PC boot standards and reject GPT? Any data on any of these points would be appreciated. I don't think there have been any reports of failure to boot properly formatted GPT yet. Lenovo T420S and T520, from the links above. Install GPT on the hard drive, try to boot. http://forums.freebsd.org/showthread.php?t=26304 http://forums.freebsd.org/showthread.php?t=26759 http://forum.thinkpads.com/viewtopic.php?f=9t=98078 As I used parted from Linux to fix the alternate GPT, i.e. put it not at the end of the image data but on the end of the disk, and it still did not appear in the boot device list, the Acer AX3960 should probably be on the list as well. Being a Core i7 2600k system maybe 6 months old, it's rather recent hardware, but doesn't boot from the memstick image. MBR format would be a better idea considering that there are a number of catches to using GPT (as noted on the list), and we're probably not anywhere near producing 2TB+ images (yet :)..), and to quote Monty Python MBR: I'm not dead yet!. If it comes to that day and age, we could provide a script or standalone command that would do the gpart foo to write out the partition table and just copy the image to the first partition, correct? Seems like more OSes should run into this issue producing GPT partitioned media than just us.. -Garrett ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
Re: Memstick image differences between 8.x and 9.x
On 10/8/11 10:41 PM, Thomas K. wrote: On Sat, Oct 08, 2011 at 04:38:09PM -0400, Glen Barber wrote: Thomas, can you please zero out the beginning of the 1024 bytes of your memory stick, as follows (please take care to note the actual device for your memory stick, and change '/dev/da0' below, as appropriate): dd if=/dev/zero of=/dev/da0 bs=1024 count=1 Then re-write the memory stick per the instructions in the Handbook. Newly added to this section of the Handbook was a note to ensure the device is _not_ mounted (either manually, or automatically). So you want me to clear the first 1K bytes, and then write the whole image back to the pen drive, did I get this right? If so, I don't understand what we're trying to archive here, maybe you could explain? Mostly what I was getting at here was ensuring the first blocks of the memory stick did not contain actual data. Though, I fear other forces may be at play here with GPT... -- Glen Barber | g...@freebsd.org FreeBSD Documentation Project ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to freebsd-current-unsubscr...@freebsd.org
