New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On PPC64 "rear mkrescue" fails with BugError in 310_network_devices.sh #1701
Comments
@schubiduuu rear -D mkrescue as requested by ReaR's BUG error message. |
Sorry for the delay but here is the log. |
Is anything else missing for further investigation? |
@rmetrich # git log -p --follow usr/share/rear/rescue/GNU/Linux/310_network_devices.sh | egrep 'Unexpected operational state|^commit|^Author' ... commit 15567ede425401b008e5b1680db36a2c62752b8f Author: Renaud Métrich + BugError "Unexpected operational state '$state' for '$network_interface'." ... this BugError belongs to your new 310_network_devices.sh code. |
@schubiduuu How does your network layout looks like? Can we see the output of
@schabrolles Can you also have a closer look at this issue please? |
: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 brd 127.255.255.255 scope host lo inet 127.0.0.2/8 brd 127.255.255.255 scope host secondary lo inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 9000 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether f6:44:7d:92:b2:04 brd ff:ff:ff:ff:ff:ff inet 10.224.0.14/25 brd 10.224.0.127 scope global eth0 inet6 fe80::f444:7dff:fe92:b204/64 scope link valid_lft forever preferred_lft forever 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000 link/ether f6:44:7d:92:b2:05 brd ff:ff:ff:ff:ff:ff inet 10.224.0.230/25 brd 10.224.0.255 scope global eth1 inet6 fe80::f444:7dff:fe92:b205/64 scope link valid_lft forever preferred_lft forever |
@schubiduuu Is your network eth0 currently operational? In the code, I'm relying on "operstate" to set up the link up/down mode. But it looks like this is not reliable. |
/sys/class/net/eth0/addr_assign_type:0 |
and yes eth0 is operational. |
@schubiduuu could you please set the interface explictly down ( |
I will post the output tomorrow morning as I need to agree on a downtime. |
@schubiduuu maybe do that on eth1? |
Unfortunately both interfaces are used productively. |
ok, as a workaround, you may edit the |
ok, I will edit the file and start another test. |
could you dump the |
@rmetrich Should I perform "lspci -vv" and "lsmod" on the source system? or after rebooting via the rescue iso? SIOCSIFFLAGS: Invalid argument |
Please run
If that fails, please provide debug output for |
No output for "lspci -vv" and for "lsmod": Module Size Used by st 51177 0 sr_mod 23543 0 ide_cd_mod 39518 0 cdrom 51354 2 sr_mod,ide_cd_mod joydev 16492 0 nfs 583351 0 fscache 85204 1 nfs lockd 113448 1 nfs auth_rpcgss 61878 1 nfs nfs_acl 3888 1 nfs sunrpc 366268 7 nfs,lockd,auth_rpcgss,nfs_acl fuse 127337 1 xfs 1077534 7 loop 25404 0 ipv6 1881 1 ipv6_lib 440978 127 ipv6 sg 45603 0 nx_crypto 45618 0 ibmveth 32645 0 ext3 206842 2 jbd 102286 1 ext3 mbcache 10827 1 ext3 dm_mirror 23171 0 dm_region_hash 16423 1 dm_mirror dm_log 15841 2 dm_mirror,dm_region_hash linear 6958 0 sd_mod 54931 8 crc_t10dif 1691 1 sd_mod dm_service_time 4794 5 dm_least_pending 4374 0 dm_queue_length 4402 0 dm_round_robin 3996 0 dm_multipath 30372 8 dm_service_time,dm_least_pending,dm_queue_length,dm_round_robin scsi_dh_hp_sw 6663 0 scsi_dh_rdac 12199 0 scsi_dh_emc 10476 0 scsi_dh_alua 17206 0 scsi_dh 11199 5 dm_multipath,scsi_dh_hp_sw,scsi_dh_rdac,scsi_dh_emc,scsi_dh_alua dm_snapshot 47338 0 dm_mod 127248 58 dm_mirror,dm_log,dm_multipath,dm_snapshot ibmvscsic 37737 16 scsi_transport_srp 8416 1 ibmvscsic scsi_tgt 17750 1 scsi_transport_srp scsi_mod 291791 12 st,sr_mod,sg,sd_mod,scsi_dh_hp_sw,scsi_dh_rdac,scsi_dh_emc,scsi_dh_alua,scsi_dh,ibmvscsic,scsi_transport_srp,scsi_tgt |
You may need to be root for |
I am root on the system and the system says "dmidecode: not found". When executing "rear -D mkresuce" there are no error messages. |
Could you upload the log anyway, for me to check. |
Sorry, I missed a "operstate" use just above.
should be replaced by
|
With that, in the log file, you should see something like the following: Was "unknown":
Should then be "up":
|
Do you mean the log file used by "rear -D mkrescue"? |
yes, the one you uploaded 1 hour ago. I'll then produce a real patch once we know more about a reliable way of getting the interface status. |
@schubiduuu @jsmeix I'll submit a patch later today (or tomorrow), based on |
@jsmeix: Even if I don't need the full network configuration of the source system, I should be able to change manually the IP config with commands like ifconfig. When trying to change the IP address or changing the operational state of eth0 it keeps telling me: SIOCSIFFLAGS: Invalid argument. |
@schubiduuu |
I can use the usual command while the source system is running but not in the recovery environment. |
Should I start another issue for the nonfunctional network commands? |
What do you exactly mean by "nonfunctional network commands?". |
Within the recovery environment after booting via a rear ISO I am not able to make any changes to the network configuration. Ifconfig or ip don't work as I get always this error message: SIOCSIFFLAGS: Invalid argument |
Then, yes, this looks like a different issue, unless the network script, when running, sets up something bad (but I doubt). |
Ok and I did this change but still get the same error. The strange thing about this issue is that I was able to use an older rear version for some time but then it didn't work suddenly. |
Try comparing the modules loaded ( |
lsmod on source system: Module Size Used by st 51177 0 sr_mod 23543 0 ide_cd_mod 39518 0 cdrom 51354 2 sr_mod,ide_cd_mod joydev 16492 0 nfs 583351 0 fscache 85204 1 nfs lockd 113448 1 nfs auth_rpcgss 61878 1 nfs nfs_acl 3888 1 nfs sunrpc 366268 7 nfs,lockd,auth_rpcgss,nfs_acl fuse 127337 1 xfs 1077534 7 loop 25404 0 ipv6 1881 1 ipv6_lib 440978 127 ipv6 sg 45603 0 nx_crypto 45618 0 ibmveth 32645 0 ext3 206842 2 jbd 102286 1 ext3 mbcache 10827 1 ext3 dm_mirror 23171 0 dm_region_hash 16423 1 dm_mirror dm_log 15841 2 dm_mirror,dm_region_hash linear 6958 0 sd_mod 54931 8 crc_t10dif 1691 1 sd_mod dm_service_time 4794 5 dm_least_pending 4374 0 dm_queue_length 4402 0 dm_round_robin 3996 0 dm_multipath 30372 8 dm_service_time,dm_least_pending,dm_queue_length,dm_round_robin scsi_dh_hp_sw 6663 0 scsi_dh_rdac 12199 0 scsi_dh_emc 10476 0 scsi_dh_alua 17206 0 scsi_dh 11199 5 dm_multipath,scsi_dh_hp_sw,scsi_dh_rdac,scsi_dh_emc,scsi_dh_alua dm_snapshot 47338 0 dm_mod 127248 58 dm_mirror,dm_log,dm_multipath,dm_snapshot ibmvscsic 37737 16 scsi_transport_srp 8416 1 ibmvscsic scsi_tgt 17750 1 scsi_transport_srp scsi_mod 291791 12 st,sr_mod,sg,sd_mod,scsi_dh_hp_sw,scsi_dh_rdac,scsi_dh_emc,scsi_dh_alua,scsi_dh,ibmvscsic,scsi_transport_srp,scsi_tgt lsmod on recovery system: Module Size Used by ipv6 1881 1 ipv6_lib 440978 137 ipv6 dm_mod 127248 0 nx_crypto 45618 0 ibmveth 32645 0 ibmvscsic 37737 0 scsi_transport_srp 8416 1 ibmvscsic scsi_tgt 17750 1 scsi_transport_srp scsi_mod 291791 3 ibmvscsic,scsi_transport_srp,scsi_tgt example of executed command: ifconfig -a -s eth0 1.2.3.4/24 |
By default during "rear mkrescue/mkbackup" at least those But by default not all those currently loaded modules on the original system See the description of the config variables To be more on the safe side you may include all If you use special hardware that may even To enforce loading of kernel modules during startup If you use special hardware that needs firmware But both But at least on some POWER architecture systems |
I used MODULES=( 'all_modules' ) and FIRMWARE_FILES=( 'yes' ) in the local.conf. Unfortunately this didn't help. Did I do anything wrong? |
As in |
@jsmeix this looks good to me, but I will not be able to test in the coming days. |
In 310_network_devices.sh use a fallback to get interface state. Since some network drivers do not set the operstate value in /sys/class/net/INTERFACE/operstate to 'up' or 'down' we fallback to using the /sys/class/net/INTERFACE/carrier value, see #1701
With #1719 merged |
@rmetrich |
According to #1741 BUG in /usr/share/rear/rescue/GNU/Linux/310_network_devices.sh line 306: 'Unexpected operational state 'unknown' for ... could have also happened on non-POWER architecture, BUG in /usr/share/rear/rescue/GNU/Linux/310_network_devices.sh line 306: 'Unexpected operational state 'unknown' for 'vnet0'.' |
Relax-and-Recover (ReaR) Issue Template
Fill in the following items before submitting a new issue
(quick response is not guaranteed with free support):
BUG in /usr/share/rear/rescue/GNU/Linux/310_network_devices.sh line 306:
'Unexpected operational state 'unknown' for 'eth0'.'
rear-system.log:
The text was updated successfully, but these errors were encountered: