Re: Syslogd message...............

2012-06-18 Thread Charlie
On Mon, 18 Jun 2012 12:34:49 +0200 "Alberto Fuentes alberto.fuen...@qindel.com" suggested this: >If you dont have any raid and it changed names for you too maybe is >not just my raid case :S I don't have any raid aL. My external hard drive mounts with UUID and also says that /media/usb0 is mou

Re: Syslogd message...............

2012-06-18 Thread Alberto Fuentes
On 06/18/2012 11:57 AM, Charlie wrote: [...] does it shift between remounts or does it shift names live? It used to shift live. [...] Maybe with raid the problem is different? Well, its a hardware raid and its presented to the system as a single disk. I have to pass a few parameters to

Re: Syslogd message...............

2012-06-18 Thread Charlie
On Mon, 18 Jun 2012 08:44:42 +0200 "Alberto Fuentes alberto.fuen...@qindel.com" suggested this: >On 06/16/2012 02:31 PM, Charlie wrote: >> It changes the device from /dev/sdb1 to /dev/sdd1 and back again. >> >> I am now mounting it as /dev/sdb1. That's what it has always been, >> and then it sta

Re: Syslogd message...............

2012-06-17 Thread Alberto Fuentes
On 06/16/2012 02:31 PM, Charlie wrote: It changes the device from /dev/sdb1 to /dev/sdd1 and back again. I am now mounting it as /dev/sdb1. That's what it has always been, and then it started to drop out while I was looking through the files and wouldn't mount and came up as /dev/sdd1 etc.. It

Re: Syslogd message...............

2012-06-17 Thread Sthu Deus
Good time of the day, Charlie. You worte: > It changes the device from /dev/sdb1 to /dev/sdd1 and back again. Oh, I got it now - You did not mention that. > I am now mounting it as /dev/sdb1. That's what it has always been, and > then it started to drop out while I was looking through the file

Re: Syslogd message...............

2012-06-17 Thread Camaleón
On Sun, 17 Jun 2012 08:43:49 +1000, Charlie wrote: > On Sat, 16 Jun 2012 17:13:26 + (UTC) "Camaleón noela...@gmail.com" > suggested this: >>Being USB volumes in external enclosures it can be that they were badly >>umounted and thus the message. I would run "fsck" over the umounted >>volumes

Re: Syslogd message...............

2012-06-17 Thread Charlie
On Sun, 17 Jun 2012 10:45:26 +0100 "keith km3...@gmail.com" suggested this: >On Sat, 2012-06-16 at 22:31 +1000, Charlie wrote: > >> It changes the device from /dev/sdb1 to /dev/sdd1 and back again. >> >> I am now mounting it as /dev/sdb1. That's what it has always been, >> and then it started t

Re: Syslogd message...............

2012-06-17 Thread keith
On Sat, 2012-06-16 at 22:31 +1000, Charlie wrote: > It changes the device from /dev/sdb1 to /dev/sdd1 and back again. > > I am now mounting it as /dev/sdb1. That's what it has always been, and > then it started to drop out while I was looking through the files and > wouldn't mount and came up as

Re: Syslogd message...............

2012-06-16 Thread Charlie
On Sat, 16 Jun 2012 17:13:26 + (UTC) "Camaleón noela...@gmail.com" suggested this: >On Sat, 16 Jun 2012 08:14:03 +1000, Charlie wrote: > >> This happens with both powered and powered only through a USB >> connection, external hard drives. Both with ext3 file systems: >> >> Message from sysl

Re: Syslogd message...............

2012-06-16 Thread Camaleón
On Sat, 16 Jun 2012 08:14:03 +1000, Charlie wrote: > This happens with both powered and powered only through a USB > connection, external hard drives. Both with ext3 file systems: > > Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721] > journal commit I/O error Being USB vol

Re: Syslogd message...............

2012-06-16 Thread Charlie
On Sat, 16 Jun 2012 11:30:34 +0700 "Sthu Deus sthu.d...@gmail.com" suggested this: >> mount /mnt/lpics >> mount: special device /dev/sdd1 does not exist > >Why don't You mount /dev/sdb1 but /dev/sdd1 ? > >Also, You can mount by UUID. > >What I would do in Your situation is: > >. connect HDD d

Re: Syslogd message...............

2012-06-15 Thread Sthu Deus
Good time of the day, Charlie. You worte: > Tried different cabling: > > blkid says, > > /dev/sdb1: UUID="4bb48afe-02d7-487f-a51f-ff378edbc98d" TYPE="ext3" > > Then in a terminal: > > mount /mnt/lpics > mount: special device /dev/sdd1 does not exist Why don't You mount /dev/sdb1 but /dev/s

Re: Syslogd message...............

2012-06-15 Thread Charlie
On Fri, 15 Jun 2012 23:48:12 +0700 "Sthu Deus sthu.d...@gmail.com" suggested this: >Good time of the day, Charlie. > > >You worte: > >> This happens with both powered and powered only through a >> USB connection, external hard drives. Both with ext3 file systems: >> >> Message from syslogd@noma

Re: Syslogd message...............

2012-06-15 Thread Sthu Deus
Good time of the day, Charlie. You worte: > This happens with both powered and powered only through a > USB connection, external hard drives. Both with ext3 file systems: > > Message from syslogd@nomad at Jun 16 08:04:30 ... > kernel:[ 3187.986721] journal commit I/O error > > Seems to be more

Re: Syslogd message...............

2012-06-15 Thread Charlie
On Fri, 15 Jun 2012 14:21:00 +0200 "Alberto Fuentes alberto.fuen...@qindel.com" suggested this: >On 06/16/2012 12:14 AM, Charlie wrote: >> >> This happens with both powered and powered only through a >> USB connection, external hard drives. Both with ext3 file systems: >> >> Message from syslogd

Re: Syslogd message...............

2012-06-15 Thread Alberto Fuentes
On 06/16/2012 12:14 AM, Charlie wrote: This happens with both powered and powered only through a USB connection, external hard drives. Both with ext3 file systems: Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721] journal commit I/O error This seems regular error in disk

Syslogd message...............

2012-06-15 Thread Charlie
This happens with both powered and powered only through a USB connection, external hard drives. Both with ext3 file systems: Message from syslogd@nomad at Jun 16 08:04:30 ... kernel:[ 3187.986721] journal commit I/O error Seems to be more funny things happening with this testing system than anyt