Asus F2A55-M - FreeBSD - 2014 archive
back to main FreeBSD page for this machine.
2014 archive.
2014-11-01: ada0p4 - also adjust /usr/local/etc/smb.conf. Replaces share q4data with q3data.
2014-10-31: ada0p4 - adjust /etc/fstab. before:
root@kg-quiet# more /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0p1 none swap sw 0 0 /dev/ada0p4 / ufs rw 1 1 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 #linprocfs /compat/linux/proc linprocfs rw 0 0
after:
root@kg-quiet# more /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0p1 none swap sw 0 0 /dev/ada0p4 / ufs rw 1 1 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 #linprocfs /compat/linux/proc linprocfs rw 0 0 /dev/ada1p1 /d1 ufs rw 2 2 /dev/ada2p1 /d2 ufs rw 2 2 /dev/ada3p1 /d3 ufs rw 2 2
good. After mounting /d1, /d2 and /d3, fix permissions on /d1:
root@kg-quiet# chmod g+w /d1
done.
2014-10-31: ada0p4 - create partitioning and filesystem on new ada1 drive:
root@kg-quiet# gpart show ada1 gpart: No such geom: ada1. root@kg-quiet# gpart create -s GPT ada1 ada1 created
verify
root@kg-quiet# gpart show ada1 => 34 5860533101 ada1 GPT (2.7T) 34 5860533101 - free - (2.7T)
add partition for the whole drive:
root@kg-quiet# gpart add -t freebsd-ufs ada1 ada1p1 added
verify:
root@kg-quiet# gpart show -p ada1 => 34 5860533101 ada1 GPT (2.7T) 34 6 - free - (3.0k) 40 5860533088 ada1p1 freebsd-ufs (2.7T) 5860533128 7 - free - (3.5k)
put a filesystem on it:
root@kg-quiet# newfs -U /dev/ada1p1 [...] 5856048544, 5856424800, 5856801056, 5857177312, 5857553568, 5857929824, 5858306080, 5858682336, 5859058592, 5859434848, 5859811104, 5860187360
done.
2014-10-28: ada0p4 - temporary mount ada4p1 on /d3, then you can copy from d2 -> d3:
root@kg-quiet# mount /dev/ada4p1 /d3
and temporary mount of ada5p1 on /d5, for copy from d4 -> d5:
root@kg-quiet# mount /dev/ada5p1 /d5
how does it look? disk layout:
root@kg-quiet# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ada0p4 145G 22G 111G 17% / devfs 1.0k 1.0k 0B 100% /dev procfs 4.0k 4.0k 0B 100% /proc /dev/ada2p1 902G 830G 9.1M 100% /d1 /dev/ada1s1d 902G 829G 809M 100% /d2 /dev/ada3p1 1.8T 1.6T 305M 100% /d4 /dev/ada4p1 2.7T 4.0k 2.4T 0% /d3 /dev/ada5p1 2.7T 4.0k 2.4T 0% /d5
fix permissions on /d3 and /d5:
root@kg-quiet# chmod g+w /d3 /d5
done. Now I'm ready for copying.
2014-10-28: ada0p4 - create partitioning and filesystem on ada4 and ada5 drives:
root@kg-quiet# gpart show ada4 gpart: No such geom: ada4. root@kg-quiet# gpart show ada5 gpart: No such geom: ada5.
nothing from before
root@kg-quiet# gpart create -s GPT ada4 ada4 created root@kg-quiet# gpart create -s GPT ada5 ada5 created
verify
root@kg-quiet# gpart show -p ada4 => 34 5860533101 ada4 GPT (2.7T) 34 5860533101 - free - (2.7T) root@kg-quiet# gpart show -p ada5 => 34 5860533101 ada5 GPT (2.7T) 34 5860533101 - free - (2.7T)
add "whole drive" partitions
root@kg-quiet# gpart add -t freebsd-ufs ada4 ada4p1 added root@kg-quiet# gpart add -t freebsd-ufs ada5 ada5p1 added
verify
root@kg-quiet# gpart show -p ada4 => 34 5860533101 ada4 GPT (2.7T) 34 6 - free - (3.0k) 40 5860533088 ada4p1 freebsd-ufs (2.7T) 5860533128 7 - free - (3.5k) root@kg-quiet# gpart show -p ada5 => 34 5860533101 ada5 GPT (2.7T) 34 6 - free - (3.0k) 40 5860533088 ada5p1 freebsd-ufs (2.7T) 5860533128 7 - free - (3.5k) looks good.
Put a filesystem on ada4p1:
root@kg-quiet# newfs -U /dev/ada4p1 [...] 5854543520, 5854919776, 5855296032, 5855672288, 5856048544, 5856424800, 5856801056, 5857177312, 5857553568, 5857929824, 5858306080, 5858682336, 5859058592, 5859434848, 5859811104, 5860187360
Put a filesystem on ada5p1:
root@kg-quiet# newfs -U /dev/ada5p1 [...] 5854543520, 5854919776, 5855296032, 5855672288, 5856048544, 5856424800, 5856801056, 5857177312, 5857553568, 5857929824, 5858306080, 5858682336, 5859058592, 5859434848, 5859811104, 5860187360
done.
2014-10-28: ada0p4 - fixed drive naming by loading the ahci module in /boot/loader.conf:
ahci_load="YES"
also fixed up /etc/fstab, which now reads:
root@kg-quiet# more /etc/fstab # Device Mountpoint FStype Options Dump Pass# /dev/ada0p1 none swap sw 0 0 /dev/ada0p4 / ufs rw 1 1 /dev/acd0 /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 #linprocfs /compat/linux/proc linprocfs rw 0 0 /dev/ada2p1 /d1 ufs rw 2 2 /dev/ada1s1d /d2 ufs rw 2 2 /dev/ada3p1 /d4 ufs rw 2 2
and drives now show up like this:
root@kg-quiet# swapinfo -h;df -h Device 1K-blocks Used Avail Capacity /dev/ada0p1 18874368 0B 18G 0% Filesystem Size Used Avail Capacity Mounted on /dev/ada0p4 145G 22G 111G 17% / devfs 1.0k 1.0k 0B 100% /dev procfs 4.0k 4.0k 0B 100% /proc /dev/ada2p1 902G 830G 9.1M 100% /d1 /dev/ada1s1d 902G 829G 809M 100% /d2 /dev/ada3p1 1.8T 1.6T 305M 100% /d4
nice.
2014-10-28: ad4p4 - prepare to boot again:
root@kg-quiet# gpart set -a bootonce -i 4 ad4 bootonce set on ad4p4
also, a general check before reboot:
root@kg-quiet# date;temp;swapinfo -h;echo " ";tvlm;echo " ";tvls;echo " ";df -h;echo " ";uptime;echo " ";ps ax | grep -v grep | grep ddc;ps ax | grep -v grep | grep smartd;ps ax | grep -v grep | grep natd Tue Oct 28 20:45:58 CET 2014 sysctl: unknown oid 'dev.cpu.0.temperature' Device 1K-blocks Used Avail Capacity /dev/ad4p1 18874368 0B 18G 0% Oct 28 16:42:07 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 17:12:07 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 17:42:07 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 18:12:08 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 18:42:07 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 19:12:07 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 19:42:08 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 20:12:07 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Oct 28 20:41:04 kg-quiet su: tingo to root on /dev/pts/7 Oct 28 20:42:08 kg-quiet smartd[712]: Device: /dev/ad10, 8 Currently unreadable (pending) sectors Jan 12 00:03:14 kg-quiet newsyslog[875]: logfile first created Filesystem Size Used Avail Capacity Mounted on /dev/ad4p4 145G 22G 111G 17% / devfs 1.0k 1.0k 0B 100% /dev procfs 4.0k 4.0k 0B 100% /proc /dev/ad8p1 902G 830G 9.1M 100% /d1 /dev/ad6s1d 902G 829G 809M 100% /d2 /dev/ad10p1 1.8T 1.6T 305M 100% /d4 8:45PM up 106 days, 2:34, 10 users, load averages: 0.08, 0.14, 0.10 712 ?? I 0:02.60 /usr/local/sbin/smartd -c /usr/local/etc/smartd.conf -p /var/run/smartd.pid
that was it.
2014-07-12: ad4p4 - aMule won't start, gives the message:
tingo@kg-quiet$ amule 2014-07-12 18:24:04: Initialising aMule 2.3.1 compiled with wxGTK2 v2.8.12 2014-07-12 18:24:04: Checking if there is an instance already running... 2014-07-12 18:24:04: No other instances are running. aMule Version: aMule 2.3.1 compiled with wxGTK2 v2.8.12 Terminated after throwing an instance of 'CEOFException' what(): SafeIO::EOF: Attempt to read past end of file. --== no BACKTRACE for your platform ==-- backtrace: Abort trap (core dumped)
This looks like a zero byte statistics.dat file:
tingo@kg-quiet$ ls -l ~/.aMule/stat* -rw-r--r-- 1 tingo users 138 Apr 16 00:02 /home/tingo/.aMule/staticservers.dat -rw-r--r-- 1 tingo users 0 Jul 11 14:52 /home/tingo/.aMule/statistics.dat
fix by removing the file:
tingo@kg-quiet$ rm ~/.aMule/statistics.dat
and now aMule starts normally again.
2014-07-12: ad4p4 - booting after the power outage; fsck runs and fixes all filesystems. From /var/log/messages:
Jul 12 09:17:30 kg-quiet kernel: WARNING: / was not properly dismounted Jul 12 09:17:30 kg-quiet kernel: WARNING: /d1 was not properly dismounted Jul 12 09:17:30 kg-quiet kernel: WARNING: /d1: mount pending error: blocks 12 files 1 Jul 12 09:17:30 kg-quiet kernel: WARNING: /d2 was not properly dismounted Jul 12 09:17:30 kg-quiet kernel: WARNING: /d4 was not properly dismounted
In /var/log/messages I can see the boot message from gptboot:
Jul 12 09:17:40 kg-quiet gptboot: Boot from ad4p4 succeeded.
Nothing more.
2014-07-12: ada0p3 - after a power outage (yesterday, while I was away) the machine boots from p3, into RELENG_9 (because it is default). Set bootonce for p4:
root@kg-quiet# uname -a FreeBSD kg-quiet.kg4.no 9.1-RELEASE FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 root@kg-quiet# gpart set -a bootonce -i 4 ada0 bootonce set on ada0p4
verify:
root@kg-quiet# gpart show -p ada0 => 34 1953525101 ada0 GPT (931G) 34 6 - free - (3.0k) 40 37748736 ada0p1 freebsd-swap (18G) 37748776 128 ada0p2 freebsd-boot (64k) 37748904 314572664 ada0p3 freebsd-ufs (150G) 352321568 314572800 ada0p4 freebsd-ufs [bootonce,bootme] (150G) 666894368 314572800 ada0p5 freebsd-ufs (150G) 981467168 125829120 ada0p6 freebsd-ufs (60G) 1107296288 846228847 - free - (403G)
ok, now reboot.
2014-06-08: prepare to copy from the old drive: I connect up the old drive via a (externally powered) sata-to usb dock, it shows up as da0 in /var/log/messages:
Jun 8 13:57:07 kg-quiet kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun 0 Jun 8 13:57:07 kg-quiet kernel: da0: <Generic External 1.04> Fixed Direct Access SCSI-4 device Jun 8 13:57:07 kg-quiet kernel: da0: 40.000MB/s transfers Jun 8 13:57:07 kg-quiet kernel: da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C) Jun 8 13:57:07 kg-quiet kernel: da0: quirks=0x2<NO_6_BYTE>
gpart info:
root@kg-quiet# gpart show -p da0 => 34 1953525101 da0 GPT (931G) 34 1953525101 da0p1 freebsd-ufs (931G)
I mount it at /media:
root@kg-quiet# mount /dev/da0p1 /media root@kg-quiet# df -h /media Filesystem Size Used Avail Capacity Mounted on /dev/da0p1 902G 773G 56G 93% /media
ready to copy. There is a bit of data to copy:
root@kg-quiet# du -sh /media/p2p/* 551G /media/p2p/Incoming 222G /media/p2p/Temp
I use worker to copy, it will take some time.
2014-06-08: set up the new ad8 drive. create partitioning on the new ad8: see if there is anything first:
root@kg-quiet# gpart show ad8 gpart: No such geom: ad8.
No, create it:
root@kg-quiet# gpart create -s GPT ad8 ad8 created
what does it look like?
root@kg-quiet# gpart show ad8 => 34 1953525101 ad8 GPT (931G) 34 1953525101 - free - (931G)
a typical 1 TB drive. Add a ufs partition that covers all of it:
root@kg-quiet# gpart add -t freebsd-ufs ad8 ad8p1 added
verify:
root@kg-quiet# gpart show -p ad8 => 34 1953525101 ad8 GPT (931G) 34 1953525101 ad8p1 freebsd-ufs (931G)
Ok, put a filesystem on it:
root@kg-quiet# newfs -U /dev/ad8p1 Reduced frags per cylinder group from 94064 to 94056 to enlarge last cyl group /dev/ad8p1: 953869.7MB (1953525100 sectors) block size 16384, fragment size 2048 using 5193 cylinder groups of 183.70MB, 11757 blks, 23552 inodes. with soft updates super-block backups (for fsck -b #) at: 160, 376384, 752608, 1128832, 1505056, 1881280, 2257504, 2633728, 3009952, 3386176, 3762400, 4138624, 4514848, 4891072, 5267296, 5643520, 6019744, 6395968, 6772192, 7148416, 7524640, 7900864, 8277088, 8653312, 9029536, [...snip...] 1944325792, 1944702016, 1945078240, 1945454464, 1945830688, 1946206912, 1946583136, 1946959360, 1947335584, 1947711808, 1948088032, 1948464256, 1948840480, 1949216704, 1949592928, 1949969152, 1950345376, 1950721600, 1951097824, 1951474048, 1951850272, 1952226496, 1952602720, 1952978944, 1953355168
done. Uncomment in /etc/fstab, then mount it:
root@kg-quiet# mount /d1
disk layout now:
root@kg-quiet# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad4p4 145G 24G 109G 18% / devfs 1.0k 1.0k 0B 100% /dev procfs 4.0k 4.0k 0B 100% /proc /dev/ad6s1d 902G 805G 24G 97% /d2 /dev/ad10p1 1.8T 1.6T 26G 98% /d4 /dev/ad8p1 902G 4.0k 830G 0% /d1
good.
2014-06-08: after a reboot, the new ad8 looks like this in smartctl:
Model Family: Seagate Barracuda (SATA 3Gb/s, 4K Sectors) Device Model: ST1000DM003-9YN162 Serial Number: Z1D1QFY8 LU WWN Device Id: 5 000c50 04dab3f29 Firmware Version: CC4C User Capacity: 1,000,204,886,016 bytes [1.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 4
cool.
2014-06-08: prepare to replace drive ad8: set bootable flag on ad4p4:
root@kg-quiet# gpart set -a bootonce -i 4 ad4 bootonce set on ad4p4
verify:
root@kg-quiet# gpart show -p ad4 => 34 1953525101 ad4 GPT (931G) 34 6 - free - (3.0k) 40 37748736 ad4p1 freebsd-swap (18G) 37748776 128 ad4p2 freebsd-boot (64k) 37748904 314572664 ad4p3 freebsd-ufs (150G) 352321568 314572800 ad4p4 freebsd-ufs [bootonce,bootme] (150G) 666894368 314572800 ad4p5 freebsd-ufs (150G) 981467168 125829120 ad4p6 freebsd-ufs (60G) 1107296288 846228847 - free - (403G)
comment out ad8 in /etc/fstab.
2014-06-08: collecting info before replacing drive ad8. disk layout:
root@kg-quiet# df -h Filesystem Size Used Avail Capacity Mounted on /dev/ad4p4 145G 24G 109G 18% / devfs 1.0k 1.0k 0B 100% /dev procfs 4.0k 4.0k 0B 100% /proc /dev/ad8p1 902G 773G 56G 93% /d1 /dev/ad6s1d 902G 805G 24G 97% /d2 /dev/ad10p1 1.8T 1.6T 26G 98% /d4 /dev/fuse0 12T 6.3T 6.4T 50% /usr/home/tingo/mpoint
mount info:
root@kg-quiet# mount /dev/ad4p4 on / (ufs, local, soft-updates) devfs on /dev (devfs, local, multilabel) procfs on /proc (procfs, local) /dev/ad8p1 on /d1 (ufs, local, soft-updates) /dev/ad6s1d on /d2 (ufs, local, soft-updates) /dev/ad10p1 on /d4 (ufs, local, soft-updates) /dev/fuse0 on /usr/home/tingo/mpoint (fusefs.sshfs, local, nosuid, synchronous, mounted by tingo)
gpart info for ad8:
root@kg-quiet# gpart show -p ad8 => 34 1953525101 ad8 GPT (931G) 34 1953525101 ad8p1 freebsd-ufs (931G)
top level directories on ad8:
root@kg-quiet# ll /d1 total 18 drwxrwxr-x 4 root wheel 512 Jun 27 2013 ./ drwxr-xr-x 30 root wheel 1024 Jun 21 2013 ../ -rwx------ 1 tingo wheel 6148 Jun 27 2013 .DS_Store* drwxrwxr-x 2 root operator 512 Jun 2 02:09 .snap/ drwxr-xr-x 4 tingo wheel 512 Jun 27 2013 p2p/
nothing more.
2014-06-01: ad4p4 - the machine suddenly hung tonight. No ping, no response from the console. I had to force it off via the power button. After it rebooted into
RELENG_9 (ada0p3) I did a gpart set -a bootonce -i 4 ada0 and rebooted it. No clues in /var/log/messages, last output or elsewhere to why it hung. The machine had
an uptime of about 344 days before it hung:
12:44PM up 344 days, 14:49, 8 users, load averages: 1.74, 1.78, 1.76