Can you post your rc.conf, lspci and lsmod output please? Please use a wired connection with a static IP address to analyze this problem.

Assigning for the time being until we get more info.

In addition to the files RedShift asked for, are you using the "network" daemon, or "netcfg" ?

Here is lspci (on my new machine)

[af@andre ~]$ lspci
00:00.0 Host bridge: Intel Corporation 4 Series Chipset DRAM Controller (rev 03)
00:01.0 PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port (rev 03)
00:1a.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #4
00:1a.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #5
00:1a.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #6
00:1a.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #2
00:1b.0 Audio device: Intel Corporation 82801JI (ICH10 Family) HD Audio Controller
00:1c.0 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 1
00:1c.2 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 3
00:1c.5 PCI bridge: Intel Corporation 82801JI (ICH10 Family) PCI Express Port 6
00:1d.0 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #1
00:1d.1 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #2
00:1d.2 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB UHCI Controller #3
00:1d.7 USB Controller: Intel Corporation 82801JI (ICH10 Family) USB2 EHCI Controller #1
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 90)
00:1f.0 ISA bridge: Intel Corporation 82801JIR (ICH10R) LPC Interface Controller
00:1f.2 RAID bus controller: Intel Corporation 82801 SATA RAID Controller
00:1f.3 SMBus: Intel Corporation 82801JI (ICH10 Family) SMBus Controller
01:00.0 VGA compatible controller: nVidia Corporation Device 0605 (rev a2)
02:00.0 Network controller: Broadcom Corporation BCM4328 802.11a/b/g/n (rev 03)
03:00.0 FireWire (IEEE 1394): JMicron Technologies, Inc. IEEE 1394 Host Controller
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)

and lsmod

[af@andre ~]$ lsmod
Module Size Used by
ipv6 260132 18
psmouse 38288 0
i2c_i801 10768 0
serio_raw 7172 0
pcspkr 4352 0
sg 28852 0
nvidia 7220856 36
intel_agp 27068 0
i2c_core 22420 2 i2c_i801,nvidia
agpgart 30804 2 nvidia,intel_agp
dcdbas 8736 0
thermal 17052 0
processor 34732 5 thermal
evdev 11296 6
fan 6148 0
button 7824 0
battery 12036 0
ac 6020 0
vboxdrv 66200 0
fuse 52892 2
snd_hda_intel 370736 1
snd_seq_oss 31872 0
snd_seq_midi_event 8192 1 snd_seq_oss
snd_seq 49968 4 snd_seq_oss,snd_seq_midi_event
snd_seq_device 8332 2 snd_seq_oss,snd_seq
snd_hwdep 8964 1 snd_hda_intel
snd_pcm_oss 40192 0
snd_pcm 69636 2 snd_hda_intel,snd_pcm_oss
snd_timer 21384 2 snd_seq,snd_pcm
snd_page_alloc 9224 2 snd_hda_intel,snd_pcm
snd_mixer_oss 16512 1 snd_pcm_oss
snd 50724 11 snd_hda_intel,snd_seq_oss,snd_seq,snd_seq_device,snd_hwdep,snd_pcm_oss,snd_pcm,snd_timer,snd_mixer_oss
soundcore 8160 1 snd
rtc_cmos 11424 0
rtc_core 17564 1 rtc_cmos
rtc_lib 4480 1 rtc_core
usb_storage 96704 0
ext3 126344 2
jbd 46484 1 ext3
mbcache 8708 1 ext3
usbhid 46016 0
hid 41856 1 usbhid
ff_memless 6664 1 usbhid
dm_crypt 14724 0
crypto_blkcipher 17540 1 dm_crypt
sr_mod 16708 0
sd_mod 27160 2
wl 1073796 0
ohci1394 30256 0
cdrom 35360 1 sr_mod
ieee80211_crypt 6532 1 wl
ieee1394 80452 1 ohci1394
r8169 28804 0
mii 6528 1 r8169
ehci_hcd 36236 0
uhci_hcd 24080 0
usbcore 134384 5 usb_storage,usbhid,ehci_hcd,uhci_hcd
dm_mod 53704 11 dm_crypt
sata_sil 9480 0
ahci 30348 2
libata 153888 2 sata_sil,ahci
dock 9616 1 libata
scsi_mod 96460 5 sg,usb_storage,sr_mod,sd_mod,libata

I am using wicd now but I've been using the network daemon since I started using Arch (since March 2008) and the troubles with the network started back in October/November. No change to machine or the other parts of the network had been performed at the time. I've only been updating my Arch machine regulary.

Regards

André

PS. I'm not running the testing repo on my machine.

OK, so is this a wicd error? That makes a HUGE difference.

Can you try this with the normal Arch network scripts? If those work fine, we know this is a wicd error and can assign the bug to the proper maintainer

No it is NOT a wicd error. I have the exact same problem when I run the "network" daemon (no network, many restarts etc. then network if lucky). I just switched to wicd because I thought it was a network daemon issue but as it appears it is not.

Regards

André

OK, for more info... could you setup /etc/rc.d/network to work (as it's more basic), try to start it and then snag:
dmesg | tail -n30
or so and post it here?

I have a feeling this is a driver issue, and something that Ubuntu and others have patched.

Actually, I recall having problems with RealTek gigabit ethernet myself on Arch a long long time ago.

But on my old machine I have an nvidia network adapter (onbard) and intel network adapter and I have the same problem there. On my new machine it is a realtek and broadcom (wireless with the wl driver). If the network doesn't work on one card it doesn't work on the other either. When I have no network on my new machine with the wired card (realtek), the wireless doesn't see any networks either but when the wired works then the wireless sees the wireless network in my house. I'll try to set it up now with network now and give you the

dmesg | tail -n30

Here is the output from dmesg | tail -n30 when I don't have network at boot

[af@andre ~]$ dmesg | tail -n30
sda: rw=0, want=1953536123, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536124, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536125, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536126, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536127, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536128, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536129, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536130, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536124, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536125, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536126, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536127, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536128, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536129, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536130, limit=976773168
warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)

and below is the output when I get network again (had to restart 4 times before it came back up)

[af@andre ~]$ dmesg | tail -n30
attempt to access beyond end of device
sda: rw=0, want=1953536127, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536128, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536129, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536130, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536124, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536125, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536126, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536127, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536128, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536129, limit=976773168
attempt to access beyond end of device
sda: rw=0, want=1953536130, limit=976773168
NET: Registered protocol family 10
lo: Disabled Privacy Extensions
warning: `avahi-daemon' uses 32-bit capabilities (legacy support in use)
r8169: eth0: link up
r8169: eth0: link up
r8169: eth0: link up
eth1: no IPv6 routers present
eth0: no IPv6 routers present

Can you start your network using the rc.d script (and NOTHING else), then show us the output of:
ifconfig -a
route -n
ethtool eth0
ping <YOURGATEWAYHERE>
ping <ANINTERNETADDRESSHERE>

and if possible supply us a packet trace as well in a .pcap file (wireshark can make these).

OK, here is the output from the rc.d script

[root@andre ~]# /etc/rc.d/network start
:: Starting Network [DONE]
[root@andre ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:23:4E:7E:F8:FD
inet6 addr: fe80::223:4eff:fe7e:f8fd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0xc000

eth1 Link encap:Ethernet HWaddr 00:21:70:4E:A8:6B
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:218 Base address:0x6000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:47 errors:0 dropped:0 overruns:0 frame:0
TX packets:47 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8925 (8.7 Kb) TX bytes:8925 (8.7 Kb)

[root@andre ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
[root@andre ~]# ethtool eth0
Settings for eth0:
No data available
[root@andre ~]# ethtool eth1
Settings for eth1:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
[root@andre ~]# ping 192.168.1.1
connect: Network is unreachable
[root@andre ~]# ping www.google.com
ping: unknown host www.google.com

as you can see I don't a network connection and I tried like 10 time with restarting and etc. but I never got it up. But the funny thing is that ethtool reports back on eth1 on and eth0 but eth0 is my wired connection and is plugged in. So something messed up with the naming conventions of Arch and the network adapters. it seems like it can't remember them after boot. After 20 tries or so in all (I switched back to wicd and then network and wicd again) I finally did get internet again and here is the new output

[root@andre ~]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:21:70:4E:A8:6B
inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::221:70ff:fe4e:a86b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:317 errors:0 dropped:0 overruns:0 frame:0
TX packets:324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:273837 (267.4 Kb) TX bytes:35519 (34.6 Kb)
Interrupt:218 Base address:0x2000

eth1 Link encap:Ethernet HWaddr 00:23:4E:7E:F8:FD
inet6 addr: fe80::223:4eff:fe7e:f8fd/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:1 dropped:0 overruns:0 frame:1009
TX packets:0 errors:6 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:16 Base address:0xc000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:8769 (8.5 Kb) TX bytes:8769 (8.5 Kb)

[root@andre ~]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0
[root@andre ~]# ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supports auto-negotiation: Yes
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised auto-negotiation: Yes
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 0
Transceiver: internal
Auto-negotiation: on
Supports Wake-on: pumbg
Wake-on: g
Current message level: 0x00000033 (51)
Link detected: yes
[root@andre ~]# ethtool eth1
Settings for eth1:
No data available

PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=0.643 ms

PING www.l.google.com (74.125.79.99) 56(84) bytes of data.
64 bytes from ey-in-f99.google.com (74.125.79.99): icmp_seq=1 ttl=241 time=63.1 ms

SEE!!! Now eth0 and eth1 have been switched back (look at the MAC addresses) and now I have internet. Very strange... On my old machine I only had one network adapter (onboard) when this problem started so it just can't be that Arch is messing up with naming of the network adapters it has to go deeper than that IMHO.

Regards

André

Ah, so it seems your network cards are having an identity crisis. Fortunately, we, of the land of milk and honey, have a solution for that. Create a file /etc/udev/rules.d/10-network.rules and put this in it:

SUBSYSTEM=="net", ATTRS{address}=="aa:bb:cc:dd:ee:ff", NAME="eth0"
SUBSYSTEM=="net", ATTRS{address}=="ff:ee:dd:cc:bb:aa", NAME="eth1"

Replace the physical addresses to the ones you want.

Edit: alternatively you can specify the network modules you use in MODULES in rc.conf, so they will always load in the same order.

But why is it having this identity crisis and why was i having these issues back when I only had one network card in my old machine? But i'll try your suggestions now, many thanks!

Regards

André

Because there's no garantuee with auto detection that your interfaces will always be detected in the same order.

But if there is only one interface, how can it be detected in a different order?

Kind Regards

André

Well, the MODULES suggestion you made didn't change a thing but the suggestion with the /etc/udev/rules.d/10-network.rules file did make a little difference I had internet right after restart after created the file and rebooted. I could even switch to dhcp during the session and I got net immediately and a new IP from the server. Then I rebooted and I had no net and the

ifconfig -a

said that eth0 and eth1 still were switched around, e.g. eth0 was eth1 and eth1 was eth0 (looking at the MAC addresses).

Regards

André

Well it doesn't work, during the last 6 or 7 reboots with the rules script running only 2 times did it work, i.e. was eth0 and eth1 set up right the rest of the times they were reversed :(. I itried running the network with wicd, network from rcnconf and also the network script directly in /etc/rc.d/network but still it seems like it is based on luck in the end...

Regards

André

Well I'm not sure why your computer with only one ethernet card didn't work all the time, but it's unrelated to this problem, where your eth0 and eth1 changes. Did you try putting your ethernet modules in the right order in MODULES? The first one there will be eth0, the second eth1 and so forth.

Yes, I did put the modules in the right order, first the eth0 (r8169) and then eth1 (wl) and still I have to reboot many times until Arch gets it right.

Regards

André

Strange, then udev is still messing up somehow.

Udev has optional persistent net rules in /lib/udev/rules.d IIRC. Maybe try enabling those (remove the '.optional' from the filename).

That will ensure your devices are always in the same order

Here is my /etc/udev/rules.d directory

40-alsa.rules 60-persistent-input.rules
40-ia64.rules 60-persistent-storage-tape.rules
40-isdn.rules 60-persistent-storage.rules
40-pilot-links.rules 60-persistent-v4l.rules
40-ppc.rules 61-persistent-storage-edd.rules
40-s390.rules 64-device-mapper.rules
40-zaptel.rules 64-md-raid.rules
50-udev-default.rules 79-fstab_import.rules
50-udev-default.rules.orig 80-drivers.rules
60-cdrom_id.rules 95-udev-late.rules

which ones do you mean I need to edit?

Regards

André

[af@andre ~]$ cd /lib/udev/rules.d
[af@andre rules.d]$ ls
40-alsa.rules 60-persistent-input.rules
40-ia64.rules 60-persistent-storage-tape.rules
40-isdn.rules 60-persistent-storage.rules
40-pilot-links.rules 60-persistent-v4l.rules
40-ppc.rules 61-persistent-storage-edd.rules
40-s390.rules 64-device-mapper.rules
40-zaptel.rules 64-md-raid.rules
50-udev-default.rules 79-fstab_import.rules
50-udev-default.rules.orig 80-drivers.rules
60-cdrom_id.rules 95-udev-late.rules

the rest

[af@andre ~]$ cd /lib/udev/rules.d
[af@andre rules.d]$ ls
60-persistent-input.rules
60-persistent-storage-tape.rules
60-persistent-storage.rules
60-persistent-v4l.rules
61-persistent-storage-edd.rules
64-device-mapper.rules
64-md-raid.rules
79-fstab_import.rules
80-drivers.rules
95-udev-late.rules

Hmmm what udev package are you using?
Those rules should mostly be moved to /lib/udev/ not /etc/udev

I'm talking about this file:
$ pacman -Qo /etc/udev/rules.d/75-persistent-net-generator.rules.optional
/etc/udev/rules.d/75-persistent-net-generator.rules.optional is owned by udev 132-1

Pulling in some more pros. This is looking more and more to me like a udev related issue... not entirely sure though, it's confusing, to say the least

I'm using u-dev 130-1 from core.

Please try upgrading. 132 has been in core for a long time, and 135 is in testing.

I just checked the homepage for according to the homepage udev 130 is in core and 135 is in testing. I know I saw udev 132 but that was only in testing. Seems like it was just upgraded to 135 and nor moved to core. I found the rules file you mentioned

[af@andre ~]$ cd /etc/udev/rules.d
[af@andre rules.d]$ ls -l
totalt 268
-rw-r--r-- 1 root root 1499 2 aug 06:29 45-libnjb.rules
-rw-r--r-- 1 root root 93643 7 mar 2008 53-sane.rules
-rw-r--r-- 1 root root 70012 21 okt 21:57 54-gphoto.rules
-rw-r--r-- 1 root root 8507 6 dec 03:50 55-hpmud.rules
-rw-r--r-- 1 root root 1071 24 sep 16:13 60-pcmcia.rules
-rw-r--r-- 1 root root 79 12 nov 06:22 60-virtualbox.rules
-rw-r--r-- 1 root root 41338 21 dec 09:30 65-libmtp.rules
-rw-r--r-- 1 root root 390 8 okt 09:37 75-cd-aliases-generator.rules.optional
-rw-r--r-- 1 root root 2403 8 okt 09:37 75-persistent-net-generator.rules.optional
-rw-r--r-- 1 root root 7010 8 okt 09:37 81-arch.rules
-rw-r--r-- 1 root root 82 14 sep 12:48 90-hal.rules
-rw-r--r-- 1 root root 28 19 okt 16:19 99-fuse.rules
-rw-r--r-- 1 root root 201 15 nov 03:45 device-mapper.rules

I'll try to enable it and see if that helps.

Regards

André

Tried it and doesn't chsnge a thing.

Regards

Well, one thing did change now udev takes forever to start up at boot when the eth0 and eth1 are set correct but now eicd and the network daemon can't see my network devices at all. So now I can't get net at all on this machine.

Regards

Andre

instead of udev, have a look at iftab and ifrename.

pacman -S netcfg, modify the default /etc/iftab, and add net-rename to your DAEMONS=() before network.

I name my wireless ipw2100 ipw0, and my hardware ethernet rl0, but you can rename them whatever you like.

netcfg isn't required, but it's convenient as the netcfg package contains the rc.d/ daemon and the example config.

Here is a funny observation. Since I use wicd, I can set the names of my wired and wireless to what I want (depending on what ifconfig -a says of course). Since Arch almost consistly loads the wireless first (eth0) and the wired second (eth1). If I switch those names in wicd and reconnect again I have network immediately (can switch between dhcp and static ip also) and I've been able to get net everytime after rebooting 4 times now. This is in the end maybe not a solution, because I don't know how to change the names, if I just wanted to use the network daemon. I think the reason why the Ubuntu CD worked, was that my wireless card wasn't detected at all (no entry in networkmanager-applet), hence no confusion. But the strange thing is still why the wireless wants to be named eth0, because when I did the fresh install the wired connection was the only thing installed and it was called eth0. I set the wireless up later via AUR and yaourt (broadcom-wl) and then I added the wl module to rc.conf and restarted. Also at the fresh install I had troubles getting net and had to reboot several times until I could continue the installation (doing pacman -Syu for the first time).

Regards

André

This might be unrelated but when I boot I get list errors rigt after grub (after loading initramfs) saying

Buffer I/O error on device sda3, logical block 1745542400
Buffer I/O error on device sda3, logical block 1745542401
Buffer I/O error on device sda3, logical block 1745542402
Buffer I/O error on device sda3, logical block 1745542403
Buffer I/O error on device sda3, logical block 1745542404
RTNL: assertion failed at net/core/fub_rules.c (625)
RTNL: assertion failed at net/ipv4/devinet.c (1045)
RTNL: assertion failed at net/ipv4/imgp.c (1348)
RTNL: assertion failed at net/ipv4/imgp.c (1199)
usb2-2: device not accepting address at 2, error -71 (doesn't appear always)
mknod: File exists

What do these errors mean and where do they come from? Is it the hardware of some
thing software?

Regards

André

Those are most likely hardware errors. Use smartmontools to check out if your hard disk (in this case sda) is still OK. Recommend you run a 'long' test.

I never used smartmontools, how od I use it and set up to do the long test plus I'm running fakerad (RAID 0)?

Regards

André

man smartctl will tell you that.

Well, I ran a long check on sda and smartmontools found no errors. I ran

smartctl -t long /dev/sda

and then looked at the error log file

[root@andre ~]# smartctl -l error /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=== START OF READ SMART DATA SECTION ===
SMART Error Log Version: 1
No Errors Logged

Regards

André

This looks like your partition table is either incorrect, or your filesystems don't match the partitions you created (this happens when you re-partition your disk, but don't re-read your partition table for example):
sda: rw=0, want=1953536123, limit=976773168
attempt to access beyond end of device

That can be because when I installed Arch on my new machine with the fakeraid (dmraid & RAID 0) I created the partitions with cfdisk via the installer. After setting them up and everything I wrote the table and cfdisk gave the warning (partition table created but could not reread the table). Is there a way to fix this?

Regards

André

Well, at the moment everything seems ok (the last 2 days at least). I have net all the time. Wireless is at eth0 and wired is on eth1 and using wicd. On my old machine eth0 and eth1 switch between eachother constantly so I have to move the network cable constantly after reboot.

Regards

André

Well, still everything works so far once in a while though the etho and eth1 get switched and I have to reboot. After the upgrade to the latest kernel 2.6.28 the above mentioned errors

Buffer I/O error on device sda3, logical block 1745542400
Buffer I/O error on device sda3, logical block 1745542401
Buffer I/O error on device sda3, logical block 1745542402
Buffer I/O error on device sda3, logical block 1745542403
Buffer I/O error on device sda3, logical block 1745542404
RTNL: assertion failed at net/core/fub_rules.c (625)
RTNL: assertion failed at net/ipv4/devinet.c (1045)
RTNL: assertion failed at net/ipv4/imgp.c (1348)
RTNL: assertion failed at net/ipv4/imgp.c (1199)
usb2-2: device not accepting address at 2, error -71 (doesn't appear always)

are gone :-D.

Regards

André

You can stop the swapping of eth0/eth1 if you follow the instructions in my post above to use net-rename. It's very easy.

Closing this as not a bug.