Custom Query (16363 matches)
Results (1060 - 1062 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #6168 | obsolete | problems with ata trigger hostbyte=DID_BAD_TARGET / ext3 mounted readonly | ||
| Description |
I don't know when this started, i use Save machine state/Restore machine state instead of booting, and I can't run most things anymore: timeless@timeless-tablet:~$ uptime bash: /usr/bin/uptime: Input/output error timeless@timeless-tablet:~$ touch ~ touch: setting times of `/home/timeless': Read-only file system timeless@timeless-tablet:~$ mount|grep rootfs rootfs on / type rootfs (rw) timeless@timeless-tablet:~$ fsck / fsck 1.41.4 (27-Jan-2009) [142525.444929] end_request: I/O error, dev sda, sector 4442137 [142525.446041] end_request: I/O error, dev sda, sector 4442137 fsck.ext2: Input/output error dmesg includes: [117949.000986] ata1.00: exception Emask 0x0 SAct 0x3 SErr 0x0 action 0x6 frozen
[117949.003383] ata1.00: cmd 61/08:00:51:c5:77/00:00:00:00:00/40 tag 0 ncq 4096 out
[117949.003467] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[117949.004018] ata1.00: status: { DRDY }
[117949.005022] ata1.00: cmd 61/08:08:a9:05:20/00:00:00:00:00/40 tag 1 ncq 4096 out
[117949.005033] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
[117949.006250] ata1.00: status: { DRDY }
[117949.018431] ata1: hard resetting link
...
[117998.034920] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[117998.034926] end_request: I/O error, dev sda, sector 3726569
[117998.036349] Aborting journal on device sda1.
[117998.037541] sd 0:0:0:0: [sda] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK,SUGGEST_OK
[117998.037546] end_request: I/O error, dev sda, sector 3674129
[117998.038852] Buffer I/O error on device sda1, logical block 459266
[117998.040267] lost page write due to I/O error on sda1
[117998.040295] JBD: Detected IO errors while flushing file data on sda1
[117998.236539] ext3_abort called.
[117998.238241] EXT3-fs error (device sda1): ext3_journal_start_sb: Detected aborted journal
[117998.241917] Remounting filesystem read-only
|
|||
| #5865 | fixed | problems with Gemplus USB SmartCard Reader on osol-130 (x64) with VirtualBox 3.1.2 => fixed in SVN | ||
| Description |
Not sure how to proceed... Have checked privileges and all, but I keep getting the famous acces denied... and it seems that the device is "held" instead of "captured". Do I need to do some type of cfgadm magic? bash-4.0$ VBoxManage list usbhost VirtualBox Command Line Management Interface Version 3.1.2 (C) 2005-2009 Sun Microsystems, Inc. All rights reserved. Host USB Devices: UUID: ab78832f-54fc-4114-b885-40bc4ee87cce VendorId: 0x08e6 (08E6) ProductId: 0x3437 (3437) Revision: 1.0 (0100) Manufacturer: Gemplus Product: USB SmartCard Reader Address: 0x8e6:0x3437:256:/pci@0,0/pci10de,cb84@4 Current State: Held UUID: 62ea2dbe-8477-4cce-9d7a-87f93e92ce97 VendorId: 0x0bda (0BDA) ProductId: 0x0158 (0158) Revision: 81.149 (81149) Manufacturer: Generic Product: USB2.0-CRW SerialNumber: 20060413092100000 Address: 0xbda:0x158:20885:/pci@0,0/pci10de,cb84@4,1 Current State: Busy |
|||
| #959 | fixed | problems with BIOS reals beyond LBA boundary? | ||
| Description |
I observe the following problems with VirtualBox. An explanation that fits this problem patterns is that there is a problem with BIOS initiated reads beyond the LBA boundary of a disk.
Here is an explanation that fits the above problem pattern: in real mode, reads from disks that are beyond the LBA boundary (separate interface INT 0x10,AH=0x42 IIRC) is broken. FAT/NTFS MBR uses the AH=0x02 interface for everything beyond sector 1024*255*63. This fits all problem/no problems:
Side notes: Vmware is able to boot into ALL of the 3 cases were virtual box isn't able. For problem 4, I made sure to add the necessary drivers into the criticaldevice section of the windows registry. I'm not sure if I did that correctly, but what really indicates that there is a problem at a much lower level (bios level) is that, in problem 3 I'm not only unable to boot into windows, but also unable to boot into the recovery console. the recovery console refuses to load because HAL.dll is not found (as I said HAL.dll is likely to reside after the LBA boundary). My next test case is: format a plain NTFS disk, fill it up with to 8GB, and do a fresh win xp install. The result (if my thesis is correct) should be that NTLDR is not found, and booting dies. (will do that in about a week, I just filed this bug now so that this issues is known, and this knowledge isn't lost if for some reason I forget to do this) Of course, if you have further insight you are free to provide it. |
|||

