Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#35866 - "WRITE SAME Failed" error in installation.

Attached to Project: Arch Linux
Opened by saladom (saladom) - Thursday, 20 June 2013, 13:35 GMT
Last edited by Bartłomiej Piotrowski (Barthalion) - Sunday, 23 June 2013, 12:02 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:I'm trying to install Arch linux using the VMware now. but this error blocks me. :(

I just followed the beginner wiki.

Mounting the /dev/sda1 to /mnt makes a error all the time when I install the Archlinux(2013.06.01) newly.

Should I wait for the new linux kernal version to solve this error?


Additional info:
* package version(s)

Arch Linux 2013.06.01

* config and/or log files etc.


Steps to reproduce:
This task depends upon

Closed by  Bartłomiej Piotrowski (Barthalion)
Sunday, 23 June 2013, 12:02 GMT
Reason for closing:  Not a bug
Comment by Jan de Groot (JGC) - Thursday, 20 June 2013, 16:59 GMT
Is it just printed once, or does it spam your complete terminal?

Recent kernels issue the WRITE SAME command for zeroing. Not every driver, controller or disk supports it, so if it fails the kernel prints a message and reverts to the old manual method.
Comment by saladom (saladom) - Friday, 21 June 2013, 01:17 GMT
Isn't this a big problem? hmm. Thank you.

I want someone to note about this in beginner's guide.

The error bothers me every time I reboot the system after the installation.
Comment by Jan de Groot (JGC) - Friday, 21 June 2013, 09:25 GMT
You'll probably get that error on every reboot, not just the installation.

The kernel devs chose to print this warning at error level instead of just debug.
Comment by saladom (saladom) - Friday, 21 June 2013, 15:57 GMT
OK. Now, I see. Thank you very much for your reply. :D

Loading...