My external USB3 hard drive worked for a while but it gave an error and dropped the drive and now it won’t mount. I’m hoping rebooting will fix it but that is a bit drastic.
[12171.656060] xhci_hcd 0000:02:00.0: ERROR no room on ep ring
[12171.656067] xhci_hcd 0000:02:00.0: ERR: No room for command on command ring
[12171.656074] hub 4-0:1.0: couldn’t allocate port 1 usb_device
I tried a USB2 port and it worked.
[12478.736201] usb 5-1: new high-speed USB device number 3 using ehci_hcd That is not a good solution either because I have more USB3 ports.
I’m using Jessie. Linux cheetah 3.2.0-4-amd64 #1 SMP Debian 3.2.65-1+deb7u2 x86_64 GNU/Linux
After resizing a partition on my hard disk, partition numbering changed and now number 7 comes before and number 6 comes after:
Model: ATA SAMSUNG MP0402H (scsi)
Disk /dev/sda: 40.1GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos Disk Flags:
Number Start End Size Type File system Flags
1 32.3kB 8390MB 8390MB primary fat32 boot
2 8390MB 40.1GB 31.7GB extended lba
5 8390MB 9434MB 1045MB logical linux-swap(v1)
7 9434MB 26.2GB 16.8GB logical ext3
6 26.2GB 40.1GB 13.8GB logical ext3
Is it possible, and how?, to correct that and change back 7 with 6? Googling around found no solution.
Thanks for any help,
hi everybody, I’m fighting since several days with a problem which appeared on my Jessie desktop about 2 weeks ago. Here are the facts
- until end of March, no problem: PC files were seen on all my upnp clients
I was using as upnp clients an Android app on my tablet and an ADSL box (french freebox)
and mediatomb as server (but it used to work also with minidlna)
- since 2 weeks, my PC is not seen on the clients.
(nothing useful in the log file)
I tried to use minidlna instead of mediatomb: same thing.
- I installed minidlna on 2 Debian laptops, and they were seen immediatly, without
any configuration change.
- I have also a Windows 7 laptop, and it is also seen.
I’m unable to find what kind of change on my PC can explain this sudden failure.
I hoped to get some imformation with upnp-inspector, running on the desktop and on one laptop. It actually detected the local minidlna server (not the network ones!)
but I could not find any useful information
As there is no port redirection for the laptops, I don’t see why it should be necessary for the desktop. Anyway, I tried some port redirections, without success.
Has anybody an idea ?
When /etc/fstab has an ext4 filesystem on a logical volume which is itself on a software raid, the system times out waiting for (I think!) fsck on that filesystem. This causes the boot to drop into the emergency shell.
If I just type
I have a bug in liberoffice writer that puts text on a new line instead of using the spacebar to do so. I cant report the bug as the packages is not listed for liberoffice.
>> Just a suggestion: have you considered running LVM …
> I might look into it. My last foray into that territory was with a
> fedora install, single digit version and it was a lost it all
> disaster. And I never did learn what actually failed. But I am now a
> bit wary of LVM’s in general.
I also ran LVM for a while. For my SOHO network, I didn’t have much need or benefit from using LVM and multiple logical volumes in place of multiple partitions on my system drives. I found that the old-fashioned small boot partition, swap partition, and single root partition worked fine and was the easiest to maintain. When I had three 250~300 GB HDD’s and wanted a JBOD, LVM worked great. A striped volume was even more impressive. Then one of 250 GB drives started acting up and ~500 GB
wasn’t enough for my needs, so bought a 3 TB drive and forgot about LVM.
The one annoyance I had with LVM was that it adds another layer of complexity when using an install disc in rescue mode, live CD, etc., or when putting the drive into another computer. But with enough practice, I used to know the commands by memory.
Then I heard about ZFS. So, I tried zfs-fuse (Debian package) and then ZFS on Linux (http://zfsonlinux.org/). ZOL was faster and offered more features (notably de-duplication). The only way to get data on ZFS is with a working system with the right packages. I walked away because:
1. By design, ZFS has a very different mindset from traditional partitions, volume management, and file systems. Just running it required a fair amount of learning. Backing up and restoring ZFS was even harder.
2. Oracle shut the door on FOSS ZFS. Solaris ZFS has moved forward, but OpenZFS hasn’t kept up.
3. ZFS should really be run on a machine with ECC memory, which I don’t have.
4. ZOL is developed and supported by a U.S. government weapons research lab, so I was worried about (more?) back doors.
I evaluated ZFS on FreeBSD 10.1 in January, but ran into unresolved installer/ boot problems with encrypted mirrored ZFS root on USB drives.
Perhaps I was overly ambitious, and should try encrypted mirrored ZFS
root on traditional HDD’s or SSD’s.
Is this the wrong place to ask this question?
———- Forwarded message ——–
My phone is recognized only on USB3 ports (even if it is a USB2 device)
Here are the logs:
Apr 17 20:40:18 bibi kernel: [ 5870.268275] usb 4-1.5: device descriptor read/64, error -71
Apr 17 20:40:18 bibi kernel: [ 5870.456001] usb 4-1.5: device descriptor read/64, error -71
Apr 17 20:40:18 bibi kernel: [ 5870.631908] usb 4-1.5: new high-speed USB device number 4 using ehci-pci Apr 17 20:40:18 bibi kernel: [ 5870.715904] usb 4-1.5: device descriptor read/64, error -71
Apr 17 20:40:18 bibi kernel: [ 5870.903958] usb 4-1.5: device descriptor read/64, error -71
Apr 17 20:40:19 bibi kernel: [ 5871.079823] usb 4-1.5: new high-speed USB device number 5 using ehci-pci Apr 17 20:40:19 bibi kernel: [ 5871.495351] usb 4-1.5: device not accepting address 5, error -71
Apr 17 20:40:19 bibi kernel: [ 5871.567601] usb 4-1.5: new high-speed USB device number 6 using ehci-pci Apr 17 20:40:19 bibi kernel: [ 5871.983124] usb 4-1.5: device not accepting address 6, error -71
Apr 17 20:40:19 bibi kernel: [ 5871.983332] usb 4-1-port5: unable to enumerate USB device
On USB3 :
Apr 17 20:41:10 bibi kernel: [ 5922.900930] usb 1-2: new high-speed USB
device number 3 using xhci_hcd Apr 17 20:41:10 bibi kernel: [ 5923.029489] usb 1-2: New USB device found, idVendorb4, idProduct 08
Apr 17 20:41:10 bibi kernel: [ 5923.029496] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Apr 17 20:41:10 bibi kernel: [ 5923.029499] usb 1-2: Product: RAINBOW 4G
Apr 17 20:41:10 bibi kernel: [ 5923.029502] usb 1-2: Manufacturer:
Apr 17 20:41:10 bibi kernel: [ 5923.029505] usb 1-2: SerialNumber:
Apr 17 20:41:10 bibi mtp-probe: checking bus 1, device 3:
Apr 17 20:41:10 bibi mtp-probe: bus: 1, device: 3 was an MTP device
Is it a ehci problem ?
Shoud I change some USB settings ?
Thanks for your help
PS : I am running Linux bibi 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt9-2 (2015-04-13)
x86_64 GNU/Linux, but it was the same with previous versions of the kernel.
I am as you have proably guessed by now, the originator of some bash scripts that greatly simplify the day to day background operations.
Two of these “scripts” make use of inotifywait to hand them the data they need to do the rest of their jobs.
One of them watches /var/spool/mail and is dependent on finding the
$pidof kmail so it kmail isn’t running, it will not send a message to kmail over the dcop or dbus facility and thereby stuffing up the buffers either of these use.
However, there are generally two instances of inotifywait running because I also use a session to watch another directory where a .jar file running as drivewire for a legacy computer in the basement, so that I
can send a file to a printer it thinks is attached to that machine, but which in reality is actually sent up the usb cable to this machine and dropped into a file here.
Simplified, that file, when closed by drivewire, is then sent via an lp command in that script, thru cups which renders it, then sends it back down that same usb cable to a brother B&W laser printer on that computers desk, where it gets spit out in a beautiful font, at 19 ppm, which is about 20x faster than any pin pounder printer that was ever connected to it 30 years ago.
However, if something goes aglay, my scripts try to kill the inotifywait session, and go silent until the proper $pidof’s are present again.
But occasionally they will kill each others inotifywait sessions as I am currently doing that kill with killall $name. Not the correct way obviously to kill the session that THAT script started.
Because inotifywait is not silent when it launches, I have been forced to do an “var=inotifywait $option_string 2>&1 >/dev/null &” to absorb the noise. Am I dumping the PID return? Can I save that launch return and use it to do a specific “kill $savedvar”?
The manpage for inotifywait is silent in this regard, but I suspect I am looking at the wrong manpage. Perhaps, since its a bash script in both cases, its the bash manual I should be studying?
Thanks for any clues. The bash manual, at around 500 pages, details aren’t that easy to find in that tome.
Cheers, Gene Heskett