Re: initramfs prompt
2014-11-07 14:06 GMT+01:00 Darac Marjal mailingl...@darac.org.uk: On Fri, Nov 07, 2014 at 12:29:31PM +0100, Achim Spreen wrote: Hello. I have a laptop without cdrom or floppy and it isn't usb-bootable. After an unsuccessfull installation mininal of debian wheezy 7.6 i got only a initramfs prompt, busybox and little programs in /sbin and /bin. I can't write on the disk, all changes get lost after reboot. Can i and when how write to the disk ? Here some output: #Grub menu: GNU GRUB ... search --fs-uuid echo ... linux /boot/vmlinuz-3.2.0-4-686-pae ro ... #boot: ... [ 0.927417] Simple Boot Flag at 0x6e set to 0x1 ... [ 0.965249] ERST: Table is not found ! [ 0.965312] GHES: HEST is not enabled ! ... [ 2.129223] sd 0:0:0:0: [sda] Write Protect is off [ 2.129471] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA ... [ 2.484098] sda: sda1 sda5 sda6 sda7 sda8 sda9 sda10 sda11 sda2 ... Begin: Loading essential drivers ... done Begin: Running /scripts/init-premount ... done ... modprobe: module unknown not found in modules.dep mount: can't read '/etc/fstab': No such a file or directory Begin: Running /scripts/local-bottom ... done done Begin: Running /scripts/init-bottom ... mount: mounting /dev on /root/dev failed: No such a file or directory done Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg. [ 4.899187] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver ... BusyBox v1.20.2 (Debian 1:1.20.0-7) built-in shell (ash) Enter 'help' ... /bin/sh: can't access tty: job control turned off (initramfs) _ OK, so initramfs hasn't been able to find your root filesystem. I thought that generally resulted in the kernel panicking, but apparently not. I notice that you haven't told the kernel where your root filesystem is, though, so either autodetection hasn't worked or there is no autodetection. I would suggest adding root=device to the end of the linux /boot/vmlinuz-3.2.0-4-686-pae ro line, where device is any valid way of telling linux where the device is (so you could say /dev/sda1, LABEL=rootfs, UUID=1234-567... etc etc). If that works and you get into your system, re-run sudo update-grub to fix the grub configuration. Bye -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/aaad2d0fdf31192f09b774865a1fd...@andaluciajunta.es Hi, in addition, you can try to locate your hard drive with sfdisk -l . I think that it should work. If not, try : # cd /bin # ln -s busybox sfdisk # sfdisk -l
Re: excessive CPU usage
Hello Gary What does top returns ? - high load average ? / high %sys ? ... 2014-09-29 4:32 GMT+02:00 Gary Roach gary719_li...@verizon.net: On 09/21/2014 11:54 AM, Gary Roach wrote: Hi all For the last few months I have been plagued by very slow response from my system. As an example, it takes 2 1/2 minutes to drag and drop 80 files from my email inbox to the trash bin in icedove. It has taken as high as 5 minutes for iceweasel to load. This problem is not just these packages but also applies to all of the rest of my programs. I am using Debian Wheezy with a i5750 4 core processor on a fast Intel board. I run a kde desktop. All the software is up to date. I have checked all of the log files and can't find any anomalies. Rebooting doesn't help. Using the KDE System Monitor (ksysguard) I have noticed that at least one of the processors goes to 100% and stays there for long periods even though there is no noticeable activity in the process tables. The only other thing I have noticed (the printing just hung up while I am writing this) is that the hard drive indicator comes on and stays on during the processor activity. I ran some checks on the hard drive but found no indication of any hard drive problems. Has anyone else had a similar problem or have any idea what is going on. Thanks in advance Gary R. After several days of investigation, I am still not sure what is causing the problem. I have noted the following: The journaling program jbd2/sda1-8 is taking up most of the I/O time. I do have noatime set in fstab. Having two identical machines is very helpful. My wifes system is fast and never bogs down. Mine is a real dog at this time. I ran iotop on both systems. In my wifes kjournal will pop to the top of the list for a very short period when loading a new application. Otherwise iotop is quiet. On mine kjournal doesn't show at all but jbd2/sda1-8 shows up all of the time. There is constant activity on my system even when nothing is happening. Below is the output from gsmartcontrol. Note that vendor specific attributes 197 and 198 raw values are 757 and 232 respectively and are highlighted in pink on the gsmartcontrol program. My wifes computer's raw values are included in the last column of the smart attributes table for comparison. Also note that there were no errors reported for my wifes system. Do I need to replace the drive or is this fixable. Is this even the root cause of my problems. I'm not too sharp on reading this data an will appreciate comments from a more knowledgeable person. smartctl 5.41 2011-06-09 r3365 [x86_64-linux-3.2.0-4-amd64] (local build) Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD5000AADS-00M2B0 Serial Number:WD-WCAV59765616 LU WWN Device Id: 5 0014ee 25992fc38 Firmware Version: 01.00A01 User Capacity:500,107,862,016 bytes [500 GB] Sector Size: 512 bytes logical/physical Device is:In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is:Sun Sep 28 18:12:56 2014 PDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84)Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 121)The previous self-test completed having the read element of the test failed. Total time to complete Offline data collection: ( 9960) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities:(0x0003)Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability:(0x01)Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 118) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities:(0x3037)SCT Status supported. SCT Feature Control
Re: Suggestions? A small webserver for file upload
Well Lighttpd is pretty easy to use : http://www.lighttpd.net/ 2014-09-26 12:47 GMT+02:00 softwatt softw...@gmx.com: Checkout HFS + Wine. http://www.rejetto.com/hfs/
Re: Strange message, ifup eth0..............
2014-09-08 14:22 GMT+02:00 Charlie aries...@ipstarmail.com.au: Using Debian Jessie, new install Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 07) When I type this ifup eth0 into a root terminal get this message: bound to 192.168.2.2 -- renewal in 2147483648 seconds. /etc/network/if-up.d/00check-network-cable: 72: local: detected:: bad variable name run-parts: /etc/network/if-up.d/00check-network-cable exited with return code 2 Failed to bring up eth0. But the Ethernet connection works? So really nothing to complain about, it just seems strange. But what does concern me is when I type ifdown eth0 the Ethernet connection does **not** terminate and I get this message: ifdown eth0 ifdown: interface eth0 not configured I wonder if anyone might know what is configuring the Ethernet? My /etc/network/interfaces reads: # The primary network interface # allow-hotplug eth0 iface eth0 inet dhcp In the past ifup and ifdown have always worked as expected? This the ifupdown package installed: ifupdown - high level tools to configure network interfaces TIA Charlie -- Registered Linux User:- 329524 *** If you don't get everything you want, think of the things you don't get that you don't want. - Oscar Wilde *** Debian GNU/Linux - just the best way to create magic - -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/2014090810.2503fb0b@taogypsy Hello Charlie, This make me think at this bug : https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726816 Have you checked the version of your packages ? Bests Julien
Re: IPv6 neighbor solicitations to use link-local source address
2014-09-04 12:32 GMT+02:00 mett m...@pmars.jp: On Thu, 4 Sep 2014 18:50:01 +0900 mett m...@pmars.jp wrote: On Thu, 4 Sep 2014 09:12:46 +0200 Julien b jumbo...@gmail.com wrote: Hi mett, thank you for your answer. I hope that I'm not top-posting too ping6 -I doesn't change anything, the box is still using the global scope address. Best regards Julien 2014-09-04 2:32 GMT+02:00 mett m...@pmars.jp: On Thu, 4 Sep 2014 09:04:00 +0900 mett m...@pmars.jp wrote: Hi, When pinging link-local addresses, u need to specify the exit interface. So maybe if u specify the exit interface and another link-local as destination, you might be able to do it: -- mett@asus:~$ ip -6 add show 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 fe80::20c:6eff:fef8:7d1c/64 scope link valid_lft forever preferred_lft forever mett@asus: -- root@tamirrsso:/var/log# ip -6 add show 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 fe80::207:95ff:fed5:2fda/64 scope link valid_lft forever preferred_lft forever root@tamirrsso:/var/log# -- mett@asus:~$ ping6 -I eth0 fe80::207:95ff:fed5:2fda PING fe80::207:95ff:fed5:2fda(fe80::207:95ff:fed5:2fda) from fe80::20c:6eff:fef8:7d1c eth0: 56 data bytes 64 bytes from fe80::207:95ff:fed5:2fda: icmp_seq=1 ttl=64 time=0.433 ms 64 bytes from fe80::207:95ff:fed5:2fda: icmp_seq=2 ttl=64 time=0.205 ms 64 bytes from fe80::207:95ff:fed5:2fda: icmp_seq=3 ttl=64 time=0.201 ms 64 bytes from fe80::207:95ff:fed5:2fda: icmp_seq=4 ttl=64 time=0.256 ms 64 bytes from fe80::207:95ff:fed5:2fda: icmp_seq=5 ttl=64 time=0.199 ms HTH! On Wed, 3 Sep 2014 15:55:38 +0200 Julien b jumbo...@gmail.com wrote: Hello everybody I'm very new to lists.debian.org so please appologize if I am doing something wrong by sending this email. I'm just out of idea with a behavior in NDP and must find a solution. I didn't find anything on the internet. RFC4861 section 7.2.2 says that the source address in NDP neighbor solicitations can be any one of the addresses assigned to the interface. It also says that using the prompting packet's source address ensures that the recipient installs it in its neighbor cache. The latter is the behavior I can see on my boxes (a debian 6.0.9 + custom kernel 3.2.14) and also on a Centos one. # ip -6 addr list 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a10:7e40:edf6:100::32/64 scope global valid_lft forever preferred_lft forever inet6 fe80::a00:27ff:fe02:3cbd/64 scope link valid_lft forever preferred_lft forever # ping6 2a10:7e40:edf6:100::33 -c 3 /dev/null # tcpdump -nli eth0 icmp6 18:09:04.726908 IP6 2a10:7e40:edf6:100::32 ff02::1:ff00:33: ICMP6, neighbor solicitation, who has 2a10:7e40:edf6:100::33, length 32 18:09:04.727373 IP6 2a10:7e40:edf6:100::33 2a10:7e40:edf6:100::32: ICMP6, neighbor advertisement, tgt is 2a10:7e40:edf6:100::33, length 32 18:09:04.727391 IP6 2a10:7e40:edf6:100::32 2a10:7e40:edf6:100::33: ICMP6, echo request, seq 1, length 64 18:09:04.727738 IP6 2a10:7e40:edf6:100::33 2a10:7e40:edf6:100::32: ICMP6, echo reply, seq 1, length 64 My question is : How can I force ndp to use the link-local address assigned to that outgoing device ? (in the trace above, ndp would then send the neighbor solicitation with fe80::a00:27ff:fe02:3cbd source address). This is requested by our customer for security reasons and as far as I can see it complies with RFC4861 as well. If someone had a clue how to do that or if it's just impossible, I would really appreciate your help. Thank you Best resgards Julien By the way, sorry for top-posting... -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20140904093203.696b0eff@asus.tamerr Hey, U cannot ping a global address with a link-local address. If you want to use your link-local address as source, u need to ping the link-local address of your destination (and need to specify exit interface). Global
IPv6 neighbor solicitations to use link-local source address
Hello everybody I'm very new to lists.debian.org so please appologize if I am doing something wrong by sending this email. I'm just out of idea with a behavior in NDP and must find a solution. I didn't find anything on the internet. RFC4861 section 7.2.2 says that the source address in NDP neighbor solicitations can be any one of the addresses assigned to the interface. It also says that using the prompting packet's source address ensures that the recipient installs it in its neighbor cache. The latter is the behavior I can see on my boxes (a debian 6.0.9 + custom kernel 3.2.14) and also on a Centos one. # ip -6 addr list 1: lo: LOOPBACK,UP,LOWER_UP mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 3: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2a10:7e40:edf6:100::32/64 scope global valid_lft forever preferred_lft forever inet6 fe80::a00:27ff:fe02:3cbd/64 scope link valid_lft forever preferred_lft forever # ping6 2a10:7e40:edf6:100::33 -c 3 /dev/null # tcpdump -nli eth0 icmp6 18:09:04.726908 IP6 2a10:7e40:edf6:100::32 ff02::1:ff00:33: ICMP6, neighbor solicitation, who has 2a10:7e40:edf6:100::33, length 32 18:09:04.727373 IP6 2a10:7e40:edf6:100::33 2a10:7e40:edf6:100::32: ICMP6, neighbor advertisement, tgt is 2a10:7e40:edf6:100::33, length 32 18:09:04.727391 IP6 2a10:7e40:edf6:100::32 2a10:7e40:edf6:100::33: ICMP6, echo request, seq 1, length 64 18:09:04.727738 IP6 2a10:7e40:edf6:100::33 2a10:7e40:edf6:100::32: ICMP6, echo reply, seq 1, length 64 My question is : How can I force ndp to use the link-local address assigned to that outgoing device ? (in the trace above, ndp would then send the neighbor solicitation with fe80::a00:27ff:fe02:3cbd source address). This is requested by our customer for security reasons and as far as I can see it complies with RFC4861 as well. If someone had a clue how to do that or if it's just impossible, I would really appreciate your help. Thank you Best resgards Julien
