Stable IT

Все, готово! Теперь на контейнере необходимо лишь настроить клиентские библиотеки, для CentOS: http://phpsuxx.blogspot.com/2009/12/nfs.html, для Debian: http://phpsuxx.blogspot.com/2011/01/nfs-debian.html

Источник: http://wiki.openvz.org/NFS

Пару слов о недвижимости в Дубае

http://d-prospero.livejournal.com/99721.html?thread=3232137

Методология тайм-менеджмента "Getting Things Done"

http://ru.wikipedia.org/wiki/Getting_Things_Done

Friday, 25 March 2011

Django: массовая регистраций моделей в админке

http://markeev.labwr.ru/2011/03/blog-post_17.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+markeev+%28%D0%98%D0%B2%D0%B0%D0%BD+%D0%9C%D0%B0%D1%80%D0%BA%D0%B5%D0%B5%D0%B2%29

Любителям слушать музыку вместе с работой посвящается

В книге “Человеческий фактор: успешные проекты и команды” (Том ДеМарко, Тимоти Листер), ... , вычитал про интересную особенность мозга: когда работаешь в наушниках, та часть мозга, которая отвечает за озарения, внезапные прозрения и вообще техническую гениальную-виртуозность тупо отключается. Она занята прослушивание музыки. Так что если хотите не просто программировать, а программировать с озарениями и проблесками творческой мысли – работайте в тишине. Для меня, кстати, это значит, что день придется делить на 2 рабочих куска с 8 до 11 и с 22 до 24, т.к. только в эти промежутки некому меня отвлекать.

Источник: http://markeev.labwr.ru/2010/12/django-multihost-uwsgi.html?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+markeev+%28%D0%98%D0%B2%D0%B0%D0%BD+%D0%9C%D0%B0%D1%80%D0%BA%D0%B5%D0%B5%D0%B2%29

Как добавить свой путь в PATH на CentOS?

Открываем файл конфигурации:

vi /etc/profile

Находим строку "Path manipulation" и чуть нижее нее будет условный оператор, внутрь которого и нужно добавить наш дополнительный путь поиска бинарных приложений:

# Path manipulation
if [ "$EUID" = "0" ]; then
pathmunge /sbin
pathmunge /usr/sbin
pathmunge /usr/local/sbin
pathmunge /usr/StorMan # добавленный путь
fi

После этого выходим/входим в ssh сессию и приложения из добавленного пути станут доступны по именам команд, без использования абсолютных путей.

Источник: http://serverfault.com/questions/102932/adding-a-directory-to-path-in-centos

Отличная бесплатная ip2geo база

http://www.wipmania.com/ru/base/

По наводке: http://slach.livejournal.com/320111.html

Странные ошибки от контролллера Adaptec 5405

sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:<3>Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
Dev sdc: unable to read RDB block 0
Buffer I/O error on device sdc, logical block 0
Buffer I/O error on device sdc, logical block 0
unable to read partition table
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:<3>Buffer I/O error on device sdc, logical block 0
Dev sdc: unable to read RDB block 0
unable to read partition table
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:Dev sdc: unable to read RDB block 0
unable to read partition table
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc : READ CAPACITY failed.
sdc : status=0, message=00, host=1, driver=00
sdc : sense not available.
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc:Dev sdc: unable to read RDB block 0
unable to read partition table
sd 6:0:0:0: Device offlined - array deleted
sd 6:0:0:0: Device online - array created
SCSI device sdc: 1170210816 512-byte hdwr sectors (599148 MB)
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc: detected capacity change from 1073741824 to 599147937792
SCSI device sdc: 1170210816 512-byte hdwr sectors (599148 MB)
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
SCSI device sdc: 1170210816 512-byte hdwr sectors (599148 MB)
sdc: Write Protect is off
sdc: Mode Sense: 06 00 10 00
SCSI device sdc: drive cache: write through w/ FUA
sdc: unknown partition table
printk: 30 messages suppressed.
TCP: Treason uncloaked! Peer 217.118.66.105:46079/80 shrinks window 1145999560:1146003940. Repaired.
TCP: Treason uncloaked! Peer 217.118.66.105:46079/80 shrinks window 1145999560:1146003940. Repaired.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc2, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
kjournald starting. Commit interval 5 seconds
EXT3 FS on sdc3, internal journal
EXT3-fs: mounted filesystem with ordered data mode.

В целом массив работает отлично, ошибки заметил уже лишь потом, но все равно приятного мало.

Wednesday, 23 March 2011

Adaptec: aacraid: Host adapter abort request

Вот такие вот рекомендации дает производитель: http://ask.adaptec.com/scripts/adaptec_tic.cfg/php.exe/enduser/std_adp.php?p_faqid=15357&p_created=1225366599

Реальное воспроизведение этой проблемы у меня на CentOS / OpenVZ ядре выглядело так:

aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter abort request (0,0,0,0)
aacraid: Host adapter reset request. SCSI hang ?
aacraid: SCSI bus appears hung
INFO: task kjournald:2667 blocked for more than 300 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kjournald D ffff81063d6c6d20 0 2667 239 2694 2614 (L-TLB)
ffff81063c96dd10 0000000000000046 ffff8103cef55c18 ffff81063e994048
ffff81063d6c6d20 ffff81063f2c21e0 00225e9c3f355275 007303b73490f812
ffff81063d6c6f28 ffff81063f2be000 ffffffff80315a00 ffffffff8006f959
Call Trace:
[] do_gettimeofday+0x40/0x8f
[] sync_buffer+0x0/0x40
[] io_schedule+0x59/0x8a
[] sync_buffer+0x3b/0x40
[] __wait_on_bit+0x40/0x6e
[] sync_buffer+0x0/0x40
[] out_of_line_wait_on_bit+0x6c/0x78
[] wake_bit_function+0x0/0x23
[] :jbd:journal_commit_transaction+0x66b/0x163e
[] autoremove_wake_function+0x0/0x2e
[] try_to_del_timer_sync+0x7f/0x88
[] keventd_create_kthread+0x0/0xc4
[] :jbd:kjournald+0xb9/0x21b
[] autoremove_wake_function+0x0/0x2e
[] :jbd:kjournald+0x0/0x21b
[] kthread+0xfe/0x132
[] child_rip+0xa/0x11
[] keventd_create_kthread+0x0/0xc4
[] kthread+0x0/0x132
[] child_rip+0x0/0x11
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000000
end_request: I/O error, dev sda, sector 1133805164
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 112099172
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 303601948
Buffer I/O error on device sda3, logical block 33492206
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 183335284
Buffer I/O error on device sda3, logical block 18458873
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 273263468
Buffer I/O error on device sda3, logical block 29699896
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 232821356
Buffer I/O error on device sda3, logical block 24644632
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 86586132
Buffer I/O error on device sda3, logical block 6365229
lost page write due to I/O error on sda3
Buffer I/O error on device sda3, logical block 6365230
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1116971484
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 84935588
Buffer I/O error on device sda3, logical block 6158911
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 263340548
Buffer I/O error on device sda3, logical block 28459531
lost page write due to I/O error on sda3
Buffer I/O error on device sda3, logical block 28459532
lost page write due to I/O error on sda3
Buffer I/O error on device sda3, logical block 28459533
lost page write due to I/O error on sda3
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 275067372
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 306325300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 306325332
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 312738348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 316436948
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 263233268
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 316519140
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 316568044
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 346630132
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 347241932
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 459654004
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 460845484
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 565326356
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 569129404
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 640792020
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 660554428
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 928905388
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 77890148
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 198046388
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 208842820
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 232649956
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 928970300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 929035804
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1093459916
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1098507076
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 198046204
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100424348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100424452
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100425092
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 198028908
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1100425300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1103607796
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160166780
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 82970692
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 189826148
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 189878244
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 190022364
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160171820
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160187908
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160198900
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160203716
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 160737052
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1160214452
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 70747316
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 71142516
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 71665108
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 74873164
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 77072380
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 80954860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 82987108
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 82987156
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 83334076
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 83334124
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 84943132
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98054508
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98187988
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189236
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189268
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189300
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189804
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98189964
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98271148
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98271340
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98278748
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 128166348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98278812
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98278860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98281972
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282084
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282420
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282948
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98282980
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98287612
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98287748
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 98287948
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 123360132
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 127312892
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 135922428
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 138690860
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 154303020
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 156942356
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 158376348
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 308734652
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1088653580
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1087114988
Aborting journal on device sda3.
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 273794092
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
ext3_abort called.
EXT3-fs error (device sda3): ext3_journal_start_sb: Detected aborted journal
Remounting filesystem read-only
end_request: I/O error, dev sda, sector 78396708
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 215049556
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 191614356
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 199221588
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1094780788
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 1094781492
sd 0:0:0:0: timing out command, waited 360s
sd 0:0:0:0: SCSI error: return code = 0x06000028
end_request: I/O error, dev sda, sector 415043868
EXT3-fs error (device sda3): ext3_find_entry: reading directory
#11855957 offset 0
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_truncate: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
EXT3-fs error (device sda3) in ext3_orphan_del: Journal has aborted
EXT3-fs error (device sda3) in ext3_reserve_inode_write: Journal has aborted
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_committed_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
__journal_remove_journal_head: freeing b_frozen_data
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error
journal commit I/O error

arcconf при этом также не работал:

/usr/StorMan/arcconf getconfig 1
Could not open log file: /var/log/UcliEvt.log
[root@node ~]#

Debian + Lenovo IdeaCenter B505 = черный экран после запуска иссов

Фиксится так - из Recovery mode добавляем в файл:

echo "blacklist nouveau" >> /etc/modprobe.d/blacklist.conf

После этого все заработает корректно.

Источник: http://wiki.debian.org/KernelModesetting#nVidiaGfxCards

Tuesday, 22 March 2011

Пара слов о Ливии

Очень достойно, рекомендую: http://kungurov.livejournal.com/33074.html

Четко, по делу, без лишней конспирологии.

Как загрузить Ubuntu 10.04 в single mode?

нужно допиться к списку опций ядра:

single init=/bin/bash

Как включить grub меню на Ubuntu 10.04 LTS

Зажимаем shift пока мерцает курсор и будет отображено grub меню :)

Subscribe to: Posts ( Atom )

FastNetMon

Thursday, 31 March 2011

Wednesday, 30 March 2011

Sunday, 27 March 2011

Friday, 25 March 2011

Wednesday, 23 March 2011

Tuesday, 22 March 2011