Hi!
Yesterday was my first try to burn CD on FreeBSD 11.1-RELEASE and for my surprise didn’t work with the same settings which I use few years:
Code:
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
(cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
(cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
(cd1:umass-sim0:0:0:0): SCSI status: Check Condition
(cd1:umass-sim0:0:0:0): SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
(cd1:umass-sim0:0:0:0): Error 22, Unretryable error
(cd1:umass-sim0:0:0:0): cddone: got error 0x16 back
g_vfs_done():cd1[READ(offset=32768, length=2048)]error = 5I have two drives: one is internal and the other external and the problem is with both of them. And I have FreeBSD on iMac 11.1 also few years. I did try to burn CD on OS X and everything is okay and works. No errors.
I tried to burn under GNOME3 and the log shows:
Code:
Checking session consistency (brasero_burn_check_session_consistency brasero-burn.c:1739)
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_set_output_size_for_current_track
BraseroLocalTrack stopping
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_session_output_size
BraseroLocalTrack called brasero_job_get_action
BraseroLocalTrack called brasero_job_get_current_track
BraseroLocalTrack no remote URIs
BraseroLocalTrack stopping
BraseroChecksumFiles called brasero_job_get_output_type
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_set_output_size_for_current_track
BraseroChecksumFiles stopping
BraseroChecksumFiles called brasero_job_get_output_type
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_session_output_size
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_action
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_get_current_track
BraseroChecksumFiles called brasero_job_set_current_action
BraseroChecksumFiles called brasero_job_error
BraseroChecksumFiles finished with an error
BraseroChecksumFiles asked to stop because of an error
error = 1
message = "File "(null)" could not be opened (Inappropriate ioctl for device)"
BraseroChecksumFiles stopping
Session error : File "(null)" could not be opened (Inappropriate ioctl for device) (brasero_burn_record brasero-burn.c:2856)I use
automount
from ports but han I disabled it and build
gvfs
. Under gnome when I put disk in it mounted but the problem is when it start writing (above log).
In devfs.conf I have:
Code:
# Commonly used by many ports
link cd0 cdrom
link cd0 dvd
link cd0 dvdr
link cd0 dvdrw
link cd0 cd
link cd0 cdrw
# Allow a user in the wheel group to query the smb0 device
perm smb0 0666
# Allow members of group operator to cat things to the speaker
# own speaker root:operator
perm speaker 0666
# K3b
# own /dev/cd0 root:operator
perm /dev/cd0 0666
perm /dev/acd0 0666
# own /dev/cd1 root:operator
perm /dev/cd1 0666
perm /dev/acd1 0666
# own /dev/pass0 root:operator
perm /dev/pass0 0666
# own /dev/pass1 root:operator
perm /dev/pass1 0666
# own /dev/pass2 root:operator
perm /dev/pass2 0666
# own /dev/pass3 root:operator
perm /dev/pass3 0666
# own /dev/xpt0 root:operator
perm /dev/xpt0 0666
perm /dev/xpt1 0666
# Allow all USB Devices to be mounted
perm /dev/da0 0666
perm /dev/da1 0666
perm /dev/da2 0666
perm /dev/da3 0666
perm /dev/video0 0666Code:
cdrecord -minfo
Cdrecord-ProDVD-ProBD-Clone 3.01 (amd64-unknown-freebsd11.0) Copyright (C) 1995-2015 Joerg Schilling
Using libscg version 'schily-0.9'.
No target specified, trying to find one...
cdrecord: Too many CD/DVD/BD-Recorder targets found.
scsibus1:
1,0,0 100) '' '' '' NON CCS Disk
1,1,0 101) *
1,2,0 102) *
1,3,0 103) *
1,4,0 104) *
1,5,0 105) *
1,6,0 106) *
1,7,0 107) *
scsibus2:
2,0,0 200) 'OPTIARC ' 'DVD RW AD-5680H ' '3AHB' Removable CD-ROM
2,1,0 201) *
2,2,0 202) *
2,3,0 203) *
2,4,0 204) *
2,5,0 205) *
2,6,0 206) *
2,7,0 207) *
scsibus3:
3,0,0 300) 'ASUS ' 'SDRW-08D2S-U ' 'F401' Removable CD-ROM
3,1,0 301) *
3,2,0 302) *
3,3,0 303) *
3,4,0 304) *
3,5,0 305) *
3,6,0 306) *
3,7,0 307) *
scsibus4:
4,0,0 400) 'APPLE ' 'SD Card Reader ' '1.00' Removable Disk
4,1,0 401) *
4,2,0 402) *
4,3,0 403) *
4,4,0 404) *
4,5,0 405) *
4,6,0 406) *
4,7,0 407) *
cdrecord: Select a target from the list above and use 'cdrecord dev=b,t,l'.Thank you very much.
Solved [Solved] LSI 9211-4i multiple errors
Melchior
I have a Intel SR1530SH with a LSI 9211-4i.
I use FreeBSD 10.0-p8
In the dmesg , I have this errors:
The LSI card 9211-4i lets have SATA-II (300MB/s), but as shown above, it uses the SATA-I (150MB/s) . The problem would come about the driver?
PS: The two hard drives are WD RE4 GP @ 2TB!
For the first error block, I installed the latest version of the driver by following this procedure and this is the result:
I have no error message: (probe3:mps0:0:2:5): CAM status: Invalid Target ID :beergrin
But the transfer rate is still stuck in SATA-I (150MB/s)
Do you have an idea?
Thank you in advance for your lights!
Best regards, Melchior
User23
Re: LSI 9211-4i multiple errors
Melchior
Re: LSI 9211-4i multiple errors
When I see something written I like it when it’s the same thing on my system!
Although the rate of writing/reading is 110MB/s system see why discs SATA I instead of the SATA II?
When I buy a BMW ///M5, I like everything to be as a ///M5
Best regards, Melchior
wblock@
Re: LSI 9211-4i multiple errors
Is it jumpered to use a slower speed? The manual says a jumper on pins 5-6 sets it to the slower communication speed. Although, as @User23 says, that’s still faster than the drive can transfer data from the disk.
Terry_Kennedy
Re: LSI 9211-4i multiple errors
Many of our drivers simply make up a speed and report it. Years ago I submitted patches for this for a number of controllers, but they pre-date the CAM and AHCI changes and appear to have been dropped. In the case of the OP, the issue is here, in mpt_sas.c:
If the drive in question is really a SAS drive and not a SATA one, you can get the actual speed with smartctl -x :
Melchior
Re: LSI 9211-4i multiple errors
My problem is solved, not completely but almost!
I destroyed my RAID array. I start with my CD and I install FreeBSD!
Nice job my dear! :f
I run dmesg and . TADAAA :beergrin
The problem is with the RAID card, even if it is flashed, installed with the correct drivers, the RAID card shows that it’s SATA I when I created a RAID 1 or 0.
Now, I use the LSI’s IT firmware and i create a RAID 1 with ZFS!
By doing this I also noticed that I no longer had my freezes on the screen!
Источник
Error 5, Unretryable error
Chriscom
Dabbler
I’m desperate for a bit of help here. I’ve had my FreeNas box working for over a year now, yet today I was happily using it in Windows 10 and noticed it was slowing moving a file, it then when I tried to save anything it wouldn’t work and had lost the network connection.
I rebooted server using the off/on button on the front of the machine and when it started I got the following message back:
Trying to mount root from zfs:freenas-boot/root/freenas-9.3-stable-201512121950[].
Loading early kernel modules:
GEOM_RAID5: Module loaded, version 1.3.20140711.2 (rev f91e28e40bf7)
(da0:umass-sim0:0:0:0:0): READ(10). CDB: 28 00 00 00 24 ee 00 00 01 00
(da0:umass-sim0:0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
(da0:umass-sim0:0:0:0:0): Error 5, Unretryable error
(da0:umass-sim0:0:0:0:0): READ(10). CDB: 28 00 00 00 24 ee 00 00 02 00
(da0:umass-sim0:0:0:0:0): CAM status: SCSI Status Error
(da0:umass-sim0:0:0:0:0): SCSI status: Check Condition
(da0:umass-sim0:0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
(da0:umass-sim0:0:0:0:0): Error 5, Unretryable error
Now I’ll hold my hands up now I don’t know much about this stuff, I managed to get the whole thing working as I wanted using the GUI and a few instructions. But past that I struggle with even using the command line.
I’ve read a few bits here so far, which have confused me more, and at the moment I think my USB stick that I use to boot up has died and I need to get a new one, install FreeNAS again and then get the config from my old USB stick and I should be fine?
I’m really really worried I may lose my data (which I can’t afford to do) so I’ve currently unplugged the 4 drives on the off chance me trying anything will make it worse.
Can any body shed any light on to what I’ve done and what I should do to fix it please. Is my plan of getting a new install on a new usb stick sensible? How can I get my old config file from the USB stick?
Please help I’m in so much trouble here.
I’ve got an HP ProLiant Gen8 G1610T 2GB RAM MicroServer.
Источник
Solved Problem with CDs
fernandel
Yesterday was my first try to burn CD on FreeBSD 11.1-RELEASE and for my surprise didn’t work with the same settings which I use few years:
I have two drives: one is internal and the other external and the problem is with both of them. And I have FreeBSD on iMac 11.1 also few years. I did try to burn CD on OS X and everything is okay and works. No errors.
I tried to burn under GNOME3 and the log shows:
I use automount from ports but han I disabled it and build gvfs. Under gnome when I put disk in it mounted but the problem is when it start writing (above log).
In devfs.conf I have:
fernandel
scdbackup
the error message
> READ(10). CDB: 28 00 00 00 00 00 00 00 01 00
> SCSI sense: ILLEGAL REQUEST asc:21,0 (Logical block address out of range)
stems from an attempt to read the first block of the medium.
The «ILLEGAL REQUEST» error stems directly from the drive.
> Looks like that I have a problem just with the blank CD/DVD.
If the CD is blank, then this block is not yet readable.
Even if it was an empty formatted medium, which would be readable without
having ever been written, then mounting should fail because of no filesystem
superblock.
But being blank should not hamper burn success, of course.
> I tried to burn under GNOME3
> message = «File «(null)» could not be opened (Inappropriate ioctl for device)»
The message «Inappropriate ioctl for device» is supposed to stem from the
kernel. Probably when Brasero tried to inspect the medium by kernel means
instead of burn program means or (like K3B) by own SCSI command transactions.
The log you show looks like it stems from a verify attempt after burning.
Do you have messages from the burn preparation or the actual writing ?
Something that complains about «SCSI sense» ?
Источник
Как подключить 4G модем Мегафон MR100-3 к FreeBSD 9.1
Есть модем Мегафон MR100-3 (он же Huawei E5372) и его нужно подключить к FreeBSD 9.1
В Ubuntu кое-как настроил, но нужно для FreeBSD 9.1
Сначала подключаю к Ubuntu 14.04 и вижу
# ls -la /dev | grep -i usb
# ls -la /dev | grep wdm
root@alexey-desktop:
# ls -la /dev | grep sr
Посылаю команду с помощью usb_modeswitch и вижу:
# usb_modeswitch -v 12d1 -p 14fe -V 12d1 -P 1506 -M «55534243123456780000000000000011062000000100000000000000000000» -n 1
# ls -la /dev | grep wdm
# ls -la /dev | grep sr
# ls -la /dev | grep -i usb
Получаю по DHCP адрес
# dhclient wwan0
root@alexey-desktop:
# route add default gw 192.168.8.1
root@alexey-desktop:
Да и VID:PID поменялся
И если отправить AT команду ATI:
# cat /dev/ttyUSB0
Manufacturer: huawei
Model: E5372
Revision: 21.270.09.01.209
А во FreeBSD не работает
bsd-0 # ls /dev | grep -i cd
bsd-0 # ls /dev | grep -i cu
bsd-0 # usb_modeswitch -v 12d1 -p 14fe -V 12d1 -P 1506 -M «55534243123456780000000000000011062000000100000000000000000000» -n
Далее VID:PID меняется
И CD-ROM не исчезает
bsd-0 # ls /dev | grep -i cd
bsd-0 # ls /dev | grep -i cu
bsd-0 # uname -a
FreeBSD 9.1-RELEASE FreeBSD 9.1-RELEASE #1: Mon Jan 13 18:15:58 MSK 2014
31 декабря 2014 года у FreeBSD 9.1-RELEASE заканчивается цикл поддержки. Может имеет смысл перейти на FreeBSD 10.1?
Ай-яй-яй, как-то не с руки такому «матёрому» «бээздэшнику» советовать «обновить» систему, не находишь? Неужто в вашей FreeBSD всё решается только обновлением, мда, печаль.
ТС, поставь роутер на Linux, перед FreeBSD и подключи модем к нему, ну или подними виртуалку с Linux, пробрось туда модем и настрой Internet там, а далее разведёшь Internet, например, посредством моста.
Раз уж iZEN не знает как тебе помочь.
лольнул с минисрачика
у меня недавно была ситуация, когда huawei gsm модем распозновался как /dev/sr0
внутри него были драйвера. как ни странно, они были и для оффтопика и для linux-a.
установил, проблема решилась.
всё это выполнял на красношляпе.
Ай-яй-яй, как-то не с руки такому «матёрому» «бээздэшнику» советовать «обновить» систему, не находишь?
Не нахожу. В старые версии системы не добавляются идентификаторы и драйверы новых устройств.
В старые версии системы не добавляются идентификаторы и драйверы новых устройств.
В первом случае можно загрузить модуль с указанием идентификатора устройства или обновить пакет, во-втором случае — обновить ядро, а не всю систему.
И получишь овощ.
Собственно, какова цель обновлять только ядро, не трогая базовую систему? В чём глубинный смысл?
Мда, странно, это же Unix система, должна быть совместима.
Смысл в том, что бы не перенастраивать всю систему, из-за новых версий ПО придётся править конфигурационные файлы установленных программ-демонов (сервисов), проверять работу прочих программ и утилит, в тоже самое время ТС нужно всего лишь настроить работу 4g модема в системе.
ТС вас спрашивает как ему прикрутить новую ручку к двери, а вы ему говорите, что нужно построить новый дом и уже тогда он сможет прикрутить ручку к двери.
Смысл в том, что бы не перенастраивать всю систему, из-за новых версий ПО придётся править конфигурационные файлы установленных программ-демонов (сервисов)
Для этого есть mergemaster(8), с помощью которого обновляют и сливают конфигурации системных сервисов.
Если установленные программы не обновлять, то они будут представлять угрозу безопасности пользовательским данным.
Для этого есть mergemaster(8), с помощью которого обновляют и сливают конфигурации системных сервисов.
Вещь, конечно, хорошая, но в любом случае сравнение файлов конфигурации посредством diff, возможность выбора частей изменений в новой версии файла, которые будут приняты, даже автоматическое принятие изменений в файлах, которые не были изменены вручную или которые отличаются лишь версией релиза FreeBSD, не избавит от необходимости правки конфигурационных файлов, изменения конфигарции в соответствии с особенностями новой версии программы, а зачастую и написания конфигурации с нуля и, конечно, детальной проверки всего функционала.
Если установленные программы не обновлять, то они будут представлять угрозу безопасности пользовательским данным.
31 декабря 2014 года у FreeBSD 9.1-RELEASE заканчивается цикл поддержки.
поддержка ещё действует, если даже она будет прекращена, то разработчики используемых программных продуктов продолжают поддерживать несколько версий своих продуктов, можно собирать из исходных кодов новые субверсии программ, выпущенные для используемой мажорной версии программы в текущем дистрибутиве.
Источник
Error 5, Unretryable error on attempted install
bureau13
Dabbler
This is my first foray into TrueNAS. I’m attempting to install from DVD to an old PC that I’ve upgraded with 6x3TB WD Red Plus, and I’m attempting a mirrored install onto two 16G USB sticks. However, I don’t seem to be getting far enough for any of that to matter.
I boot up from the DVD-ROM, and I get the TrueNAS boot menu. I select to boot the installer (or it auto-selects that) and it runs, putting out a bunch of output. Some of it seems like errors but maybe they’re normal: Can’t find zfs, a whole bunch of «need to extend HID» or something like that, then eventually it just prints out Error 5, Unretryable error, some other info about SCSI, etc, then it pauses, and prints the Error 5 stuff again, and again, and again ad nauseum. I’m never getting to the point where I select where I want to install, or anything. I see a lot of threads on this Error 5, but they all seem to have something to do with the hard drives or boot devices and I’m not even there yet. Any ideas?
Samuel Tai
Never underestimate your own stupidity
Junk the USB sticks. They’re the cause of most install problems, because it’s too common for sticks not to have full capacity. The Chinese are notorious for hacking sticks so a 512k looks like a 16G.
Early USB chipsets weren’t really great for booting either.
Please describe your hardware, per the forum rules.
Источник
Есть фря, есть мтс коннект, при подключении выводит лог в /etc/log/messages
Код: Выделить всё
Jul 8 16:16:37 perfilovvy-router kernel: ugen1.2: <MOBILE> at usbus1
Jul 8 16:16:37 perfilovvy-router kernel: umass0: <Mass Storage> on usbus1
Jul 8 16:16:37 perfilovvy-router kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000
Jul 8 16:16:37 perfilovvy-router kernel: umass0:6:0:-1: Attached to scbus6
Jul 8 16:16:37 perfilovvy-router kernel: cd1 at umass-sim0 bus 0 scbus6 target 0 lun 0
Jul 8 16:16:37 perfilovvy-router kernel: cd1: <Mass Storage 2.31> Removable CD-ROM SCSI-2 device
Jul 8 16:16:37 perfilovvy-router kernel: cd1: Serial Number 123456789ABCDEF
Jul 8 16:16:37 perfilovvy-router kernel: cd1: 40.000MB/s transfers
Jul 8 16:16:37 perfilovvy-router kernel: cd1: cd present [37376 x 2048 byte records]
Jul 8 16:16:37 perfilovvy-router kernel: cd1: quirks=0x10<10_BYTE_ONLY>
Jul 8 16:16:37 perfilovvy-router kernel: da0 at umass-sim0 bus 0 scbus6 target 0 lun 1
Jul 8 16:16:37 perfilovvy-router kernel: da0: <TF CARD Storage 2.31> Removable Direct Access SCSI-2 device
Jul 8 16:16:37 perfilovvy-router kernel: da0: Serial Number 123456789ABCDEF
Jul 8 16:16:37 perfilovvy-router kernel: da0: 40.000MB/s transfers
Jul 8 16:16:37 perfilovvy-router kernel: da0: Attempt to query device size failed: NOT READY, Medium not present
Jul 8 16:16:37 perfilovvy-router kernel: da0: quirks=0x2<NO_6_BYTE>
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 fe 00 00 01 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91fe
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 c1 00 00 04 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91c1
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 fe 00 00 01 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91fe
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:
Jul 8 16:16:38 perfilovvy-router kernel: 0:0): cddone: got error 0x5 back
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:38 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 fe 00 00 01 00
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91fe
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 c1 00 00 04 00
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91c1
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 fe 00 00 01 00
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91fe
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:
Jul 8 16:16:39 perfilovvy-router kernel: 0):
Jul 8 16:16:39 perfilovvy-router kernel: cddone: got error 0x5 back
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 ff 00 00 01 00
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91ff
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:39 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 e0 00 00 01 00
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91e0
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): READ(10). CDB: 28 00 00 00 91 fc 00 00 01 00
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): CAM status: SCSI Status Error
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI status: Check Condition
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): SCSI sense: MEDIUM ERROR asc:11,0 (Unrecovered read error)
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Info: 0x91fc
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): Error 5, Unretryable error
Jul 8 16:16:40 perfilovvy-router kernel: (cd1:umass-sim0:0:0:0): cddone: got error 0x5 back
Вобщем где косяк? он не может модем распознать?
В ядре блок про USB не комментировал, все есть.
добавил строки в cat /boot/loader.conf
Суть в том что мой модем определяется как CD-ROM для Freebsd, и в /dev/ не появляется устройство типа cuaU.
Подскажите как модем превратить из cd-roma в usb модем.
Последний раз редактировалось f_andrey 2015-07-08 12:18:38, всего редактировалось 1 раз.
Причина: Автору. пожалуйста, выбирайте соответствующий раздел форума.
В мини-фаге по материалам данного форума описал 2 способа монтирования флешок (
http://uvsw.narod.ru/faq/x.html#q4
). Но не хватает универсальности! Помогите добить тему и сделать для пользователей действительно универсальный способ.
Кратко!!!
4. USB Flash Drive можно тоже автомонтировать?
способ A. Нужно остановить даемон usbd, затем запустить usbd с ключами -v -d и подключить флешку. Usbd сообщит параметры vendor, product, release. Затем внести свои данные в /etc/usbd.conf, соблюдая отступы как в примере.
device «USB device»
vendor 0x0ea0
product 0x6828
release 0x0110
attach «sleep 2 && test -c /dev/da0s1 && mount_msdosfs -m 777 -L ru_RU.KOI8-R -D CP866 /dev/da0s1 /mnt/usb»
detach «umount -f /mnt/usb»
способ B. В файле /etc/devd.conf пропишите инструкции демону устройств devd и перезагрузитесь.
#### my usb device ######
attach 0 {
device-name «umass0»;
action «sleep 2 && test -c /dev/da0s1 && /sbin/mount_msdosfs -m 777 -L ru_RU.KOI8-R -D CP866 /dev/da0s1 /mnt/usb»;
};
detach 0 {
device-name «umass0»;
action «umount -f /mnt/usb»;
};
###################
——————-
Недостатки способа А в том что нужно прописывать специфичные для каждого USB Flash параметры. Этот способ отметаем, способ B лучше, но не все сладко.
Я взял свою флешку на 128Mb Seitec назовем ее X и коллеги на 256Mb BandySteno назовем Y. Если вставлять мою флешку X, то появляются устройства /dev/da0 и /dev/da0s1 и команда action «sleep 2 && test -c /dev/da0s1 && /sbin/mount_msdosfs -m 777 -L ru_RU.KOI8-R -D CP866 /dev/da0s1 /mnt/usb»;
спит 2 сек + проверяет наличие устройства + монтирует da0s1. Но если вставить флешку Y, то появляется только /dev/da0 и естественно команда action не срабатывает. И тут парадокс флешку Y можно в ручную подмонтировать mount_msdosfs /dev/da0 /mnt/usb, а мою X так не подмонтировать, только через /dev/da0s1.
Хотелось бы монтировать ЛЮБУЮ флешку сходу, а тут даже не понимаю почему /dev/da0s1 то появляется с моей X флешкой, а с Y — нет.
Вообщем нужен универсальный способ для монтирования USBFlash сходу с поддержкой русских букв. Плиз, хелп!