Opened 11 years ago
Closed 3 weeks ago
#10203 closed bug (invalid)
disk not accessible in sata mode
Reported by: | bstrik | Owned by: | axeld |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Drivers/Disk | Version: | R1/Development |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Platform: | All |
Description
I tried installing the latest nightly build. This was not possible because the formatting of the partition failed. It fails with a general error. The stable build (rev1alpha4-44702) works like a charm. After investigation i found that hrev46226 is the last one that works for me, hrev46239 and later fail. Please see the attached output. In both cases (46226 and 46239) the output was created by booting from usb and after haiku was started i ran the installer. Please let me know if you need additional information.
Attachments (6)
Change History (15)
by , 11 years ago
Attachment: | listdev46226.txt added |
---|
by , 11 years ago
Attachment: | screenshot46226.png added |
---|
by , 11 years ago
Attachment: | syslog46226.txt added |
---|
by , 11 years ago
Attachment: | listdev46239.txt added |
---|
by , 11 years ago
Attachment: | screenshot46239.png added |
---|
by , 11 years ago
Attachment: | syslog46239.txt added |
---|
comment:1 by , 11 years ago
comment:3 by , 11 years ago
Owner: | changed from | to
---|---|
Status: | new → assigned |
Axel might have an idea...
comment:4 by , 11 years ago
Not really. Does mounting other partitions on that disk (provided there are any) work? If that's the case, seeing the actual SATA request could help finding the cause of this.
comment:6 by , 10 years ago
Component: | - General → Drivers/Disk |
---|---|
Keywords: | disk sata removed |
Platform: | x86 → All |
comment:8 by , 4 years ago
Both syslogs show that the SATA controller is affected by a corrupted PCI BAR which should be fixed in hrev54417. As both syslogs show the corruption it cannot be the root issue here however. As there was no reply after the last request I'm inclined to close as not reprodicible.
comment:9 by , 3 weeks ago
Resolution: | → invalid |
---|---|
Status: | assigned → closed |
The SATA port seems to be reset which causes the BFS error. A bad request could have led to this situation (namely a timeout). How long does it take to have the error logged?
Now looking at the ranges hrev46226-hrev46239, I don't see anything related except maybe hrev46230.