On 21 Aug 2023 19:53, Tim Woodall wrote:
On Mon, 21 Aug 2023, Tim Woodall wrote:
On Wed, 24 Aug 2022, Tim Woodall wrote:
I got this error while installing build-essential
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb
On 21/08/2023 18:53, Tim Woodall wrote:
On Mon, 21 Aug 2023, Tim Woodall wrote:
On Wed, 24 Aug 2022, Tim Woodall wrote:
I got this error while installing build-essential
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb
On Mon, 21 Aug 2023, Tim Woodall wrote:
On Wed, 24 Aug 2022, Tim Woodall wrote:
I got this error while installing build-essential
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb (subprocess): decompressing archive
On Wed, 24 Aug 2022, Tim Woodall wrote:
I got this error while installing build-essential
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb (subprocess): decompressing archive
On Wed, 2022-08-24 at 11:48 +0100, Tim Woodall wrote:
> On Wed, 24 Aug 2022, Andy Smith wrote:
>
> > Hello,
> >
> > On Wed, Aug 24, 2022 at 08:23:11AM +0100, Tim Woodall wrote:
> > > dpkg-deb (subprocess): decompressing archive
> > >
On 24/08/2022 08:23, Tim Woodall wrote:
There's no SMART errors or anything like that either.
Anyone got any ideas - any logging I should add to try and track down
where the issue might be?
Sure, check dmesg as a first thing, if its a block device error it will
be recorded there.
--
With
On Wed, 24 Aug 2022, Andy Smith wrote:
Hello,
On Wed, Aug 24, 2022 at 08:23:11AM +0100, Tim Woodall wrote:
dpkg-deb (subprocess): decompressing archive
'/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb' (size=4015516)
member 'data.tar': lzma error: compressed data is corrupt
Hello,
On Wed, Aug 24, 2022 at 08:23:11AM +0100, Tim Woodall wrote:
> dpkg-deb (subprocess): decompressing archive
> '/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb'
> (size=4015516) member 'data.tar': lzma error: compressed data is corrupt
[…]
> Am I right that this must be a
Am 24. Aug 2022, um 08:23:11 Uhr schrieb Tim Woodall:
> There's no SMART errors or anything like that either.
Run badblocks to check your disk.
> Anyone got any ideas - any logging I should add to try and track down
> where the issue might be?
Check the disk with badblocks and test the
I got this error while installing build-essential
Preparing to unpack .../03-libperl5.34_5.34.0-5_arm64.deb ...
Unpacking libperl5.34:arm64 (5.34.0-5) ...
dpkg-deb (subprocess): decompressing archive
'/tmp/apt-dpkg-install-zqY3js/03-libperl5.34_5.34.0-5_arm64.deb' (size=4015516)
member
The drives/partitions are all identified by UUID or NAME, not
/dev/sd*. The external disks all have external power.
I should have been more specific about my main question: given a
failure on one drive, is it to be expected that the connections of all
the drives sharing the same USB connection
On Thu, Feb 02, 2017 at 06:00:59PM -0800, Ross Boylan wrote:
> I have multiple drives in a Vantec HX4 case connect by USB 3.0 It
> seems a disk I/O error* causes the entire USB connection to reset,
> causing all the drives to be remapped and screwing up the connections
> to all the disks in the
Ross Boylan wrote:
> I do seem to have a hardware problem with one of the disks (though I'm
> now getting an error for the replacement). I moved it to a single
> drive case connected by USB and got errors when reading the same
> sectors that originally caused trouble. It also exhibited the same
I have multiple drives in a Vantec HX4 case connect by USB 3.0 It
seems a disk I/O error* causes the entire USB connection to reset,
causing all the drives to be remapped and screwing up the connections
to all the disks in the case.
Is this expected behavior for the linux kernel?
I'm running
On 24 Apr 2011, Allan Wind wrote:
On 2011-04-24 22:18:02, Anthony Campbell wrote:
I just did a fresh installation of Debian. Everything seemed to go off
correctly but when I came to reboot I got:
Non-system disk or disk error: replace and strike any key when ready.
I reinstalled
I just did a fresh installation of Debian. Everything seemed to go off
correctly but when I came to reboot I got:
Non-system disk or disk error: replace and strike any key when ready.
I reinstalled twice and also reinstalled grub twice. No errors reported.
I suspect a hard disk failure or cmos
On 2011-04-24 22:18:02, Anthony Campbell wrote:
I just did a fresh installation of Debian. Everything seemed to go off
correctly but when I came to reboot I got:
Non-system disk or disk error: replace and strike any key when ready.
I reinstalled twice and also reinstalled grub twice
I get the following error when try to boot one lenovo 3000 N1000 laptop:-
When trying to boot from hard disk:-
Error 21: Selected disk does not exist...
When booting from live cd. This is the output from dmesg.
...
ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
ata1.00: failed
On Tuesday 01 March 2011 09:24:27 Kousik Maiti wrote:
Time to get a new hard drive. Hope you don't have too much data on it you don't
have a copy somewhere else.
Thierry
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
On Tue, Mar 01, 2011 at 01:54:27PM +0530, Kousik Maiti wrote:
I get the following error when try to boot one lenovo 3000 N1000 laptop:-
When trying to boot from hard disk:-
Error 21: Selected disk does not exist...
When booting from live cd. This is the output from dmesg.
...
ata1.00
On Tue, Mar 1, 2011 at 08:24, Kousik Maiti kousiks...@gmail.com wrote:
I get the following error when try to boot one lenovo 3000 N1000 laptop:-
When trying to boot from hard disk:-
Error 21: Selected disk does not exist...
When booting from live cd. This is the output from dmesg
on 13:54 Tue 01 Mar, Kousik Maiti (kousiks...@gmail.com) wrote:
I get the following error when try to boot one lenovo 3000 N1000 laptop:-
When trying to boot from hard disk:-
Error 21: Selected disk does not exist...
When booting from live cd. This is the output from dmesg.
...
ata1.00
Hi.
I have problem with my laptop.
When I use graphic enviroment some program like icedove don't response.
I think, this is depend on disk.
I put in attachment dmesg output. The last lines, I think, give the answer.
Thanks
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with
pch0317 wrote at 2010-08-14 13:56 -0500:
I put in attachment dmesg output. The last lines, I think, give the answer.
No attachment...
signature.asc
Description: Digital signature
in the first one i tried] it
say's:
GRUB hard disk error
What can I do?
Different UUID?
In the console as root type blkid to get UUID of your partitions then
setup /etc/fstab accordingly, you also may need to change the kernel
syntax too.
--
Jimmy Johnson
SimplyMEPIS 8.5 at sda9
Registered
tried] it
say's:
GRUB hard disk error
What can I do?
I already tried:
grub-install /dev/sdc -that's the pendrive name [bios - hard drive
emulation=hard drive, not auto]
or:
# grub
find /boot/grub/stage1
hd0,0
hd1,0
root (hd0,0)
setup (hd0,0)
etc.
What's the solution? Please help me:\
I can't
Hallo,
beim Versuch einer Installation von einem SCSI CD Laufwerk an einem
Adaptec Controller (AHA-2940U/UW/D) gibt es folgende Fehlermeldungen:
isolinux: Disk error 80, AX = 42FD, drive 9F
isolinux: Disk error 80, AX = 42A0, drive 9F
Die erste beim Versuch 31r1a mit Kernel 2.6 zu
Also sprach Stefan Tichy [EMAIL PROTECTED] (Fri, 17 Feb 2006 18:34:07
+0100):
Hallo,
He,
Ich könnte ja wohl nachträglich den 2.4 Kernel durch 2.6 ersetzen,
aber ich will halt schon wissen, was die Ursache ist.
Die Fehlermeldung deutet auf einen Lesefehler hin. Vielleicht bekommt
der
Hi Alvin. Once again, thanks for your ultra-fast reply. I have not been
able to understand completly what you've said so I'll comment along your
mail, ok?
Alvin Oga wrote:
On Tue, 30 Nov 2004, Joao Clemente wrote:
...but when one is suposed to get the GRUB menu, I get simply a
GRUB Hard Disk
Joao Clemente wrote:
[snip]
3) install into the boot sector of the partition (/dev/hda1 ) instead
MBR of the disk ( /dev/hda )
- but the mbr must be empty too
I am not certain of you're refering to grub, lilo, or both. I see no
reason why grub (or lilo) would fail when installed in MBR
* Joao Clemente [EMAIL PROTECTED] [2004 Nov 30 20:09 -0600]:
grub is unreasonably finicky
What means finicky? 1rst time I see this word
Probably the best way to explain it is to say that it is very
particular about everything being setup the way it likes it and if not
then it fails. In
it will reboot to continue from the freshly installed
system...
...but when one is suposed to get the GRUB menu, I get simply a
GRUB Hard Disk Error message
googling revealed problems when using dual-booting, XP or stuff like
that. I am using a full-disk install over a win95 installation, so no
dual
On Tue, 30 Nov 2004, Joao Clemente wrote:
...but when one is suposed to get the GRUB menu, I get simply a
GRUB Hard Disk Error message
grub is unreasonably finicky
you have several choices..
1) boot into dos a: fdisk /mbr
-- wipe it out and try grub-install again
On these old machines it was often necessary to use a scheme called
Logical Block Addressing (LBA) to allow MS-DOS access to the entire
drive. Many later 486 machines incorporated LBA into the BIOS and once
activated is rather seemless.
If the BIOS did not support LBA the drive manufacturer
Sehr geehrtes Debian Team,
letztens wollte ich mir
endlich Debian auf meinem Testrechner installieren. Ich scheiterte aber schon
vor der Installation beim Booten von der CD.
Und zwar wird mir
gemeldet
Zitat:
ISOLINUX
1.67/debian-cd 2002-05-14 isolinux: Disk
wird mir gemeldet
Zitat:
ISOLINUX 1.67/debian-cd 2002-05-14 isolinux: Disk error 00, drive F0
Der gleiche Fehler kommt sowohl bei der Debian Mini-CD als auch bei
Debian CD 1-3.
Falls der Rechner ein Diskettenlaufwerk hat wäre es möglich, einen Satz
Bootdisketten (ich glaube drei Stück
Hallo,
Ich möchte mein System zur Sicherheit wegen Festplattengeräusche
sichern.
Dazu möchte ich mondo resczue verwenden.
in /var/log/mondo-archive.log gibt es einen Fehler von Mindi.
Da es ein script ist, und weil mein Horizont nicht reicht, das alles zu
verstehen weiß ich nicht welches
Can someone tell me what is causing the following errors?
Sep 24 21:53:32 localhost kernel: hda: dma_intr: status=0x51
{ DriveReady SeekComplete Error }
Sep 24 21:53:32 localhost kernel: hda: dma_intr: error=0x40
{ UncorrectableError }, LBAsect=22581489, sector=1825392
Sep 24 21:53:32
On Mon, Sep 01, 2003 at 09:24:23AM -0300, Listas wrote:
What this errors means? A Hard Disk or SCSI Controller problem?
I don't know. Have you tried to test the drive with the utility that
I believe most SCSI controllers have built in? This utility can usually
be run from the controller
a hole
at offset 0
SCSI disk error : host 0 channel 0 id 2 lun 0 return code = 2802
[valid=0] Info fld=0x0, Current sd08:25: sense key Not Ready
Additional sense indicates Logical unit not ready, initializing command
required
scsidisk I/O error: dev 08:25, sector 32
EXT2-fs error (device sd(8,37
I run Woody (3.0 r1), and always boot from a floppy
and normally clear out /usr/src after compiling
kernels and producing a boot floppy.
Have just compiled 2.4.21 so that I can compile an
nvidia module. I've probably compiled my own kernel
over 20 times (using make-kpkg) and never had any
I'm getting the following:
Feb 24 04:02:45 consort kernel: EXT2-fs error (device ide0(3,5)): ext2_write_inode:
unable to read inode block - inode=258689, block=524360 Feb 24 04:02:45 consort
kernel: EXT2-fs error (device ide0(3,5)):
ext2_write_inode: unable to read inode block - inode=258690,
On Mon, Feb 24, 2003 at 01:05:37PM -0500, Walter Tautz wrote:
ext2_write_inode: unable to read inode block - inode=258690, block=524360 Feb 24
04:02:51 consort kernel: hda: read_intr: status=0x59 { DriveReady SeekComplete
DataRequest Error }
Feb 24 04:02:51 consort kernel: hda: read_intr:
Good morning. Please reply directly, I cannot subscribe to the list from
work.
I'm receiving an error that I would like some help with, if possible. To
wit:
# lilo
Warning: Int 0x13 function 8 and function 0x48 return different
head/sector geometries for BIOS drive 0x80
Added Linux-2.4.16 *
Hi Everyone,
I have just installed Potato on an old P233. I put it
on a new 17GB UDMA drive (Seagate), which the bios
does not recognize correctly. It works fine with
kernel 2.2.17, but I get the following message from
time to time:
hda: status timeout: state=0xd0 { Busy }
hda: no DRQ after
Hi Everyone,
I have just installed Potato on an old P233. I put it
on a new 17GB
UDMA drive (Seagate), which the bios does not
recognize
correctly. It works fine with kernel 2.2.17, but I get
the folloing
message from time to time:
hda: status timeout: state=0xd0 { Busy }
hda: no DRQ after
hdb:hdb: set_multmode: status=0x51 {DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 {DriveStatusError }
hdb1 hdb2
VFS: Mounted root (ext2 filesystem) readonly.
It looks like your hard disk doesn't support multimode - reading/writing
multiple disk blocks at once. What kernel
Gerardo Garcia Alvarez wrote:
I get this error when the kernel starts
Partition check:
hda: hda1
hdb:hdb: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
hdb1 hdb2
VFS: Mounted root (ext2 filesystem) readonly.
You should
I get this error when the kernel starts
Partition check:
hda: hda1
hdb:hdb: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
hdb1 hdb2
VFS: Mounted root (ext2 filesystem) readonly.
Linux is in /dev/hdb1 and works fine. I have
A long time ago, in a galaxy far, far way, someone said...
I get this error when the kernel starts
Partition check:
hda: hda1
hdb:hdb: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 { DriveStatusError }
hdb1 hdb2
VFS: Mounted root (ext2
On Sat, 29 Jan 2000, Phil Brutsche wrote:
A long time ago, in a galaxy far, far way, someone said...
I get this error when the kernel starts
Partition check:
hda: hda1
hdb:hdb: set_multmode: status=0x51 { DriveReady SeekComplete Error }
hdb: set_multmode: error=0x04 {
Hello. I started getting a disk error on my Maxtor 17.2 GB disk tonight.
It's been running fine for over 2 months, and my current uptime is 63 days
with no apparent disk problems.
Here's how I have my disk partitioned:
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/hda2
Hi,
I'm having a strange problem here (ok, maybe it's not a real
problem, yet). Every day (at least for the last two), I'm having a SCSI
disk error entry in my kern.log, occurring at 6:25 am.
Yes, only at this exact time I'm having problems.
I ran 45+ kernel
Mario Olimpio de Menezes writes:
| Hi,
|
| I'm having a strange problem here (ok, maybe it's not a real
| problem, yet). Every day (at least for the last two), I'm having a SCSI
| disk error entry in my kern.log, occurring at 6:25 am.
| Yes, only at this exact time I'm having
On 1 Dec 1999, Martyn Pearce wrote:
Mario Olimpio de Menezes writes:
| Hi,
|
| I'm having a strange problem here (ok, maybe it's not a real
| problem, yet). Every day (at least for the last two), I'm having a SCSI
| disk error entry in my kern.log, occurring at 6:25 am.
| Yes
Mario Olimpio de Menezes writes:
| I forgot to say that I already did this: went to single mode (init
| 1), then ran: mount -t ext2 -r -o remount,ro /dev/sdaX /mount-point
| Then, e2fsck -c /dev/sdaX
|
| Well, no badblocks, no problem at all in the whole disk.
|
On 1 Dec 1999, Martyn Pearce wrote:
Mario Olimpio de Menezes writes:
| I forgot to say that I already did this: went to single mode (init
| 1), then ran: mount -t ext2 -r -o remount,ro /dev/sdaX /mount-point
| Then, e2fsck -c /dev/sdaX
|
| Well, no badblocks, no problem at
Mario Olimpio de Menezes writes:
| Yes, it's interesting.
| The box is at work (here). I think the hardware (fan cooler, power supply,
| etc) is OK. This is a new machine (arrived last friday Nov 26th).
|
| Yes, the machine is permanently networked but I can't say which other
| processes
On Wed, Dec 01, 1999 at 09:33:51AM -0200, Mario Olimpio de Menezes wrote:
On 1 Dec 1999, Martyn Pearce wrote:
Mario Olimpio de Menezes writes:
| I forgot to say that I already did this: went to single mode (init
| 1), then ran: mount -t ext2 -r -o remount,ro /dev/sdaX /mount-point
I ran into this problem tonight and I'm trying to be very cautious
so if anyone can give me (a semi newbie) some advice I'd appreciate it.
Here's what happened. I used CFDISK to re-designate a extra partition on
my hard drive from BeOS type (it wasn't being used at all) to Windows95 Fat
32
so
On Mon, Nov 01, 1999 at 10:24:27PM -0500, Jon Hughes wrote:
I'm cautious about clearing some illegal block for fearing I'll lose data or
what not.
And you're right :)
Try to change it again, but this time with 'fdisk' instead of 'cfdisk',
some cdfisk versions are not very good, especially with
Hi dear debianers;
I've installed Slink and worked fine. (hard disk A for Windows;
hard disk B for Linux, boot from loadlin or sometimes from floppy.)
Now I want to install the kernel-package downloaded from Debian
for a kernel compile (kernel-source-2.0.36 downloaded as well).
Look like it could be a problem with motherboard or controller. When I booted
up tonight there are no problems.
Running badblocks detects no problems with the paritition and dumpe2fs lists
none either.
I will have to pull the machine to bits, look for anything loose and clean the
fans.
Hi All,
Recently when debian is coming up, the following message is displayed:
hda: dma_intr: status=0x51 { DriveReady SeekComplete Error }
hda: dma_intr: error=0x40 { UncorrectableError }, LBAsect=65662, sector=65598
end_request: I/O error, dev 03:01, sector 65598
EXT2-fs error (device 03:01):
Don't know how to solve it, but if it helps anyone who knows more about hard
disks than me my hd gives the first2 lines and it works fine.
You could try running e2fsck -c if you can get it working, as that could
correct the third error (possibly).
Peter Allen
I am attempting to install debian with floppies. I successfully get
through all the installation until I attempt to install the kernel and
modules. It installs stuff from the rescue floppy fine, but when
installing from the drivers disk, I get the following error:
I am having a problem installing debian linux. when the installation
program tries to write to the hard drive it produces nothing but error
messages. It goes by too fast but I think it says that the drive door
on my hard drive is open. I don't understand this because I know that
my hard drive
67 matches
Mail list logo
