Re: FreeBSD on SSD on ASUS P5KPL-C
2012/11/18 Shane Ambler free...@shaneware.biz: On 18/11/2012 06:49, Snow Mountains wrote: Could you recommend a reliable document on how to do a correct block alignment for new FreeBSD 9 install? FreeBSD Handbook doesn't mention this at all, although I can find a lot of (not quite consistent) advises on the net on how to do it with gpart/newfs. Over the last week there has been a discussion with the subject Advanced Format Drive ? on this list that has been discussing that. If you only just signed up then you can search for it in the mail archives. There is a lot of useful info there, and I also found a lot of useful tips from Warren Block on how to create swap as a file, how to use tmpfs, about noatime etc. However, nowhere I can found anything that could explain me for sure how to do this BEFORE that: I've got 240G Kingston SSD. I want this: win7: ada2s1 ~ 30G empty (probably for experimental little win7 install in the future) freebsd9: ada2s2a ~3G for / ada2s2d ~80G the for /usr (separated for easier backup) ada2s2f ~ the rest for storage How to do this with gpart, respecting 4g alignment etc? Can anybody share the exact commands to achieve this? SergiM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on SSD on ASUS P5KPL-C
2012/11/19 Warren Block wbl...@wonkity.com: On Mon, 19 Nov 2012, Snow Mountains wrote: 2012/11/18 Shane Ambler free...@shaneware.biz: On 18/11/2012 06:49, Snow Mountains wrote: Could you recommend a reliable document on how to do a correct block alignment for new FreeBSD 9 install? FreeBSD Handbook doesn't mention this at all, although I can find a lot of (not quite consistent) advises on the net on how to do it with gpart/newfs. Over the last week there has been a discussion with the subject Advanced Format Drive ? on this list that has been discussing that. If you only just signed up then you can search for it in the mail archives. There is a lot of useful info there, and I also found a lot of useful tips from Warren Block on how to create swap as a file, how to use tmpfs, about noatime etc. I didn't say anything about noatime, and personally have not done that on SSDs. However, nowhere I can found anything that could explain me for sure how to do this BEFORE that: I've got 240G Kingston SSD. I want this: win7: ada2s1 ~ 30G empty (probably for experimental little win7 install in the future) freebsd9: ada2s2a ~3G for / ada2s2d ~80G the for /usr (separated for easier backup) ada2s2f ~ the rest for storage How to do this with gpart, respecting 4g alignment etc? Can anybody share the exact commands to achieve this? That's 4K. Most of the following is shown in the new Handbook gmirror section: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/geom-mirror.html Create the MBR partitioning scheme: # gpart create -s mbr ada2 Add MBR bootcode: # gpart bootcode -b /boot/mbr ada2 Add the Windows 7 partition, forcing it to start at block 2048 because -a is not going to do what is expected for slices because of decades-old CHS stuff: # gpart add -t ntfs -b 2048 -s 30g ada2 Create the FreeBSD slice: # gpart create -s bsd ada2s1 Set this slice active and add FreeBSD bootcode: # gpart set -a active -i 1 ada2s1 Warren, great, thank you! Just one small problem. Here I got this: # gpart create -s bsd ada2s1 gpart: geom 'ada2s1': File exists # gpart set -a active -i 1 ada2s1 gpart: index '1': No such file or directory Expected? Anyway, is it any way to but FreeBSD on something like s2? Sergi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on SSD on ASUS P5KPL-C
2012/11/20 Warren Block wbl...@wonkity.com: On Tue, 20 Nov 2012, Snow Mountains wrote: Just one small problem. Here I got this: # gpart create -s bsd ada2s1 gpart: geom 'ada2s1': File exists # gpart set -a active -i 1 ada2s1 gpart: index '1': No such file or directory Expected? Anyway, is it any way to but FreeBSD on something like s2? Sorry, typo. FreeBSD does not have to be the first slice. # gpart create -s bsd ada2s2 # gpart set -a active -i 1 ada2s2 Hm, still doesn't work. Look: # gpart destroy -F ada2 ada2 destroyed # gpart create -s mbr ada2 ada2 created # gpart bootcode -b /boot/mbr ada2 bootcode written to ada2 # gpart add -t ntfs -b 2048 -s 30g ada2 ada2s1 added # gpart create -s bsd ada2s2 gpart: arg0 'ada2s2': Invalid argument S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on SSD on ASUS P5KPL-C
2012/11/20 Warren Block wbl...@wonkity.com: I know I've seen that, but can't recall what causes it. You can try retasting before creating the BSD partitions: # true /dev/ada2 # gpart create -s bsd ada2s2 Sorry, no difference: # gpart show ada2 = 63 468862065 ada2 MBR (223G) 63 2016- free - (1M) 2079 62914509 1 ntfs (30G) 62916588 405945540- free - (193G) # true /dev/ada2 # gpart create -s bsd ada2s2 gpart: arg0 'ada2s2': Invalid argument S. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
FreeBSD on SSD on ASUS P5KPL-C
Hello, I'm about to upgrade hardware on my desktop and to install FreeBSD 9 on it. I have ASUS P5KPL-C and want to buy a SSD or SATA-III 6Gb/s drive for it. Please advise me: * does it make sense to buy SSD drive for a mb that supports 4x SATA 3Gb/s (of couse, expecting a possible future mb upgrade)? * if SSD is capable of working at greater speed, will it simply operate on maximum 3Gb/s on P5KPL-C? * the same question for SATA-III 6Gb/s. Will it simply operate on 3Gb on my mb? * How will FreeBSD 9 behave in such situations? Any special tweaking needed? Thank you very much for your explanations, Sergi M. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: FreeBSD on SSD on ASUS P5KPL-C
2012/11/17 ill...@gmail.com ill...@gmail.com: On 17 November 2012 12:26, Snow Mountains snow.mountain...@gmail.com wrote: * How will FreeBSD 9 behave in such situations? Any special tweaking needed? I wouldn't expect any special behaviour, though you need to take care with block alignment. Perhaps in the future FreeBSD will have a blocksize/erase-blocksize aware formatting partitioning tool(s), but at the moment, you need to make sure those are correctly aligned if you want good performance from 4k blocksize drives ( SSDs will probably still need to be aligned to whatever the erase block size is). illoai, thank you for the answer! I'll certainly go with SSD in that case. Could you recommend a reliable document on how to do a correct block alignment for new FreeBSD 9 install? FreeBSD Handbook doesn't mention this at all, although I can find a lot of (not quite consistent) advises on the net on how to do it with gpart/newfs. Sergi ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Thomas, thank you for reply! No, it wasn't dangerously dedicated disk. However, what is the exact command to add ad4s1 and ad4s3 using bsdlabel? Is it possible at all? I thought I should use fdisk or gpart for that. Thanks, Sergi M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Groupping restored partitions into slices
Thomas, thank you very much for your mail, but that isn't what I asked. Of course, I know that bsdlabel -R ad0s1 new_label_file writes new labels to ad0s1. My question is: what to do if I _lost_ s1, s2, and s3 - how to recover _them_ first? Without that, all I can do is to write labels table directly on ad0. SergiM. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Missing SATA drive after upgrade to 7.0
2008/3/25, Christopher Cowart [EMAIL PROTECTED]: Hello, I was in the process of upgrading from 6.2 to 7.0. After the installkernel, I rebooted into single, only to find the mountroot prompt: | Trying to mount root from ufs:/dev/ad2s1a | | Manual root filesystem specification: | fstype:device Mount device using filesystem fstype |eg. ufs:da0s1a | ? List valid disk boot devices | empty line Abort manual input | | mountroot ? | | List of GEOM managed disk devices: | acd0 fd0 Boot messages for 7.0 (grep -i ata dmesg-7.0): | atapci0: Intel 6300ESB SATA150 controller port | 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1470-0x147f at device 31.2 | on pci0 | ata0: ATA channel 0 on atapci0 | ata0: [ITHREAD] | ata1: ATA channel 1 on atapci0 | ata1: [ITHREAD] | acd0: CDROM LG CD-ROM CRN-8245B/1.16 at ata0-master UDMA33 Boot messages for 6.2 (grep -i ata dmesg-6.2): | atapci0: Intel 6300ESB SATA150 controller port | 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1470-0x147f at device 31.2 | on pci0 | ata0: ATA channel 0 on atapci0 | ata1: ATA channel 1 on atapci0 | acd0: CDROM LG CD-ROM CRN-8245B/1.16 at ata0-master UDMA33 | ad2: 76324MB Seagate ST380013AS 3.25 at ata1-master SATA150 Any ideas where my harddrive went? I can `boot kernel.old' without any problems. I think this post [1] might be related. Unfortunately, the problem went away for the person who submitted the referenced PR. [1] http://lists.freebsd.org/pipermail/freebsd-i386/2008-January/006239.html Hey, I have same problem with my old computer: atapci0: Intel PIIX4 UDMA33 controller port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xf000-0xf00f at device 2.1 on pci0 ata0: ATA channel 0 on atapci0 ata0: [ITHREAD] ata1: ATA channel 1 on atapci0 ata1: [ITHREAD] ad1: 76319MB WDC WD800JB-00JJC0 05.01C05 at ata0-slave UDMA33 acd0: CDRW CD-W540E/1.0C at ata1-master UDMA33 Also, it waits 10 seconds after ata0: ATA channel 0 on atapci0, true ? If you reboot 3-4 times it will pass and everything will work normally. Then, I tried with disabled ACPI and it booted always without problems. However, then I recompiled GENERIC kernel because of HPLIP and now situation is opposite: it always boots with ACPI but not with ACPI. Very strange... SergiM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no ad1s3a,b,d... on ad1s3 after bsdlabel
2008/3/12, Lowell Gilbert [EMAIL PROTECTED]: Snow Mountains [EMAIL PROTECTED] writes: I try to understand bsdlabel. I have former fat slice (ad1s3) on my disk and I want to make several BSD partitions on it. I did this: # dd if=/dev/zero of=/dev/ad1s3 bs=1k count=1024 1024+0 records in 1024+0 records out 1048576 bytes transferred in 0.318986 secs (3287217 bytes/sec) # bsdlabel -w ad1s3 # bsdlabel -e ad1s3 (edit) # bsdlabel ad1s3 # /dev/ad1s3: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1000 164.2BSD0 0 0 b: 1000 10164.2BSD0 0 0 c: 476166600unused0 0 # raw part, don't edit d: 27616644 20164.2BSD0 0 0 # newfs -U /dev/ad1s3a newfs: /dev/ad1s3a: could not find special device # ls /dev/ad1s3* /dev/ad1s3 # What I miss because I don't have ad1s3a,b,d? If repeat same procedure on disk (big file) mounted as /dev/md0, a see /dev/md0,a,b,d,e... after this group of commands. On what version of FreeBSD? This happens on: # uname -r 6.2-RELEASE-p11 SergiM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: no ad1s3a,b,d... on ad1s3 after bsdlabel
2008/3/12, Josh Paetzel [EMAIL PROTECTED]: On Wednesday 12 March 2008 07:30:34 am Snow Mountains wrote: 2008/3/12, Lowell Gilbert [EMAIL PROTECTED]: Snow Mountains [EMAIL PROTECTED] writes: I try to understand bsdlabel. I have former fat slice (ad1s3) on my disk and I want to make several BSD partitions on it. I did this: # dd if=/dev/zero of=/dev/ad1s3 bs=1k count=1024 1024+0 records in 1024+0 records out 1048576 bytes transferred in 0.318986 secs (3287217 bytes/sec) # bsdlabel -w ad1s3 # bsdlabel -e ad1s3 (edit) # bsdlabel ad1s3 # /dev/ad1s3: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1000 164.2BSD0 0 0 b: 1000 10164.2BSD0 0 0 c: 476166600unused0 0 # raw part, don't edit d: 27616644 20164.2BSD0 0 0 # newfs -U /dev/ad1s3a newfs: /dev/ad1s3a: could not find special device # ls /dev/ad1s3* /dev/ad1s3 # What I miss because I don't have ad1s3a,b,d? If repeat same procedure on disk (big file) mounted as /dev/md0, a see /dev/md0,a,b,d,e... after this group of commands. On what version of FreeBSD? This happens on: # uname -r 6.2-RELEASE-p11 SergiM Did you delete and recreate the slice or is it still marked as FAT when you do fdisk /dev/ad1 Josh, you are right! No, I did not do it. It was still marked as FAT. I thought that it is enough to overwrite first 1M of slice with zeros. I entered sysinstall and just changed slice's type with T. That was enough. Then, fresh bsdlabel appeared on it. After editing, I now have all BSD partitions (a,b,d...) mountable. However, here handbook is not precise, I think. Please see this: http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/disks-adding.html I deduced from it that fdisk is necessary only for dedicated and new disks (fdisk -BI da1 #Initialize your new disk). If it's still a FAT/DOS slice you might try deleting and recreating it as a native FreeBSD slice, I'm not entirely sure putting a bsdlabel on a FAT slice is going to do the right thing (although I could be wrong here) It seems that you are right. But this still confuses me: # dd if=/dev/zero of=/home/minidisk.bin bs=1k count=10 . # mdconfig -a -t vnode -f /home/minidisk.bin -u 2 # ls /dev/md2* /dev/md2 # bsdlabel -w md2 # ls /dev/md2* /dev/md2/dev/md2a /dev/md2c # bsdlabel -e md2 .. # ls /dev/md2* /dev/md2/dev/md2b /dev/md2d /dev/md2a /dev/md2c /dev/md2e and then # fdisk /dev/md2 *** Working on device /dev/md2 *** The data for partition 1 is: sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD) start 63, size 192717 (94 Meg), flag 80 (active) beg: cyl 0/ head 1/ sector 1; end: cyl 11/ head 254/ sector 63 The data for partition 2 is: UNUSED The data for partition 3 is: UNUSED The data for partition 4 is: UNUSED So bsdlabel was enough in this case. Why is this different from real hard disk? And one more question: is disk geometry data somehow written in fdisk W (write) actions? I mean, is it possible to spoil something on existing FreeBSD slices (which contain data) if I set wrong geometry for entire drive when I edit something in fdisk editor? Thank you very much SergiM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
no ad1s3a,b,d... on ad1s3 after bsdlabel
Hi I try to understand bsdlabel. I have former fat slice (ad1s3) on my disk and I want to make several BSD partitions on it. I did this: # dd if=/dev/zero of=/dev/ad1s3 bs=1k count=1024 1024+0 records in 1024+0 records out 1048576 bytes transferred in 0.318986 secs (3287217 bytes/sec) # bsdlabel -w ad1s3 # bsdlabel -e ad1s3 (edit) # bsdlabel ad1s3 # /dev/ad1s3: 8 partitions: #size offsetfstype [fsize bsize bps/cpg] a: 1000 164.2BSD0 0 0 b: 1000 10164.2BSD0 0 0 c: 476166600unused0 0 # raw part, don't edit d: 27616644 20164.2BSD0 0 0 # newfs -U /dev/ad1s3a newfs: /dev/ad1s3a: could not find special device # ls /dev/ad1s3* /dev/ad1s3 # What I miss because I don't have ad1s3a,b,d? If repeat same procedure on disk (big file) mounted as /dev/md0, a see /dev/md0,a,b,d,e... after this group of commands. thanks SergiM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lost FreeBSD slices (labels?) after NetBSD install -- please help!!
2007/12/19, Nikola Lečić [EMAIL PROTECTED]: On Wed, 19 Dec 2007 03:54:00 +0100 Snow Mountains [EMAIL PROTECTED] wrote: [...] Hello and thanks vry much for this response and because you pointed me to right direction - what to read! It took me some time to run this and to understand always what I am doing, but it seems to work! testdisk gives me sizes that 100% correspond with _partition_ (:)) proportions I remember (and some nonsenses about tiny FAT partition somewhere...). dlfind homepage was incredibly useful for me as newbie in creating BSD partition labels, and I created bsdlabel file, carefully calculated offsets, I am happy that former ad1s4a is mountable so that I can read /etc/fstab! Excellent! Just note that you don't need to calculate offsets; you can use asterisk (*) for all offsets from b: (swap) onward; and you can use * as the size of the last partition, too. However I have several questions just to be 100% sure. a. swap size: by an accident, I have written swapsize (from swapinfo) of 1024 1kb blocks; it is slightly different from what I get when I subtract all partition size from total slice's size (as testdisk reported). What I should trust? Use the value from swapinfo; swap is just that space (unlike sizes that you see in df(1) output: they are not sizes of partitions). The size of slice: you should anyway _first_ run 'bsdlabel-w /dev/ad1s4' -- it will write initial info and the value for c: will be the value you should use. Success!!! After several wrong tables, I got right one, my dear documents are now visible and readable again! Correct size of swap was indeed size reported by swapinfo. b. Do I need just bsdlabel -R -e? You probably typoed, either '-R' or '-e' (= 'from file' or 'to edit directly'). However, I believe you should use '-B' as well, because bootstrap code was destroyed too, and you won't be able to boot FreeBSD even with recovered partitions. Indeed (-B), and FreeBSD is bootable again. Is it safe to experiment? Yes, it is. If you write wrong data, it will just not work. Once you get mountable partitions, please fsck(8) them. fsck said: FREE BLK COUNT(S) WRONG IN SUPERBLK -- SALVAGE? on all partitions except ad1s4a; I said 'yes' and now it says they are clean. c. What to write as fsize, bsize fsize and bsize are 2048 and 16384 if you used all defaults when installed FreeBSD (read newfs(8)). and bps/cpg? It is completly confusing for me, bps/cpg explanation from bsdlabel man page is unclear to me, I see that some people use all zeros and I can not find a clue in various examples... Hmm, yes... Actually, it seems that they can be calculated by comparing data obtained from 'bsdlabel -A /dev/ad1s4...' (look at the top of the output) and from particular 'newfs -N /dev/ad1s4X' (this command doesn't create new file system but just prints all data about how it would be created) -- but after recovery, of course. Read the entire thread that contains this: http://lists.freebsd.org/pipermail/freebsd-questions/2004-January/031603.html However, I've never been able to find any info in the docs that exactly explains what algorithm newfs(8) uses for this field... Therefore I believe (although I'm not 100% sure) that the only way to get old bps/cpg data is to (1) dump(8) partitions once they work; (2) bsdlabel -e bps/cpg of these partitions to zeros; (3) recreate file systems there (this will write new (true) bps/cpg values); (4) restore(8) filesystems. However, if fsck(8) tells you that filesystems are clear once you recover them, I believe you don't have to worry about this. Maybe some filesystem guru can confirm. (According to this reputable source: http://www.onlamp.com/pub/a/bsd/2002/06/27/Big_Scary_Daemons.html last three values are actually ignored...) -- Nikola Lečić :: Никола Лечић I tried to google to find similar partition sizes, and to use their bsdlabel values, but according to what you said everything depends on specific disc hardware, so tables of other people are not 100% usable... But all-zeroes seems to work 100% well and happy! (And of course, backups are the first thing to do!) Resume, for archives, what I did in FreeSBIE with your explanations: o Use disk size reported from raw bsdlabel -w o Use swap size reported from swapinfo, or guess, but the subtracted value (disk - sum of other partitions) was not correct for me... :( o Use partition sizes reported from testdisk o Assemble table accorting to bsdlabel manual page and to, for example, dlfind homepage o Write it with -B option. o Try to mount; nothing? Play with swap size... o Mountable? fsck them o Correct everything fsck wants. o that's it. thank you! Sergi M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Lost FreeBSD slices (labels?) after NetBSD install -- please help!!
2007/12/16, Nikola Lečić [EMAIL PROTECTED]: Hello, On Fri, 14 Dec 2007 05:15:16 + Snow Mountains [EMAIL PROTECTED] wrote: People, I have FreeBSD install on 80G disk that looked like this: ad1s1 ~ 2.4G ad1s2 ~23.0G ad1s3 ~19.1G ad1s4 ~38.0G, FreeBSD partition, sliced like this: ^ ^^ (a note: the correct terminology is actually the opposite: these a...e are partitions, real BSD partitions. What is called partition in non-BSD world is a slice here; so: FreeBSD slice, (BSD-)partitioned/labelled like this...) ad1s4a / (507630 1K-blocks) ad1s4b swap ad1s4d /var ad1s4e /tmp ad1s4f /usr [...] However, FreeBSD is now unbootable!!! Then I loaded FreeSBIE (FreeBSD 6.2 live CD), tried 'boot0cfg -B /dev/ad1' (also with '-d 0x80'), but no help! Then I realized that ad1s4 slices are lost. This means: A) from FreeSBIE, there is only /dev/ad1s4, no a,b,d,e,f. If I do this: FreeSBIE# mount /dev/ad1s4 /mnt/ufs.4 this is former / (ad1s4a) and is of its size (~507M). This probably means that you unwillingly changed FreeBSD label of ad1s4 and it's most likely that NetBSD wrote its own instead. However, from the bsdlabel(8) manpage: The various BSDs all use slightly different versions of BSD labels and are not generally compatible. So, NetBSD didn't recognise FreeBSD's labels and understood entire ad1s4 as one partition; however, ad1s4's reality is that it begins with small / (lost ad1s4a) and that is what you see; the rest is just ignored. boot0cfg did nothing because NetBSD obviously deleted ad1s4 FreeBSD's bootstrap code as well. I can't reach other slices! However, it gives me hope that NetBSD's slices are also invisible, although working from within itself: FreeSBIE# mount /dev/ad1s1 /mnt/ufs.1 gives also small NetBSD's / (its wd0a), not /usr etc. The same reason as above. [...] Please help me to recover my FreeBSD system. If I lost my data (ok, I understand they are buried, not erased), please tell me that gently. :-( That's why I think that you haven't lost any data. You must however re-create bsdlabel table on ad1s4. Since you didn't mention that you have a backup of bsdlabel (do you? :-)), you must recover it. There are two small utilities designed for this purpose, dlfind and ffsrescue: http://www.42.org/~sec/resources/disklabel.html http://www.leidinger.net/FreeBSD/ffsrescue.tar.gz but they don't recognise UFS2 beginning marks (only UFS1 ones). However, I tested sysutils/testdisk and it recognised UFS2 labels on my healthy slices perfectly, so there is no reason that it can't help you, since it simply analyses slice contents. This utility is not part of FreeSBIE, but I think that you can just download ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-6.2-release/sysutils/testdisk-6.3.tbz Then untar it in ~freesbie and run the binary. Just do this: ./testdisk /dev/ad1s4 and choose non partitioned in the second menu. Please note that testdisk will not recognise your swap. Then please try to compare results (given in 512k-blocks) to what you remember about partition sizes. If it gives you reasonable proportions, then re-creating a bsdlabel shouldn't be a big problem. So please take these actions and if the aforementioned assumptions are correct and you obtain some useful info, we shall continue. :-) Hello and thanks vry much for this response and because you pointed me to right direction - what to read! It took me some time to run this and to understand always what I am doing, but it seems to work! testdisk gives me sizes that 100% correspond with _partition_ (:)) proportions I remember (and some nonsenses about tiny FAT partition somewhere...). dlfind homepage was incredibly useful for me as newbie in creating BSD partition labels, and I created bsdlabel file, carefully calculated offsets, I am happy that former ad1s4a is mountable so that I can read /etc/fstab! However I have several questions just to be 100% sure. a. swap size: by an accident, I have written swapsize (from swapinfo) of 1024 1kb blocks; it is slightly different from what I get when I subtract all partition size from total slice's size (as testdisk reported). What I should trust? b. Do I need just bsdlabel -R -e? Is it safe to experiment? c. What to write as fsize, bsize and bps/cpg? It is completly confusing for me, bps/cpg explanation from bsdlabel man page is unclear to me, I see that some people use all zeros and I can not find a clue in various examples... Again, many thanks! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Lost FreeBSD slices (labels?) after NetBSD install -- please help!!
Hi, People, I have FreeBSD install on 80G disk that looked like this: ad1s1 ~ 2.4G ad1s2 ~23.0G ad1s3 ~19.1G ad1s4 ~38.0G, FreeBSD partition, sliced like this: ad1s4a / (507630 1K-blocks) ad1s4b swap ad1s4d /var ad1s4e /tmp ad1s4f /usr First three partitions are former fat/ntfs that I emptied, transformed to FreeBSD's ufs2 and used as FreeBSD storage. I used boot0cfg and my boot menu looked like this: F1 DOS (although nothing were installed in F1-F3, just ufs2 data) F2 DOS F3 DOS F4 FreeBSD Today, however, I decided to try a small NetBSD install on small ad1s1, I thought I could do no harm if I tell it to install itself onto first partition. So I passed through install, carefully checked partition1 (on wd0 disk according to it) for mark 'new fs', and sliced it did like this: wd0a / (around 550M) ... wd0e /usr (total ~2,4M, as described above) and left all other options (BSD labels etc.) as defaults. NetBSD installed and booted, menu looked like this: F1 BSD F2 DOS F3 DOS F4 FreeBSD However, FreeBSD is now unbootable!!! Then I loaded FreeSBIE (FreeBSD 6.2 live CD), tried 'boot0cfg -B /dev/ad1' (also with '-d 0x80'), but no help! Then I realized that ad1s4 slices are lost. This means: A) from FreeSBIE, there is only /dev/ad1s4, no a,b,d,e,f. If I do this: FreeSBIE# mount /dev/ad1s4 /mnt/ufs.4 this is former / (ad1s4a) and is of its size (~507M). I can't reach other slices! However, it gives me hope that NetBSD's slices are also invisible, although working from within itself: FreeSBIE# mount /dev/ad1s1 /mnt/ufs.1 gives also small NetBSD's / (its wd0a), not /usr etc. B) From NetBSD: FreeBSD's ad1s2 - NetBSD's wd0f (readable, data ok) FreeBSD's ad1s3 - NetBSD's wd0g (readable, data ok) FreeBSD's ad1s4a - NetBSD's wd0h (just /, 507M, readable) others (ad1s4 d-f), containing /usr/home are lost! Please help me to recover my FreeBSD system. If I lost my data (ok, I understand they are buried, not erased), please tell me that gently. :-( many thanks in advance Sergi M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Sony Ericsson: (da0:umass-sim0:0:0:0): NOT READY asc:3a, 0 (repeated)
Lowell Gilbert wrote: I have a Sony Ericsson phone, but it isn't a USB device. Thanks Lowell for your response. Do you attach your Sony Ericsson to computer at all, for example if you use it as camera? Is there any other option, or something that can you recommend? Another cable? These kinds of messages usually mean that the umass device is not responding as expected to queries. Some other Sony devices (cameras) seem to have extra padding requirements; you could try adding a quirk to the code for the umass device driver. To look more deeply, you would need someone with a decent knowledge of the USB protocols. Can you help me about what text I should add (in umass.c??) I mean, how to add quirk just for this specific phone? Sorry, but this is far away from my knowledge but I would like to try. I know how to recompile kernel and test it. I searched google for how to do this, but everything is too high level discussion. Thanks Sergi M ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sony Ericsson: (da0:umass-sim0:0:0:0): NOT READY asc:3a, 0 (repeated)
I posted this question 10 days ago, got no replies. Is it possible nobody here installed CD release of FreeBSD 6.2 and has Sony Ericsson mobile phone or something similar which causes similar problem? :-) Maybe summer time is the cause :-) So let me repeat: = Hi list, If I plug in my Secure Digital reader with the card from kamera, it is detected very fine and I can mount using -t msdosfs on /mnt/da0s1. But I have a little problem when trying to attach my Sony Ericcson W810 mobile phone to FreeBSD 6.2. See what I get: umass0: Sony Ericsson Sony Ericsson W810, rev 2.00/0.00, addr 5 umass1: Sony Ericsson Sony Ericsson W810, rev 2.00/0.00, addr 5 da0 at umass-sim0 bus 0 target 0 lun 0 da0: SEMC Int.Memory Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 da1 at umass-sim1 bus 1 target 0 lun 0 da1: SEMC Mem-Stick Removable Direct Access SCSI-0 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error .. this block repeats many many times for da0 and da1 too. umass0: at uhub4 port 1 (addr 5) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass1: at uhub4 port 1 (addr 5) disconnected (da1:umass-sim1:1:0:0): lost device (da1:umass-sim1:1:0:0): removing device entry When I plug out the Ericsson, umass1: detached Other data: FreeBSD 6.2, straight from instalation cd: FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC dmesg | grep usb usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: Intel 82801DB/L/M (ICH4) USB 2.0 controller on ehci0 usb3: USB revision 2.0 I searched google, more than 100 results with mistake messages, but nothing I can really use. What can be the reason? Do I have to send more data? with best regards, tnx in advance SM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Sony-Ericsson W810: (da0:umass-sim0:0:0:0): NOT READY asc:3a,0
Hi list, If I plug in my Secure Digital reader with the card from kamera, it is detected very fine and I can mount using -t msdosfs on /mnt/da0s1. But I have a little problem when trying to attach my Sony Ericcson W810 mobile phone to FreeBSD 6.2. See what I get: umass0: Sony Ericsson Sony Ericsson W810, rev 2.00/0.00, addr 5 umass1: Sony Ericsson Sony Ericsson W810, rev 2.00/0.00, addr 5 da0 at umass-sim0 bus 0 target 0 lun 0 da0: SEMC Int.Memory Removable Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 da1 at umass-sim1 bus 1 target 0 lun 0 da1: SEMC Mem-Stick Removable Direct Access SCSI-0 device da1: 1.000MB/s transfers da1: Attempt to query device size failed: NOT READY, Medium not present (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error Opened disk da0 - 6 (da0:umass-sim0:0:0:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:umass-sim0:0:0:0): CAM Status: SCSI Status Error (da0:umass-sim0:0:0:0): SCSI Status: Check Condition (da0:umass-sim0:0:0:0): NOT READY asc:3a,0 (da0:umass-sim0:0:0:0): Medium not present (da0:umass-sim0:0:0:0): Unretryable error .. this block repeats many many times for da0 and da1 too. umass0: at uhub4 port 1 (addr 5) disconnected (da0:umass-sim0:0:0:0): lost device (da0:umass-sim0:0:0:0): removing device entry umass0: detached umass1: at uhub4 port 1 (addr 5) disconnected (da1:umass-sim1:1:0:0): lost device (da1:umass-sim1:1:0:0): removing device entry When I plug out the Ericsson, umass1: detached Other data: FreeBSD 6.2, straight from instalation cd: FreeBSD 6.2-RELEASE #0: Fri Jan 12 10:40:27 UTC 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC dmesg | grep usb usb0: Intel 82801DB (ICH4) USB controller USB-A on uhci0 usb0: USB revision 1.0 usb1: Intel 82801DB (ICH4) USB controller USB-B on uhci1 usb1: USB revision 1.0 usb2: Intel 82801DB (ICH4) USB controller USB-C on uhci2 usb2: USB revision 1.0 usb3: EHCI version 1.0 usb3: companion controllers, 2 ports each: usb0 usb1 usb2 usb3: Intel 82801DB/L/M (ICH4) USB 2.0 controller on ehci0 usb3: USB revision 2.0 I searched google, more than 100 results with mistake messages, but nothing I can really use. What can be the reason? Do I have to send more data? with best regards, tnx in advance SM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Master volume doesn't work with headphones
(Posted this yesterday to the multimedia list, but questions list seems to be more appropriate. Sorry for double posting.) Hi FreeBSD people, I have a simple mixer question. What I can do to get Master volume working the same way with and without headphones? If I plug in headphones (dell i5100), master volume does nothing (even if I set it to 0 or 100), and I must use pcm; this is not nice because then KDE tray volume control doesn't work. What is the cause of this and how can I change it? Apologize if this is a stupid question. %sysctl -a | grep snd hw.snd.report_soft_formats: 1 hw.snd.targetirqrate: 32 hw.snd.verbose: 1 hw.snd.maxautovchans: 4 hw.snd.unit: 0 hw.snd.pcm0.buffersize: 16384 %mixer SM Mixer vol is currently set to 83:83 Mixer pcm is currently set to 78:78 Mixer speaker is currently set to 75:75 Mixer line is currently set to 75:75 Mixer mic is currently set to 0:0 Mixer cd is currently set to 75:75 Mixer rec is currently set to 100:100 Mixer igainis currently set to 100:100 Mixer ogainis currently set to 70:70 Mixer line1is currently set to 0:0 Mixer phin is currently set to 0:0 Mixer phoutis currently set to 0:0 Mixer videois currently set to 75:75 Recording source: mic %kldstat Id Refs AddressSize Name 1 14 0xc040 742370 kernel 32 0xc0b4e000 1af50linux.ko 41 0xc0b69000 58554acpi.ko 51 0xc3adf000 5000 snd_ich.ko 61 0xc3ae4000 1c000sound.ko 71 0xc3b12000 6000 linprocfs.ko 81 0xc3b22000 4000 logo_saver.ko Thank you SM ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
