Re: [SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sun, Sep 29, 2019 at 03:04:48AM +0200, local10 wrote: > Sep 28, 2019, 11:24 by bouncingc...@gmail.com: > > > Having read that, I don't see any admission that fsck makes any > > changes if run without any options as it seems you did. So I > > wonder what caused the change in the debugfs message.

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, Sep 28, 2019 at 04:01:27PM +1000, David wrote: > > Maybe better to hide the stdout from md5sum: > > # find junk -xdev -type f -exec md5sum '{}' >/dev/null \; > > To be more precise, that hides the stdout from both md5sum and find, > but I don't think that matters to the goal. This is corr

Re: [SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 28, 2019, 11:24 by bouncingc...@gmail.com: > Having read that, I don't see any admission that fsck makes any > changes if run without any options as it seems you did. So I > wonder what caused the change in the debugfs message. > man wasn't available in BusyBox so I had to limit myself to the

Re: [SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sun, 29 Sep 2019 01:24:00 +1000 David wrote: > Having read that, I don't see any admission that fsck makes any > changes if run without any options as it seems you did. So I > wonder what caused the change in the debugfs message. I'll offer a guess. Modern disk drives have a full up controlle

Re: [SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 22:31, local10 wrote: > Sep 28, 2019, 02:06 by loca...@tutanota.com: > > Good advice, thanks. I have a backup drive which is almost a > > mirror copy of the failing one, so that's why I am not very worried > > about it. I'm going to try to fix it in a couple of days, so let

Re: [SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 28, 2019, 08:31 by loca...@tutanota.com: > The end result: > Starting with the "The end result:" the email provider I use screwed up the email formatting, in the original it was a numbered list which should've looked something like this: The end result: 1. fsck reports the repaired fs as cl

[SOLVED, kind of] Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 28, 2019, 02:06 by loca...@tutanota.com: > Good advice, thanks. I have a backup drive which is almost a mirror copy of > the failing one, so that's why I am not very worried about it. I'm going to > try to fix it in a couple of days, so let's see how it goes. > So I forced fsck to run at re

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 28, 2019, 00:50 by bouncingc...@gmail.com: > In your situation, I would: > 1) backup everything important ASAP. > and (assuming your init is systemd): > 2) read here > https://www.linuxuprising.com/2019/05/how-to-force-fsck-filesystem.html > 3) do something like a one-off use of > fsck.mode=f

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 15:57, David wrote: > On Sat, 28 Sep 2019 at 15:05, David wrote: > > > I had another thought: if you care curious about where the problem > > is, maybe you could run some read-only command that reads > > every part of your disk, and see if it gets stuck anywhere. > > For ex

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 15:05, David wrote: > I had another thought: if you care curious about where the problem > is, maybe you could run some read-only command that reads > every part of your disk, and see if it gets stuck anywhere. > For example: > # find / -xdev -type f -exec md5sum '{}' \; O

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Buy spinrite from www.grc.com, that will work, but after fixing, I would copy to a new drive. You will need a dos disk but this program works well. On Fri, 27 Sep 2019 22:38:59 -0400, local10 wrote: > > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > > Hi, I assume you are attempting to follo

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 12:39, local10 wrote: > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > It's telling you that the filesystem itself is broken/unreadable. > > I assume you know what inodes are, if not then you should > > read about that. > > In such a case, I think that it is not possib

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

On Sat, 28 Sep 2019 at 12:39, local10 wrote: > Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > > > > In such a case, I think that it is not possible to repair this filesystem. > > What I find weird about this that the filesystem (it's a root filesystem) > appears to be fully functional, it boots

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

Sep 27, 2019, 20:08 by bouncingc...@gmail.com: > Hi, I assume you are attempting to follow a procedure similar > to this one: > https://www.smartmontools.org/wiki/BadBlockHowto#Repairsinafilesystem > > Yes, a different docum

Re: ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

out what file this block number belongs to failed (see below, > /dev/sda2 contains an ext4 root file system that was mounted as root when > debugfs was run): > > # debugfs > debugfs 1.44.5 (15-Dec-2018) > debugfs: open /dev/sda2 > debugfs: testb 950 > Block 950 marked in

ext4: debugfs: icheck: Input/output error while calling ext2fs_block_iterate

): # debugfs debugfs 1.44.5 (15-Dec-2018) debugfs:  open /dev/sda2 debugfs:  testb 950 Block 950 marked in use debugfs:  icheck 950 icheck: Input/output error while calling ext2fs_block_iterate icheck: Can't read next inode while doing inode scan debugfs:  quit # Any ideas? Thanks # uname -a Linu

Re: dd: error reading '/dev/sr0': Input/output error

md wrote: > Using an old PATA-to-USB cable, I attached a 15 year old PATA DVD Drive to > the SATA based computer I've been using. With this drive (/dev/sr1), dd > seems to working fine without having to precede it with dvdbackup -M. Thomas Schmitt wrote: > But aren't those copied sectors still sc

Re: dd: error reading '/dev/sr0': Input/output error

Hi, md wrote: > > libdvdread: Attempting to retrieve all CSS keys Pascal Hambourg wrote: > Didn't these messages about CSS keys ring a bell in anybody's mind ? In hindsight, yes. > Check the kernel logs with dmesg. This yielded a nice theory about libdvdcss and not going to jail. md wrote:

Re: dd: error reading '/dev/sr0': Input/output error

Using an old PATA-to-USB cable, I attached a 15 year old PATA DVD Drive to the SATA based computer I've been using. With this drive (/dev/sr1), dd seems to working fine without having to precede it with dvdbackup -M. In the dvdread README on github, I found this: '. If you attempt to read

Re: dd: error reading '/dev/sr0': Input/output error

Le 10/12/2018 à 06:34, md a écrit : MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s dd: error reading '/dev/sr0': Input/output error (...) MD> dvdbackup -M libdvdread: Attempting to retrieve all CSS keys libdvdread: This c

Re: dd: error reading '/dev/sr0': Input/output error

On Monday 10 December 2018 12:57:46 md wrote: > In the scenarios when dd fails, the amount that dd reads before > failing varies from to movie dvd to movie dvd. At times dd will read > 400MB before failing. > > A few FWIW snippets: > dvdbackup 'fixes' the dd problem > xorriso doesn't 'fix' the dd

Re: dd: error reading '/dev/sr0': Input/output error

Hi, md wrote: > [] sr 4:0:0:0: [sr0] tag#20 Sense Key : Illegal Request [current] > [] sr 4:0:0:0: [sr0] tag#20 Add. Sense: Read of scrambled sector without > authentication > [] sr 4:0:0:0: [sr0] tag#20 CDB: Read(10) 28 00 00 3b 23 c0 00 00 40 00 This is probably CSS access restriction. I gues

Re: dd: error reading '/dev/sr0': Input/output error

In the scenarios when dd fails, the amount that dd reads before failing varies from to movie dvd to movie dvd. At times dd will read 400MB before failing. A few FWIW snippets: dvdbackup 'fixes' the dd problem xorriso doesn't 'fix' the dd problem xorriso has similar problem to dd dvdbackup 'fixes'

Re: dd: error reading '/dev/sr0': Input/output error

On Monday 10 December 2018 04:37:10 Thomas Schmitt wrote: > Hi, > > Jude DaShiell wrote: > > Why not prefix that dd command with a sudo udevadm settle command > > and only allow the dd command to run on success case? > > man udevadm says: > > udevadm settle [options] >Watches the udev ev

Re: dd: error reading '/dev/sr0': Input/output error

> > > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso > > > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s > > > dd: error reading '/dev/sr0': Input/output error > > > > Do you see fresh messages in the output of dmesg ? > > Like >

Re: dd: error reading '/dev/sr0': Input/output error

On Monday 10 December 2018 03:44:20 Thomas Schmitt wrote: > Hi, > > Gene Heskett wrote: > > > > Classic slow spinup. > > I wrote: > > > After 33 MiB of reading ? > > > > That much would would also invalidate the dry sliders theory > > There might well be mechanical or optical problems involved. As

Re: dd: error reading '/dev/sr0': Input/output error

Hi, Jude DaShiell wrote: > Why not prefix that dd command with a sudo udevadm settle command and > only allow the dd command to run on success case? man udevadm says: udevadm settle [options] Watches the udev event queue, and exits if all current events are handled. We have no i

Re: dd: error reading '/dev/sr0': Input/output error

On Mon, 10 Dec 2018, Thomas Schmitt wrote: > Date: Mon, 10 Dec 2018 02:45:43 > From: Thomas Schmitt > To: debian-user@lists.debian.org > Cc: mickyd...@protonmail.com > Subject: Re: dd: error reading '/dev/sr0': Input/output error > Resent-Date: Mon, 10 Dec 2018 07:46:

Re: dd: error reading '/dev/sr0': Input/output error

Hi, Gene Heskett wrote: > > > Classic slow spinup. I wrote: > > After 33 MiB of reading ? > That much would would also invalidate the dry sliders theory There might well be mechanical or optical problems involved. As said, the failure patterns of drives are variform. Thus my question whether d

Re: dd: error reading '/dev/sr0': Input/output error

> dd: error reading '/dev/sr0': Input/output error > > Do you see fresh messages in the output of dmesg ? > Like > > Dec 2 13:56:33 ... kernel: [...] Sense Key : Medium Error [current] > Dec 2 13:56:33 ... kernel: [...] Info fld=0x69c0 > Dec 2 13:56:33 ... k

Re: dd: error reading '/dev/sr0': Input/output error

On Monday 10 December 2018 02:34:48 md wrote: > >> When copying a dvd to file on the harddrive, I'm getting the > >> message dd: error reading '/dev/sr0': Input/output error > >> If I first run dvdbackup, then Ctrl-C out of it. I can then reissue > &g

Re: dd: error reading '/dev/sr0': Input/output error

>> When copying a dvd to file on the harddrive, I'm getting the message >> dd: error reading '/dev/sr0': Input/output error >> If I first run dvdbackup, then Ctrl-C out of it. I can then reissue >> the dd command and it will finish fine. If I eject the d

Re: dd: error reading '/dev/sr0': Input/output error

Hi, md wrote: > When copying a dvd to file on the harddrive, I'm getting [...] > MD> sudo dd if=/dev/sr0 of=/sdb1/movie.iso > 32596480 bytes (33 MB, 31 MiB) copied, 7.00018 s, 4.7 MB/s > dd: error reading '/dev/sr0': Input/output error Do you see fresh messages

Re: dd: error reading '/dev/sr0': Input/output error

On Monday 10 December 2018 00:34:58 md wrote: > When copying a dvd to file on the harddrive, I'm getting the message > dd: error reading '/dev/sr0': Input/output error > If I first run dvdbackup, then Ctrl-C out of it. I can then reissue > the dd command and it will

dd: error reading '/dev/sr0': Input/output error

When copying a dvd to file on the harddrive, I'm getting the message dd: error reading '/dev/sr0': Input/output error If I first run dvdbackup, then Ctrl-C out of it. I can then reissue the dd command and it will finish fine. If I eject the dvd then insert another dvd, the same s

Input/output error on BluRay file cmp

I'm running Debian Squeeze on an older 32bit system that I'm using as a file server. I use a BluRay writer to make compressed backups overnight. However lately I've been having some problems. The initial cp seems to work but when I do a cmp or rsync to test or fix cp errors, the writer sometime

blueman-applet input/output error

Dear list, blueman-applet has some problem in by debian box. I have blueman 1.21-4.1+b1 installed with debian wheezy. Obviously I have added the user at bluetooth group; dbus is also working. I can on/off as well as search new bluetooth devices through blueman-applet but when try to add or pair

Re (2): wodim: Input/output error.

Andrei, From: Andrei Popescu Date: Wed, 23 Feb 2011 09:37:14 +0200 > As far as I understand from the manpage the device is specified with > dev=... Oops; yes. Sorry for the distraction. I should have reviewed the man page rather than rely on memory. > Does it work if you use the full na

Re: wodim: Input/output error.

On Ma, 22 feb 11, 17:27:55, peasth...@shaw.ca wrote: > Jigdo retrieved this *netinst.iso and reported "OK: Checksums match, image is > good! " > root@dalton:~# ls -l /root/deb*.iso > -rw-r--r-- 1 root root 198338560 Feb 22 16:41 > /root/debian-6.0.0-i386-netinst.is > o > > Wodim failed as follow

wodim: Input/output error.

locks remaining: 262849 Speed set to 1411 KB/s Starting to write CD/DVD at speed 8.0 in real TAO mode for single session. Last chance to quit, starting real write in0 seconds. Operation starts. Waiting for reader process to fill input buffer ... input buffer ready. Performing OPC... Starting

Re: 'input / output error' when using ntfs-3g on Sid-based Helix Live CD

Bob McGowan wrote: Rogelio wrote: I'm having some weird issues with Helix (a Sid / Knoppix based distribution). For whatever reason, I periodically get an "input/output error" while a disk is mounted, and the only way to fix it is to umount and then mount again via ntfs-3g.

Re: 'input / output error' when using ntfs-3g on Sid-based Helix Live CD

Rogelio wrote: I'm having some weird issues with Helix (a Sid / Knoppix based distribution). For whatever reason, I periodically get an "input/output error" while a disk is mounted, and the only way to fix it is to umount and then mount again via ntfs-3g. Here's a more d

'input / output error' when using ntfs-3g on Sid-based Helix Live CD

I'm having some weird issues with Helix (a Sid / Knoppix based distribution). For whatever reason, I periodically get an "input/output error" while a disk is mounted, and the only way to fix it is to umount and then mount again via ntfs-3g. Here's a more detailed list of what

Re: input output error(5)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Pobega wrote: > On Tue, Mar 20, 2007 at 07:54:38PM -0400, Chris Parker wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> hello all, >> >> I've got a dell power edge 2400 with an adaptec scsi card. Attached to >> the card are 2 1

Re: input output error(5)

On Tue, Mar 20, 2007 at 07:54:38PM -0400, Chris Parker wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > hello all, > > I've got a dell power edge 2400 with an adaptec scsi card. Attached to > the card are 2 16G disks on the 1st raid channel, while on the 2nd > channel are 3 136G driv

input output error(5)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 hello all, I've got a dell power edge 2400 with an adaptec scsi card. Attached to the card are 2 16G disks on the 1st raid channel, while on the 2nd channel are 3 136G drives in a raid 5. Now when I try to copy alot of tiff images off a usb hard dri

Re: smartctl usage (was Re: input/output error, looks bad!)

Tyler Smith wrote: On 2007-03-18, Tyler Smith <[EMAIL PROTECTED]> wrote: On 2007-03-18, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: and what this show? /usr/sbin/smartctl -a -d ata /dev/ I decided to start with the long self test, which is running now: smartctl -t long -d ata /dev/sda Ok,

Re: input/output error, looks bad!

On 2007-03-18, Andrei Popescu <[EMAIL PROTECTED]> wrote: > Some of your values seem very high. Though according to Google's > report even 1 indicates failure to come. For comparison here are my > values: > > Reallocated_Sector_Ct 0 > ... > Reallocated_Event_Count 0 > ... > > I hope yo

smartctl usage (was Re: input/output error, looks bad!)

On 2007-03-18, Tyler Smith <[EMAIL PROTECTED]> wrote: > On 2007-03-18, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: >> >> and what this show? >> >> /usr/sbin/smartctl -a -d ata /dev/ >> > > I decided to start with the long self test, which is running now: > > smartctl -t long -d ata /dev/sda > Ok, I

Re: input/output error, looks bad!

Tyler Smith <[EMAIL PROTECTED]> wrote: Some of your values seem very high. Though according to Google's report even 1 indicates failure to come. For comparison here are my values: Reallocated_Sector_Ct 0 ... Reallocated_Event_Count0 ... I hope you get to finish your backup. R

Re: input/output error, looks bad!

On 2007-03-18, Hugo Vanwoerkom <[EMAIL PROTECTED]> wrote: > > and what this show? > > /usr/sbin/smartctl -a -d ata /dev/ > I didn't have smartctl installed. I just installed it now, and the output of smartctl -a -d ata /dev/sda is pasted below. I'm not sure how to use this tool yet, but from what

Re: input/output error, looks bad!

- most commands were greeted with something like: bash: /bin/df Input/Output Error I could still us ls, and I got aptitude to open but with big ugly warnings about how it couldn't write files and no changes could be made. shutdown didn't work (Input/Output Error etc.) , and logging out

input/output error, looks bad!

greeted with something like: bash: /bin/df Input/Output Error I could still us ls, and I got aptitude to open but with big ugly warnings about how it couldn't write files and no changes could be made. shutdown didn't work (Input/Output Error etc.) , and logging out dumped me at a log

Got a ccl : lib/crc16.mod.c : Input/output error when compiling the 2.6.16.14 kernel

ccl : lib/crc16.mod.c : Input/output error Does anybody know why it happened? I'm guessing it's probably because of the PCCard support option that I enabled, but I don't see why. Thanks, -Glen -- Glen Yu | 416-739-4861 | [EMAIL PROTECTED] --

Input/output error

NB: This email and its contents are subject to our email legal noticewhich can be viewed at http://www.sars.gov.za/Email_Disclaimer.pdf Hi   I’m experiencing a problem on SLES 9. When I run reboot on the command line I get a bash: /sbin/reboot: Input/output error. Can you please

Re: ls: filename: Input/output error

Sep 24, 2003 at 06:41:11PM +0800: > > Hello all, > >Thanks in advance for any helps. > >When I list the content of a directory, I can't see the file. > >But when I execute "ls -al filename", I got "Input/output error". > >I ju

Re: ls: filename: Input/output error

Simon Tneoh Chee-Boon, Wed, Sep 24, 2003 at 06:41:11PM +0800: > Hello all, >Thanks in advance for any helps. >When I list the content of a directory, I can't see the file. >But when I execute "ls -al filename", I got "Input/output error". >

Re: ls: filename: Input/output error

uot;ls -al filename", I got "Input/output error". >I just wonder, can I remove this file by using commands like > "debugfs"? >If yes, can I do it without shutting down my server, because it's a > live environment? >If no, what is the right way to

ls: filename: Input/output error

Hello all, Thanks in advance for any helps. When I list the content of a directory, I can't see the file. But when I execute "ls -al filename", I got "Input/output error". I just wonder, can I remove this file by using commands like "debugfs"? I

mt: /dev/nst0: Input/output error

as playing with Arkeia. Now I get: ns1:~> sudo mt -f /dev/nst0 status mt: /dev/nst0: Input/output error The machine is remote so I've tried a soft reboot but to no avail. I don't think it's Arkeia's fault because it happened once before and a poer down reboot did the t

Serial port input/output error...

Little problem which may be related to my Potato setup. My two serial ports don't work - setserial always returns "Input/output error," even when I try just the -g parm, or with autoconfig. stty returns the same thing. The hardware is fine, since it works with SuSE 6.4 and vari

input/output error

/bin#./LCDd -t 20x4 -d MtxOrb -b on MtxOrb_init: failed (Input/output error) Error loading driver MtxOrb. Continuing anyway... Well, they don't all continue anyways, but all get the i/o error. I have used /dev/ttys0 and /dev/ttys1, its got to be one of them. Actually, it needs to be /dev/

Re: /dev/fd0: Input/output error (making base disks)

On Tue, Dec 21, 1999 at 07:53:11PM -0600, Matt Garman wrote: > > Hello: > > I'm trying to make the "base" disks to do a potato install. > > When I do a "dd if=root.bin of=/dev/fd0," I get the following: > > dd: /dev/fd0: Input/output error

Re: /dev/fd0: Input/output error (making base disks)

Subject: /dev/fd0: Input/output error (making base disks) Date: Tue, Dec 21, 1999 at 07:53:11PM -0600 In reply to:Matt Garman Quoting Matt Garman([EMAIL PROTECTED]): >| >| Hello: >| >| I'm trying to make the "base" disks to do a potato install

Re: /dev/fd0: Input/output error (making base disks)

On 21/12/99 Matt Garman wrote: I'm trying to make the "base" disks to do a potato install. When I do a "dd if=root.bin of=/dev/fd0," I get the following: dd: /dev/fd0: Input/output error 1113+0 records in 1112+0 records out looks like a disk error prevented the c

/dev/fd0: Input/output error (making base disks)

Hello: I'm trying to make the "base" disks to do a potato install. When I do a "dd if=root.bin of=/dev/fd0," I get the following: dd: /dev/fd0: Input/output error 1113+0 records in 1112+0 records out And again with "cmp root.bin /dev/fd0": cmp: /dev/fd0:

Re: ls: file: Input/output error

debian > debian >What could have caused this I/O error anyway? almost anything, if the system crashed, or had some bad physical sectors on it ..or a program crashed while it was writing to disk may of curropted some stuff..hard to tell. you can always avoid a reboot and you can always (i believe)

Re: ls: file: Input/output error

> you try running a e2fsck on it ? Yes, but it was /home which was always busy, although I stoped every process I could think of using files in /home. Isn't there a tool to check which process is using a certain part of the filesystem? > run e2fsck -c too, i think that is the option to check for

Re: ls: file: Input/output error

Mail wrote: > When I do a ls I get: > > host:~/m> ls > file > > But ls -la gives: > > host:~/m> ls -la > ls: file: Input/output error > total 3 > drwx--S--- 3 user group 1024 Nov 3 16:34 . > drwxr-sr-x 28 user group 2048 Nov

ls: file: Input/output error

When I do a ls I get: host:~/m> ls file But ls -la gives: host:~/m> ls -la ls: file: Input/output error total 3 drwx--S--- 3 user group 1024 Nov 3 16:34 . drwxr-sr-x 28 user group 2048 Nov 3 16:33 .. I tried rm -rf /home/user/m but this also gives an I/O error:

Re: modem prob: cannot open /dev/tty2...input/output error

> my modem was working fine to dselect (with pon), but after i downloaded > and dpkg'd tons of files, i can no longer pon nor can i wvdial (which > gives the "cannot open /dev/tty2...imput/output error" message). > > i installed a new modem, thinking the other was fried, but i still get > the same

pppd[256]: tcgetattr: Input/output error(5) ?

1000 Aug 12 09:28:58 csnote pppd[256]: tcgetattr: Input/output error(5) Aug 12 09:28:59 csnote pppd[256]: Exit. I checked that the setup files are still correct. I have kept my custom compiled 2.0.34 kernel so far and did an 'update-modules' after converting files to the new modutils

mgetty input/output error

ser='/Auto Jun 5 10:20:59 serv1 PAM_pwdb[378]: (ppp) session opened for user paul by ppp(uid=0) Jun 5 10:21:00 serv1 mgetty[17271]: TIOCMBIS failed: Input/output error Jun 5 10:21:00 serv1 mgetty[17271]: cannot turn off soft carrier: Input/output error Jun 5 10:21:00 serv1 mgetty[17271]: