> On 11/17/06, Roby <[EMAIL PROTECTED]> wrote:
> >Seems like doing an umount after/during unplug would lead to data loss
> >if the device had been written to recently. How do buffers get flushed?
No. It's the unplugging device without unpluggins/syncing, what causes data
loss.
On 17.11.06 22:18,
On 11/17/06, Roby <[EMAIL PROTECTED]> wrote:
usbmount:
"This package automatically mounts USB mass storage devices (typically USB
pens) when they are plugged in, and unmounts them when they are removed..."
Seems like doing an umount after/during unplug would lead to data loss
if the device had
Jason Dunsmore wrote:
> On 11/16/06, Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote:
>>
>> you can use 'usbmount' for automatic mounting of usb storage devices.
>> However I'm afraid your USB flashdisk is dead...
>
> The USB flashdisk isn't dead. It works when I mount it manually.
>
> I didn'
On 11/16/06, Matus UHLAR - fantomas <[EMAIL PROTECTED]> wrote:
you can use 'usbmount' for automatic mounting of usb storage devices.
However I'm afraid your USB flashdisk is dead...
The USB flashdisk isn't dead. It works when I mount it manually.
I didn't know about usbmount. I'll give it a
On 16.11.06 12:03, Jason Dunsmore wrote:
> I just started having trouble automounting my usb drive. When I plug
> it in, the kernel recognizes it:
> usb-storage: device found at 5
> usb-storage: waiting for device to settle before scanning
> Vendor: Corsair Model: Flash Voyager Rev: 1.00
>
I just started having trouble automounting my usb drive. When I plug
it in, the kernel recognizes it:
usb 5-8.1: new high speed USB device using ehci_hcd and address 5
usb 5-8.1: configuration #1 chosen from 1 choice
scsi34 : SCSI emulation for USB Mass Storage devices
usb-storage: device found
On Thu, Mar 23, 2006 at 05:55:55PM +, Andy wrote:
> Hello List,
>
> I am running 2x Seagate 250GB SATA-II 7200.9 disks configured as linux
> software RAID-1.
>
> The following errors occasionally appear in /var/log/kern.log:
>
> kernel: ata1: translated ATA stat/err 0x51/84 to SCSI
> SK
Hello List,
I am running 2x Seagate 250GB SATA-II 7200.9 disks configured as linux
software RAID-1.
The following errors occasionally appear in /var/log/kern.log:
kernel: ata1: translated ATA stat/err 0x51/84 to SCSI
SK/ASC/ASCQ 0xb/47/00
kernel: ata1: status=0x51 { DriveReady SeekCompl
On Thu, 2003-03-13 at 05:48, Tom Allison wrote:
> [EMAIL PROTECTED] wrote:
> > On Wed, 12 Mar 2003 17:29:05 -0500
> > Tom Allison <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I've been runnign this PC for about a year now.
> >>I recently upgraded from 2.4.18 to 2.4.20.
> >>And this is the thanks I get.
On Thu, 13 Mar 2003 05:48:01 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] wrote:
> > On Wed, 12 Mar 2003 17:29:05 -0500
> > Tom Allison <[EMAIL PROTECTED]> wrote:
> >
> >
> >>I've been runnign this PC for about a year now.
> >>I recently upgraded from 2.4.18 to 2.4.20.
> >>An
[EMAIL PROTECTED] wrote:
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
---
I suggest you changing this drive before it's too late.
I had the same problem and 5 days after the drive crashes.
On Thu, 2003-03-13 at 00:29, Tom Allison wrote:
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any
Hi
I had a similiar problem with a WD 30gb drive. Used WD diag utils and it
seemed to solve the problem. I would agree on backup, but you may still
get some live out of the drive.
Regards
Tinus
On Thu, 2003-03-13 at 00:29, Tom Allison wrote:
> I've been runnign this PC for about a year now.
> I
On Wed, 2003-03-12 at 17:29, Tom Allison wrote:
> I've been runnign this PC for about a year now.
> I recently upgraded from 2.4.18 to 2.4.20.
> And this is the thanks I get
> Any suggestions? It seems to work.
>
> Mar 12 12:
On Wed, 12 Mar 2003 17:29:05 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> I've been runnign this PC for about a year now.
> I recently upgraded from 2.4.18 to 2.4.20.
> And this is the thanks I get
> Any suggestions? It seems to work.
> --
I've been runnign this PC for about a year now.
I recently upgraded from 2.4.18 to 2.4.20.
And this is the thanks I get
Any suggestions? It seems to work.
Mar 12 12:14:21 gandolf kernel: hda: dma_intr: error=0x84 {
DriveStatu
On Sat, 2003-01-18 at 23:42, Pigeon wrote:
> On Fri, Jan 17, 2003 at 10:06:01AM -0500, Matthew Daubenspeck wrote:
> > I have been running the same woody box for more then 2 years, and I
> > just got the following message:
> >
> > hda: timeout waiting for DMA
> > hda: irq timeout: status=0x58 { Dri
On Fri, Jan 17, 2003 at 10:06:01AM -0500, Matthew Daubenspeck wrote:
> I have been running the same woody box for more then 2 years, and I
> just got the following message:
>
> hda: timeout waiting for DMA
> hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
> hda: timeout waiti
hi ya mathew..
think you should swap your cable for an 18" cable..
and verify the chipset on your mb against the kernel
( might need to install the module for that chipset you're using )
have fun
alvin
- uptime will be sacrificed one way or other...
- the question is do you drag data do
On Fri, Jan 17, 2003 at 12:13:43PM -0800, Alvin Oga wrote:
> - what is the length of your ide cables ??
Standard, I would assume 24"
> - which drive is the "Master" ?? which ide connector is the Master ?
> - is the drive set to cable select or "fixed Master"
This is the only drive on t
hi ya matthew
- what is the length of your ide cables ??
- which drive is the "Master" ?? which ide connector is the Master ?
- is the drive set to cable select or "fixed Master"
- i assume you have the new 80-conductor cables
- power the machine off... wiggle the cables... pull it off an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Friday 17 January 2003 16:06, Matthew Daubenspeck wrote:
> I have been running the same woody box for more then 2 years, and I
> just got the following message:
>
> hda: timeout waiting for DMA
> hda: irq timeout: status=0x58 { DriveReady SeekComple
I have been running the same woody box for more then 2 years, and I
just got the following message:
hda: timeout waiting for DMA
hda: irq timeout: status=0x58 { DriveReady SeekComplete DataRequest }
hda: timeout waiting for DMA
hda: irq timeout: status=0xd0 { Busy }
hda: DMA disabled
ide0: reset:
On Sun, May 27, 2001 at 12:36:31PM -0600, Cameron Matheson wrote:
> Hey,
>
> I enabled DMA in my kernel (w/ the VIA82 support), and now it works (my
> hard drive writes are about six times faster), but now I get weird errors in
> the kernel output:
>
> Partition check:
> hda:hda: dma_intr: s
Hey,
I enabled DMA in my kernel (w/ the VIA82 support), and now it works (my
hard drive writes are about six times faster), but now I get weird errors in
the kernel output:
Partition check:
hda:hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x84 { DriveSta
/bin/tcpserver 0 23 /usr/sbin/in.telnetd&
>
> and the telnet works.
>
> anyone seen this problem before? any suggestions before i replace our
> /dev/hda ?
>
There are a ton of replies to these kinds of drive errors in the
archives. It is strange it only happens when using
Hi all,
on our / partition whenever anyone tries to ssh in we get:
Sep 11 10:45:39 kaos kernel: hda: dma_intr: status=0x51 { DriveReady
SeekComplete Error }
Sep 11 10:45:39 kaos kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=34431, sector=343
68
Sep 11 10:45:39 kaos kernel: end
Hi Wayne, me again, too. :)
>
>
> Try this. Unmount /dev/sdc. Do e2fsck /dev/sdc. Watch fsck as fixes
> the errors.
I've done this, but the problem:
Dec 24 04:03:53 pmurmel kernel:
EXT2-fs error (device 08:0b):
ext2_check_blocks_bitmap:
Wrong free blocks count in super block,
stored =
28 matches
Mail list logo
