Search results

Absolutely yes, do that please. I did some more poking around, and tested your 512k dump on a 7.1 box of mine. It had no problem seeing it as a disk with MBR and BSD label in the first slice, and the label partitions were identical to what I posted at #17. I guess this must be fall out with...

If you're specifying the device type with -d, you need to use "atacam", not "ata". Smartmontools is written with FreeBSD in mind though, so it should autodetect the device type correctly. (ie. no need to potentially break things with -d)

I think I found your old BSD label: => 0 409600000 md0 BSD (195G) 0 1048576 1 freebsd-ufs (512M) 1048576 4129504 2 freebsd-swap (2G) 5178080 4161536 4 freebsd-ufs (2G) 9339616 1048576 5 freebsd-ufs (512M) 10388192 230859850...

There certainly is no fix for it that can be reasonably disseminated via a community forum alone, but maybe you'll get lucky...

From my brief look at that dump, it looks like your disk was formatted as a dedicated BSD label before you installed FreeBSD 9.0. When you installed FreeBSD 9.0 it got overwritten with an MBR and a new BSD label 63 sectors offset into your old one. Sooo, I'm not sure what's left of your data...

Sounds like you need to hire someone.

Can anyone explain the OP's benchmark results?

Well, if you post more of your disk I'll test that here too. Say the first 512 KiB? That will expose a bit of your root file system data to me though. Maybe something's blowing up after the MBR.

Well, I took your mbr1 file and applied it to an MD-backed device here - works fine: # dd if=/dev/null of=d1 oseek=200000 bs=1m count=1 0+0 records in 0+0 records out 0 bytes transferred in 0.000017 secs (0 bytes/sec) # mdconfig -a -t vnode -f /data/tmp/d1 md0 # dd if=~aragon/Downloads/mbr1...

Ah yes, of course! :r

Strange... MBR looks fine. Could you post the binary of your MBR please? dd if=/dev/ada0 bs=512 count=1 | gzip > /tmp/mbr.gz And then post the resulting /tmp/mbr.gz...

I stumbled upon this: http://www.youtube.com/watch?v=IRa6wFBLU28 Looks pretty cool... and that's 4 months old.

I wonder what's wrong with... the uptime command? (or the system calls it makes)

Post a hexdump of your MBR... dd if=/dev/ada1 bs=512 count=1 | hd -v

You could also look at OpenBSD's release notes for versions 4.2, 4.3, 4.4, and 4.5. :)

You have 3 pcm units, and it looks like the second one is your analog output device. FreeBSD usually uses the first one by default, so try set pcm1 as your default unit: sysctl hw.snd.default_unit=1

I'm curious to know what hardware status app is running horizontally at the bottom of your screen? And what are those quotes below it? :)

The suspense is killing us. Post away please! :)

What's strange for me is that your last two pass rules are if-bound ("on fxp0"), but you're setting their state policy to floating?

Your conditioning makes your stance understandable, but you've got to realise a few fundamental things. Firstly, a country's legal system is grounded in the morals upon which it is built. Secondly, the morals upon which humans operate can be vastly different to the morals that justify a...